[ColorForth] pre-parsed source and code sharing

[John Drake <jmdrake_98@xxxxxxxxx>]

Hello,

The counter argument is simple.  Flux.  :-)
Seriously I would agree that sticking with
the preparsed blocks is probably better for
code sharing amoung users of colorForth the
"system" as opposed to colorForth the 
"language".  Much of the code is system
specific anyway.  But I'm sure there will
be code that could be used in both systems.
Anyway the code you posted for going from CF
to HTML is probably enough to handle the trick.

I'm active in another "language/system"
community, namely Oberon.  While the language
has been standard for years (until recently)
early on there were several "systems" available.
V4, System 3, Oberon/F ect.  Most code sharing
happened intra-system.  But if you ever needed
to do any inter-system code sharing you had
to go to a common format.  (ASCII or HTML).

What would be more of a problem is importing/
exporting blocks.  I've seen mentioned on the
mailing list that there is a utility for doing
this in Linux.  Is there a similair utility
available for Windows and/or MS-DOS?

Regards,

John M. Drake

--- Mark Slicker <maslicke@xxxxxxxxxxx> wrote:
> Hello,
> 
> Previously some comments were made that the
> pre-parsed format of
> colorForth inhibits code sharing. I believe it
> really improves code
> sharing.
> 
> Firstly, differences in style are minimized. The
> character set is minimal,
> so variances in naming style are minimal. Only the
> first word of a name is
> put in the dictionary. So prefixed names are
> effectively 
> discouraged. There is no white space, so there can
> be no difference in
> white space conventions. Words are only lower case,
> so there can be no
> difference in case conventions.
> 
> The blocks further improve code sharing, shadow
> blocks provide a standard
> way documenting your code. Blocks also encourage a
> modular style of
> application development.
> 
> Lastly, the operators of colorForth improve code
> sharing. Control
> structures like 'if ... then' 'for ... next' 'begin
> ... end' only allow a
> byte displacement. This forces you factor highley
> nested code, it also
> improves the ability for someone to read your code.
> 
> This is all I could think of at the moment, I'm
> interested in the counter
> argument, for ASCII against pre-parsed.
> 
> Mark


__________________________________________________
Do You Yahoo!?
Yahoo! Health - Feel better, live better
http://health.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