RE: [fpc-devel] Incompatibilities between win32 windows unitandwince windows unit

2007-01-07 Thread Daniël Mantione
Op Sun, 7 Jan 2007, schreef peter green: > maybe the answer is to build two windows units, one called windows and > only availible on win32 which will be effectively a delphi compatibility > unit ... No, the problem is not serious enough to warrant the extra development effort. While I'm a s

Re: [fpc-devel] Incompatibilities between win32 windows unitandwince windows unit

2007-01-07 Thread Olivier Rinaudo
originally win32 api was converted with fpc tool automatically this is why it's closer to c than delphi equ declarations. as yury indicated , compatibility adaptation should be done in redef 2007/1/7, peter green <[EMAIL PROTECTED]>: > I'm not particularly happy with "pascalization" of direc

RE: [fpc-devel] Incompatibilities between win32 windows unitandwince windows unit

2007-01-07 Thread peter green
> I'm not particularly happy with "pascalization" of direct interfaces > myself. me neither, my understanding of this problem is that borland pascalised the windows unit in delphi and freepascal followed suite for win32. but for whatever reason the same was not done for wince. since wince suppo

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

2007-01-07 Thread Aleš Katona
> 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. > I'm not saying tha

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

2007-01-07 Thread peter green
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] 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 -020

Re: [fpc-devel] Incompatibilities between win32 windows unit and wincewindows unit

2007-01-07 Thread Yury Sidorov
From: "Felipe Monteiro de Carvalho" <[EMAIL PROTECTED]> 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 reas

Re: [fpc-devel] Incompatibilities between win32 windows unit and wince windows unit

2007-01-07 Thread Olivier Rinaudo
2007/1/7, Aleš Katona <[EMAIL PROTECTED]>: 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 parame

[fpc-devel] make deb fails on trunk

2007-01-07 Thread Rob van der Linde
Sorry, I think I sent from the wrong email address before, you may get this message twice, sorry Hi, I tried building the trunk today on Ubuntu Linux 32 bit, using these instructions: http://www.freepascal.org/wiki/index.php/Release_engineering I followed the OS specific section for Linux, g

Re: [fpc-devel] Incompatibilities between win32 windows unit and wince windows unit

2007-01-07 Thread Marco van de Voort
> > 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? > > I'm not an expert on the windows unit but I encountered similar problems > among platforms and I think we should defenetly go for comp

Re: [fpc-devel] Incompatibilities between win32 windows unit and wince windows unit

2007-01-07 Thread Aleš Katona
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 > wi