blob: 9f158ddee6eb6dee8f72b10a6a384dcac668d5e5 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
|
<?xml version="1.0" encoding="ISO-8859-1"?>
<fpdoc-descriptions>
<package name="rtl">
<!--
====================================================================
cwstring
====================================================================
-->
<module name="cwstring">
<short>Implement the widestring manager with a C library based
implementation</short>
<descr>
<p>
The <var>cwstring</var> unit offers no API by itself: it just initializes the
widestring manager record of the <link id="#rtl.system">system</link>
unit with an implementation that uses collation and conversion routines
which are provided by the C library found on most Unix or Linux
systems that are POSIX compliant.
</p>
<p>
The <file>cwstring</file> should simply be included in the uses clause of the
program, preferably as one of the first units, and the initialization
section of the unit will do all the work.
</p>
<p>
Note that including this unit links your program to the C library of the
system.
</p>
<p>
It makes no sense to use this unit on a non-POSIX system like Windows, OS/2 or
DOS. Therefor it should always be enclosed with an ifdef statement:
</p>
<code>
program myprogram;
uses
{$ifdef unix}cwstring,{$endif}
classes, sysutils;
</code>
</descr>
<!-- procedure Visibility: default -->
<element name="SetCWidestringManager">
<short>Set the Widestring manager of the system unit to the C version</short>
<descr>
<var>SetCWidestringManager</var> actually sets the widestring manager record
of the system unit. It is called automatically by the initialization section
of the unit.
</descr>
</element>
</module> <!-- cwstring -->
</package>
</fpdoc-descriptions>
|
