> > well.. thats a design issue :)) design it correctly, and you wont run
> > into these type of problems.. the "one big C" syndrome dont work for
> > me, i try and make it all modular, and break those modules into a
> > seperate code segment of their own..
>
> I'd have to rewrite my entire app... needs it, though... but I've got to
> find time... :(
i did that! :) all my apps went through some major face-lifting.. :)
took me a while.. but.. it was worth it :)
> > it works perfectly for me..
> >
> > nothing "beta" about it.. much more professional feeling from prc-tools
> > than i ever got from mac-wannabe codewarrior :P codewarrior crashes
> > so many times, i am considering using the CD as my coffee coaster. :)
>
> There is no doubt that GCC is a great compiler, but having to write your
> code in small independently compilable "black boxes" to avoid an assembler
> error is not at all professional feeling. The compiler doesn't know that
> the linker is going to do the multiple segment fixups so you're required to
> "sub segment" even in a multiple segment app.
um.. you miss the point..
"you", as in... the programmer are in control. as soon as my compiler
thinks it can do things better than i want it to.. thats it, new
compiler time. most of the low level stuff i do, requires the use
of a compiler i know i can control.. :P so.. thats partly my reasoning
i dont believe you should just "throw" code at the compiler and make
it work it all out.. you should stay involved as much as possible,
kick the compiler in the backside when it does something bad :))
> Actually I run CW on Win2k Pro and it works great. Of course, there is lots
> of room for improvement here too :)
you including "constructor" as part of CW? :) hehe
> > prc-tools is the *nix compiler.. dont like tools like 'vi' and 'make',
> > then, it just aint for you :)
>
> Actually, I used a visual front end, VFDIDE, and that made it really great.
pfft.. /bin/sh and vim :) the best IDE ever made :P
> I guess the biggest problem I had and was a driving force in the switch to
> CW6 which I didn't mention in the prior post, is that PRC Tools v2.0 breaks
> GLIBs, so I can't even simply recompile my code from 0.5 to 2.0. Sure, the
> GLIB stuff doesn't work with CW either, but since I have to rewrite my apps
> to get rid of GLIBs, and avoid assembler error messages, CW made the most
> sense for me. YMMV :)
prc-tools 2.1 could fix the glibs stuff.. true.. :)) *that* could be
fixed, but.. i dont use em :P so, it would mean nothing for me to
upgrade :((
the move from 0.5.0 -> 2.0 is a big one, and, if you didn't anticipate
it (poor design, or.. just .. you know, that type of code) :P the move
is not easy :((
> > // az "its friday in 1 hour, 25 mins!"
.. 55 mins.. bed time for me. :P
// az
[EMAIL PROTECTED]
http://www.ardiri.com/ <--- free games!
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
