[colorforth] NASM for colorforth

[John Drake <jmdrake_98@xxxxxxxxx>]

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.

Regards,

John M. Drake

--- Mark Slicker <maslicke@xxxxxxxxxxxxxxxxxxxxxxx>
wrote:
> 
> 
> On Sun, 7 Jul 2002, t wrote:
> > 
> > The major roadblock to having a more active
> colorForth development effort is
> > the lack of an efficient method of sharing code.
> Until colorForth has a network
> > interface or (travesty!) an ASCII implementation,
> the requisite hand
> > translation of colorForth source will inhibit code
> sharing. If you will notice,
> > most of the shared development efforts have
> centered around
> > the ASCII assembler source which is easily
> communicated. This is not a
> > coincidence.
> >
> 
> Sharing colorForth source is equivalent to
> extracting blocks and posting
> them somewhere. Exracting blocks is trivial under
> Unix with Bernd's bget
> utility. I don't what the process is for Windows,
> more difficult I
> assume? Posting space might not be available to all,
> but blocks could be
> sent as email attachments.
> 
> I suspect another impediment is learning curve. I've
> talked to some on the
> #c4th chat. Even those much experience in assembler
> and forth, experience
> varying ammounts of dificulty with colorForth. All
> we can do about this is
> encourage people ask questions. colorForth does not
> seem purposely
> difficult, but it is likely that is very different
> from what most are used
> to.
> 
> > The only thing it might be lacking is a data base
> of operational colorForth
> > versions and matching hardware. That information
> is available in the email
> > archive.
> > 
> 
> I'm going to make draft "colorForth hardware
> compatability page" with
> information compiled from this list. I think it will
> me much more helpful
> to have this information in one place.
> 
> 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
> 


__________________________________________________
Do You Yahoo!?
Sign up for SBC Yahoo! Dial - First Month Free
http://sbc.yahoo.com------------------------

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