[fpc-devel] Incompatibilities between win32 windows unit andwince windows unit

peter green plugwash at P10Link.net
Sun Jan 7 15:54:54 CET 2007

> -----Original Message-----
> From: fpc-devel-bounces at lists.freepascal.org
> [mailto:fpc-devel-bounces at lists.freepascal.org]On Behalf Of Aleš Katona
> Sent: 07 January 2007 09:55
> To: FPC developers' list
> Subject: Re: [fpc-devel] Incompatibilities between win32 windows unit
> andwince windows unit
> On Ne, 2007-01-07 at 00:23 -0200, Felipe Monteiro de Carvalho wrote:
> > Hello,
> > 
> > I am porting fpgfx to Windows CE. During this work I noticed a lot of
> > incompatibilities between win32 windows unit and wince windows unit.
> > Trivial stuff, like a parameter is var on win32, but is a pointer on
> > wince.
> > 
> > Is there any special reason why it´s like that? Should we try to get
> > both units as compatible as possible? Can I send a patch for that?
> > 
> > thanks,
> I'm not an expert on the windows unit but I encountered similar problems
> among platforms and I think we should defenetly go for compat. The best
> thing you can do (so nobody can say anything) is "complement" both ends.
> So eg:
> you got this in 2 windows unit:
> W1. function A(const data): Pointer;
> W2. function A(data: Pointer): Pointer;
one big problem with this sort of thing is that you can pass anything to an untyped const parameter *INCLUDING* a pointer, so if you change something from taking an untyped pointer to taking an untyped const parameter you are going to cause strange bugs for users.

More information about the fpc-devel mailing list