<br><div><span class="gmail_quote">2007/1/7, Ale Katona <<a href="mailto:almindor@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">almindor@gmail.com</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Ne, 2007-01-07 at 00:23 -0200, Felipe Monteiro de Carvalho wrote:<br>> Hello,<br>><br>> I am porting fpgfx to Windows CE. During this work I noticed a lot of<br>> incompatibilities between win32 windows unit and wince windows unit.
<br>> Trivial stuff, like a parameter is var on win32, but is a pointer on<br>> wince.<br>><br>> Is there any special reason why itīs like that? Should we try to get<br>> both units as compatible as possible? Can I send a patch for that?
<br>></blockquote><div><br>All patch / comments /remarks are welcome :)<br> <br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> thanks,<br><br>I'm not an expert on the windows unit but I encountered similar problems<br>among platforms and I think we should defenetly go for compat. The best<br>thing you can do (so nobody can say anything) is "complement" both ends.
<br>So eg:<br><br>you got this in 2 windows unit:<br><br>W1. function A(const data): Pointer;<br><br>W2. function A(data: Pointer): Pointer;<br><br>Best is to complement both W1 and W2 so they both have both overloaded<br>
versions. It's not nice, but this way you ensure 100% compat and<br>everyone is happy. Ofcourse since WINCE isn't stable yet it might be</blockquote><div><br>NO, fpc wince current thrunk is very good, and excellent quality
<br>(in the past there was some issues during internal linker implementation <br>so it was not the case for all svn rel but since a few months it's very good)<br><br>wince api is not complete but i can say you that fpc-arm-wince is waiting for the
2.2 :)<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">cleaner to just copycat the windows ones into it.<br><br>Ales</blockquote>
<div><br>this is what i did since more than one year,<br>
actual wince api was first inherited from last year win32.<br>
<br>
i copy/paste them, then removed unexisting wince funcs<br>
and then start adding new ones.<br>
<br>
at the beginning i keepts possible common files for both win32/wince<br>
using ifdef. (you can look in 3month old svn inc files)<br>
but after one year i saw that nobody have interest on that.<br>
only recently ifdef and win32 declarations where removed. why ?<br>
<br>
1°)calling conventions are differents, some type/record have same name but are differents<br>
and even M$ have separated sysgen files, possibles futures issues with ce 4.2, 5, 6 versionning<br>
that can introduce also ifdefs<br>
2°)it was discussed last year here and florian+yuri thinked it was better to separate<br>
i was first against this but finally be convinced<br>
<br>
now, every time i can test some new api, i add them<br>
some are already missing but i've added all api available functions names at the beginning<br>
of .in files, so any one who need something to be added can drop a line or send a patch<br>
(here or directly to me) then i'll do my best to check an apply asap. <br>
<br>
in one year i only received 1 patch+request from Rozbeeh and it was applied in less than 24h<br>
<br>regards<br>or<br> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">_______________________________________________
<br>fpc-devel maillist - <a href="mailto:fpc-devel@lists.freepascal.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">fpc-devel@lists.freepascal.org</a><br><a href="http://lists.freepascal.org/mailman/listinfo/fpc-devel" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://lists.freepascal.org/mailman/listinfo/fpc-devel
</a><br></blockquote></div><br>