Hi Enoch, > Regarding .S > > Indeed, says Forth 2012 RC1, "the format of the display is > implementation-dependent". > > However, doesn't GFORTH display order make a better sense:
In which way: by adding the stack depth or the ordering? > > 1 2 3 .s <3> 1 2 3 ok > > While ours: > >> 1 2 3 .s > 3 2 1 ok I agree that amforth's display looks confusing at the first glance. Expecting a but? yes: I read from left to right (as probably many others do too) and I expect the TOS to read first. Gforth's display confuses me. I always have to scan the entire line to get the information I want. Basically the built-in .s is a debugging aid for the core development. I use it rather often when I dig in internals. A more user friendly .s is better implemented as forth code, DEPTH and PICK are available (I think they are useful for that task). Matthias ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ Amforth-devel mailing list for http://amforth.sf.net/ Amforth-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amforth-devel
