I think the main problem is the PIC architecture. It's actually somewhat shocking how well SDCC has done to make C actually work on an architecture that was clearly intended to run only assembly code.
As for standards, I have come to view GCC as the center of the universe. Anything that differs is nonstandard. That's why I so thoroughly appreciate the Atmel AVR processors, for which GCC is ported. -Ken Jackson Dave Baxter writes: ... > What I'm learning at the moment, is it seems that there is no such thing > as *Standard* C code any more. OK, the basic C stuff is still much the > same, and much of it ANSI compatible, notwithstanding C++ (or C#) of > course. (I've spent some years working with Pascal and Delphi, but the > only formal trainig I ever had in coding, was ANSI C based.) > > However, there seems to be little to no standardisation in the way the > various compilers are invoked, or how the build time parameters are set, > not least from within the source code, let alone via any third party IDE > via a command line shell. (Code::Blocks, or the MPLAB IDE) ... ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Sdcc-user mailing list Sdcc-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sdcc-user
