In SX Microcontrollers, SX/B Compiler and SX-Key Tool, Zoot wrote:

Robert -- I've done the exact same thing in some SX/B programs -- set a flag in the mainline program to let ISR know that it is initialized, etc. (Although sometimes I think this may point more to inadequacies in my programming style and program designs -- grin -- )

There's a tradeoff there, for sure -- I use a lot of ASM in my SX/B programs, but I like having SX/B as the overall framework -- highly convenient esp. for the mainline program. IMO, SX/B generates *really* nice and efficient code for something that is "auto-generated" assembly (Bean is the man!).

But if a program is taken out of the SX/B environment, you can generally make things *very* compact, gain a bit more control over subtler features, AND claim back global variable space used by the PARAM vars defined in SX/B. Always question of what the needs of the project are.

Bean -- how difficult would it be to extend the NOSTARTUP directive to allow for setting/not-setting vars, AND/OR setting/not-setting options, AND/OR setting/not-setting ports and such? Rather than ports/options always being setup and vars being the optional aspect?

---------- End of Message ----------


You can view the post on-line at:
http://forums.parallax.com/forums/default.aspx?f=7&p=1&m=234188#m234506

Need assistance? Send an email to the Forum Administrator at forumadmin@parallax.com

The Parallax Forums are powered by dotNetBB Forums, copyright 2002-2007 (http://www.dotNetBB.com)