> > I'm surprised to hear one of our developers advocate this technique.
> > I'm curious: why do you think it's a good technique? Presumably you have
> > a large collection of existing source code. Why is it in your interest
> > to have to change MemSet() calls in working code all over the place
> > just to compile with a new SDK? Surely you would save time and money
> > if the new SDK, while offering the improved MemFlood() for new code,
> > continued to compile your existing code correctly?
guys.. as long as we are developing.. lets just make the suttle
difference here..
MemSet != memset
the PalmOS API calls are custom built for Palm developers. since C is
case sensitive, i believe it is the assumption that if you TYPE in
MemSet rather than memset - you are aware of its implementation.
if you want to write ansi compatable code.. do this:
#define memset(ptr,size,val) MemSet(ptr,val,size)
and do it for every other PalmOS function there is that does not
suit your liking. i personally have no problem with the PalmOS api,
and if something dont work (as ansi stuff).. i normally RTFM and
even peek at the os code to verify why it wont work and update my
code..
my 2c again :)
az.
--
Aaron Ardiri
Java Certified Programmer http://www.hig.se/~ardiri/
University-College i G�vle mailto:[EMAIL PROTECTED]
SE 801 76 G�vle SWEDEN
Tel: +46 26 64 87 38 Fax: +46 26 64 87 88
Mob: +46 70 656 1143 A/H: +46 8 668 78 72
if you enjoy it, then it aint work :) - rule #106 of life
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
