[colorforth] NASM for colorforth

[Mark Slicker <maslicke@xxxxxxxxxxx>]

On Tue, 9 Jul 2002, John Drake wrote:

> Hello all,
> 
> There is merit to both sharing ColorForth as "blocks"
> and sharing ColorForth in some "portable format"
> whether that format is ASCII or something else.
> Think of people like me who dabble with Enth/Flux.
> ColorForth only works on some of the systems I have
> access to, whereas Enth/Flux works on everything
> and the learning curve for me is smaller.  It would
> be nice to be able to move code between the two
> systems.  Plus ASCII is needed if you want to post
> ColorForth code on a web page unless you're going
> to go with PNG.  (Funny that no one objects to PNG
> the same way they object to JPEG.  *grin*)  Having
> an ASCII import/export utility would be nice IMHO.
> 

Posting just blocks seems fine to me. I usually post html too, so people
know what their getting. It's not to be portable, just at the moment
people are likely be using a browser to download blocks.

In colorForth people will have a builtin viewer, so html become
unecessary.

I don't see why ASCII is prefered for interchange over blocks. It is easy
to convert automatically to ASCII or any other format when given the
source block.

You said Enth/Flux works on everything, what's the secret? Is there
something colorForth can learn?

Mark

------------------------

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
Wiki page http://kristopherjohnson.net/wiki/ColorForth
ColorForth index http://www.users.qwest.net/~loveall/c4index.htm