Hi, > It seems that the keywords code,at,shadowregs, wparam are > no longer recognized. Am I doing something wrong or have these > been changed. > I can see from the manual that 'code at' has is now '__code __at' > but shadowregs and wparam should still be supported?
Some weeks ago, *all* SDCC-specific (non-C) keywords have been renamed to __keyword in order to increase standard compliance. This is true also for shadowregs and wparam. > This is my commandline to compile the code, am I missing a switch > or something? > > /Users/nyholku/Desktop/sdcc/bin/sdcc -c "-Wl,-m,-s 18f4550.lkr" -mpic16 > -p18f4550 --disable-warning 85 --std-sdcc99 --obanksel=3 main.c -o > ../obj/main.o The only switch you might be missing is --use-non-free, used to include the default search paths of the supposedly non-free device headers and libraries. There is no switch (apart from -Dwparam=__wparam -Dshadowregs=__shadowregs) to restore the non-underline-prefixed keywords. I guess we could have kept them around in -std=sdccNN modes, but we did not :-( Best regards Raphael ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Sdcc-user mailing list Sdcc-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sdcc-user
