On 10/13/2012 11:29 AM, Matthias Trute wrote: > Hi, > >> What is your recommended practice? > > Very simple: Use what you like most. All tools > that I include with amforth are the ones I consider > useful for others as well. I do not enforce any of > them. > > The shell has a few advantages over a dumb terminal > and I like to use it. YMMV. > > Matthias
Matthias, I agree. I use it too now. We do still have a problem how to deal with hardware idiosyncrasies as timer0.frt demonstrates. It should not be dealt with through the shell (re my ill thought #py idea). The generic frt code should include some preprocessing instructions to produce MCU specific code, m4 perhaps? Once you decide on the standard people would follow :-) Thanks, Enoch. ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ Amforth-devel mailing list for http://amforth.sf.net/ Amforth-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amforth-devel
