Am 27.10.2012 21:01, schrieb Enoch: > Hello Matthias, > > I believe that downloading code from the application should be > a discouraged practice, reasons below.
I disagree. > > Matthias Trute <mtr...@web.de> writes: > >>> *Downloading* hex code from the application is what I do now. Quite ugly >>> IMO. >> >> Whats wrong with it? It keeps the state of the controller just the >> same way MARKER does and you can transfer that state to (possibly) >> a lot of other controllers (of the same type). > > 1. Downloading application compiled code may inadvertently introduce > source code bugs. For example, a programmer needs to hand type some > device-init to get his source to work in the application and forgets to > add the same to the source file itself. This can go unnoticed for a long > while since the downloaded code does include this device-init. Sounds like you want to separate your application code (or parts of it) from the amforth core code *and* you seem to want to combine your application code in binary form (aka hex or asm files) with other amforth cores or different controller types. Am I right? If the answer is yes: no way. Moreover I don't see even chance to do it that way. > 2. Host compiled Forth code can easily be enhanced with hand written > asm. The concept of "host compiled" is more or less the opposite of what amforth is designed for. The initial hex files are the solution for the chicken-and-egg problem *only*. Matthias ------------------------------------------------------------------------------ WINDOWS 8 is here. Millions of people. Your app in 30 days. Visit The Windows 8 Center at Sourceforge for all your go to resources. http://windows8center.sourceforge.net/ join-generation-app-and-make-money-coding-fast/ _______________________________________________ Amforth-devel mailing list for http://amforth.sf.net/ Amforth-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amforth-devel
