[wx-dev] wxPalm dev

[Vadim Zeitlin]

On Thu, 27 Dec 2007 23:20:13 +0800 Yunhui Fu <yhfudev at gmail.com> wrote:

YF> >  It would be great if you could add instructions about how to use/set up
YF> I add a new page in wiki:
YF> http://www.wxwidgets.org/wiki/index.php/Development:_wxPalm

 Thanks a lot, this is going to be very useful!

YF> >  Can we abstract it inside a custom global new operator? Usually defining a
YF> > global new operator in a library is a bad idea but here it's really the
YF> > only solution I can see.
YF> use #define malloc MemAlloc is ok.

 Hmm, sorry, but how is this going to help for the objects allocated with
operator new?

YF> >  Thanks! If you already have a draft of the new API, could you please post
YF> > it here?
YF> See the patch:
YF> https://sourceforge.net/tracker/?func=detail&atid=309863&aid=1858847&group_id=9863

 I did look at it but unfortunately it's not easy to understand what is it
doing just like this. It looks like it introduces some kind of intermediate
POSIX-like FS library ("pflib" -- what does "pf" mean?) but I don't really
understand why is this the best thing to do. Personally I would naively
think of either implementing real POSIX file functions on top of Palm API
(i.e. open(), close(), read(), write(), ...) and then just use them as
usual from wx code or would write wx code using Palm API directly. Could
you please explain what is the advantage of using this intermediate library
of C functions?

 Thanks in advance,
VZ