Yeah, i t was legal C and thus SDCC compiled it correctly, however a warning would have been nice. But given the constraints of SDCC development these sort of things may not be a priority.
> Use a different compiler and crank up the warnings to see what you get. Yeah, that is a very good advice, running your code through gcc with all warnings turned on whenever you are having strange results with SDCC very often pinpoints to code to your code, not SDCC. Been there, done that. I usually make a point to structure / defines / make so that I can run it using gcc anytime I need to do it. just my 2 cnt, Kusti ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Sdcc-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sdcc-user
