[colorforth] colorforth code in ASCII

[kbk@xxxxxxxxx (Kurt B. Kaiser)]

"t" <loveall@xxxxxxxxx> writes:

> Please excuse the pedantry. 

Much preferable to blather.

[...]

> See "Color Forth" section of
> http://www.users.qwest.net/~loveall/binary/concluse.txt
> for a more detailed operational description.

This is a very interesting document.  Thanks for the insight.  Is it
linked from your home page?

> 
> A formal proof is provided in the two color forth text editor source
> files: 4wdec.p (ASCII format) and 4wcedit.p (color format) which
> generate identical binaries when compiled by 4word. The formatting
> of these two files has been tweaked to make them visually similar
> when viewed with a conventional text editor that does not break
> displaying embedded color codes.
> 
> These semantic equivalents are also a close fit to Chuck's
> colorForth.  The specific colors are implementation dependent.

Being able to switch back and forth from Color display to ASCII
display, and being able to print and store using ASCII is very
helpful to the acceptance of ColorForth, IMHO.  

Your point about the Forth programmer being one with his code is can
hardly be overstated.  I am used to reading compiled Forth directly in
memory (completely understanding the structure of memory and the
execution model!) during debugging and I think that while headless,
Huffman encoded, and possibly in-lined code is great for production,
it should be produced at the end by some kind of optimizer so that the
code in memory is not obfuscated during development.

Regards, KBK
------------------------

To Unsubscribe from this list, send mail to Mdaemon@xxxxxxxxxxxxxxxxxx with:
unsubscribe ColorForth
as the first and only line within the message body
Problems   -   List-Admin@xxxxxxxxxxxxxxxxxx
Main ColorForth site   -   http://www.colorforth.com