Page 1 of 1

PostPosted: Thu Nov 14, 2002 1:17 pm
by blhorn

PostPosted: Thu Nov 14, 2002 1:52 pm
by guy
It appears that all of the effort is going into Orbforms Designer, which may be ported to Windows CE.

Which features do you need in PocketC? I could always try to put them into CEAPI if they are runtime features. If there are language features that you want then see the compiler section of the CEAPI forum.

PocketC CE API interface:
PCForm and CE API forum:

PostPosted: Fri Nov 15, 2002 3:49 pm
by wolfgang
I'm afraid the most pressing needs in V3 would be not enhancements, but bug fixes:

- problems with large symbol tables
- bugs in struct handling
- some of my programs simply crash ("Fatal error" in Windows) when they were compiled with V3
- some of my programs change behavior between V2 and V3 (e.g. I have text() commands that draw on the wrong position in V3)
- format() function has a bug on some device types (does not print a number, but only 'f').
- slow execution speed, super-slow compilation speed
- etc. etc.

But as Guy said (and I have the same information), Kevin is no longer interested in supporting PocketC (he has never been great in support to begin with). Most of the issues have been raised again and again by different people, but to no avail. To end on a positive note, Guy's compiler project is a silver lining on the horizon (a glaring one actually :-) I'm not worried about support there once it is released.


Composing music on the PocketPC! -