[fpc-devel] Re: WinCE port patches
F.Klaempfl at gmx.de
Sun Jul 3 20:17:31 CEST 2005
Yury Sidorov wrote:
Moved to fpc-devel because contains stuff which needs probably more
>>>>> 2. WinCE is unicode only OS. How would be better to handle it? RTL
>>>>> has variables/function parameters wich are PChar/Strings. I think
>>>>> in unicode systems PWideChar/WideStrings should be used.
>>>> Yes. Introduce some TOSString for the windows rtl which is
>>>> ansistring on non ce and widestring on ce and use it if ansistring
>>>> is suffient.
>>> And POSChar for PChar/PWideChar. Or maybe SysString and PSysChar?
>>> Modifications in many files will be needed. Who will do that?
>> I meant mainly for the system unit etc., not the windows unit, so it
>> shouldn't be that much.
> I meant types must be defined in system units for other targets too. For
> example there is global variable cmdline. Currently it is PChar and it
> is assigned in every system unit. We will change it to PSysChar and
> PSysChar must be defined properly in every system unit.
The question is if the real command line shouldn't be assigned to the
PChar cmdline. If someone wants the unicode command line he should use a
WinCE syscall. How is this handled in the GNU port to arm-wince? What
type does argv have?
>> About the windows unit: does M$ deliver the same header files for
>> wince and the rest? If not, I would propose to generate a new windows
>> for wince unit using h2pas. For the beginning the most important
>> functions should be enough.
> The headers are different. Were Win32 units created using h2pas?
Yes. The windows unit was done this way, however, the GNU headers
instead of the MS ones were used.
> I will
> try to generate WinCE units...
More information about the fpc-devel