Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!crdgw1!uakari.primate.wisc.edu!sdd.hp.com!mips!pacbell.com!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!pitt!willett!ForthNet
From: ForthNet@willett.pgh.pa.us (ForthNet articles from GEnie)
Newsgroups: comp.lang.forth
Subject: Formatting Forth source code
Message-ID: <2756.UUL1.3#5129@willett.pgh.pa.us>
Date: 13 May 91 11:56:57 GMT
Organization: (n.) to be organized.  But that's not important right now.
Lines: 24

Category 2,  Topic 13
Message 24        Sat May 11, 1991
R.CAVANAUGH [BobC]           at 00:10 MDT
 
Dennis,

Thanks for the thoughts! I have used lower case in C, using caps for user
definitions (such as #define MYTHING) and the habit has stuck. For some
reason, small case seems more "friendly", but you raise a good point.  As far
as comments form vs function, I usually try to highlight items of a particular
language that someone who does not know the syntax intimately can follow
what's happening.  As the example I used was getting into some of the inner
workings of that forth, I was much more detailed than I would be for say
 10 0 i . loop, which is one reasonably encapsulated and obvious. Since I work
with a text-oriented forth, vertical and logical block spacing is again
natural to me from the C world.  By the way, re the post on eForth, how do I
find out more about polyForth ? Thanks

-- Bobc
-----
This message came from GEnie via willett.  You *cannot* reply to the author
using e-mail.  Please post a follow-up article, or use any instructions
the author may have included (USMail addresses, telephone #, etc.).
Report problems to: dwp@willett.pgh.pa.us _or_ uunet!willett!dwp