Hi, > 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?
A preprocessor would create a similiar dependency on additional tools that (at least) Erich dislikes. m4 (or cpp) are tools for the unix people, but the majority of the amforth users use windows (for whatever reason....) > Once you decide on the standard people would follow :-) Hell, no! I wont make decisions for you ;) maybe a preprocessor in (g)forth can help us? Matthias ------------------------------------------------------------------------------ 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
