The base language is very similar, but not identical (the WinCE version was originally based on the Palm version). The library functions, especially as far as database, GUI, files is concerned are very different, a program port would amount more or less to a rewrite. I'd suggest you have a good look at the function lists and descriptions for both versions, this will show you what I mean.

Most important, Kevin Cao is no longer supporting the WinCE version in any way (he has never been very responsive to begin with, bugs never got fixed), while Jeremy's support for the Palm version is excellent. If you do migrate to WindowsCE, use the V2 version of the compiler, it is MUCH MUCH faster both in compiling (seconds vs. minutes for larger programs) as well as for the speed of the code it produces (a factor between 2 and 10), and has much less bugs. V3 is pretty much unusable and as I said, this will stay that way due to lack of support.

Its a shame that the Windows CE version of Pocket C is so forgotten about. You can sit and watch the Version numbers of pocket C for Palm and the Palm Orbforms rising steadily while the Windows CE version has no support of any kind.

You Palm programmers are so lucky!

Sales of Palm PDA's are in a gradual decline (they are still market leader) while Windows CE sales are gradually rising.

Don't get me wrong Palm is a great platform but Kevin should really ease off on the Palm for a while and get CE up to speed.

I'm the first one to sign that. In my opinion, PocketC for WindowsCE/PocketPC still has great potential. Never mind M$ is giving away Embedded Visual C++ for free. This is a different class, and orders of magnitude more complex to use. I think there are loads of people out there who value PocketC for it's simplicity, that it hides most of the complexity of WindowCE - and I think my own and other people's software proves you can develop professional programs with it. Not mentioning the fact I can continue coding when I am on the road

Guy Sprackland had started to develop a PocketC compatible compiler but there hasn't been any progress lately as he seems to be consumed with his "real" life I haven't given up hope competely yet, though, I know he can pull it off if he gets to it.

Kou,
How can you access thw WinCE32 API functions from CE V3? Do you just include the libraries at the start, declare them and use them the same way as in Visual Basic?
I'm interested in the BitBlt and GetTickCount functions for example.

Like many of us Guy has this weird "other life" outside the realm of Pocket C. I myself know the shame of spending time with my family and going out to earn a living.

At the present time his knowledge and abilities would seem our best hope for our CE Woes.

I don't want to be too critical of the author of Pocket C.
I know a lot of people have become frustrated by some of the CE versions issues but Kevin has still produced a great little portable language. The fact is that I just would not have time to program my Pocket PC if I had to do it from the PC. I use the time on the train or when I'm waiting around for something to do a little bit more coding.

I think Kevin has his heart with the Palm and let?¢‚Ç¨‚Ñ¢s face it, maintaining two versions of a programming language across different platforms is a lot of work for a single person.