Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!xylogics!merk!spdcc!esegue!compilers-sender
From: ramsey@ncoast.ORG (Cedric Ramsey)
Newsgroups: comp.compilers
Subject: Need input on designing a new language
Message-ID: <1990May31.160617.2881@esegue.segue.boston.ma.us>
Date: 31 May 90 16:06:17 GMT
Sender: compilers-sender@esegue.segue.boston.ma.us
Reply-To: ramsey@ncoast.ORG (Cedric Ramsey)
Organization: Compilers Central
Lines: 52
Approved: compilers@esegue.segue.boston.ma.us


	I have a question to pose to you programmers. I am thinking about
developing a new language but first I would you all's input a problem that
I have. Firstly, I must say that the main goal of many languages should be
simplicty. Simple to solve problems with and simple to implement on a compiler.
Thats the heart of my problem, simple to implement. It would be easier for
me if I forced the user, programmer, to declare all the procedures before the
function body occurs. That is; 

Declare Procedure A
 ... Local and Global variables ...
End Declare
Declare Procedure B
 ... Local and Global variables ...
End Declare
     .
     .
     .
Declare Procedure X
 ... Local and Global variables ...
End Declare


Body for procedure A
End Body

Body for procedure B
End Body
    .
    .
    .
Body for procedure X
End Body

	Else I could allow the C flavor declarations, that is;
Declare procedure A
 ... Local GLobals ...
End Declare
Body for procedure A
End body

If you programmers think that this is a good or bad idea, that is, force 
programmer to declare all procedures before usage, please send me your 
pro and/or cons against or for it. After all, the language will be for you 
guys so I feel it necessary for you guys to give me guide lines in creating 
a heafty language. please leave replys via E-mail: ramsey@ncoast.ORG , 
thank you for your time and considerations.
[What's a heafty language? -John]
-- 
Send compilers articles to compilers@esegue.segue.boston.ma.us
{spdcc | ima | lotus}!esegue.  Meta-mail to compilers-request@esegue.
Please send responses to the author of the message, not the poster.