Related articles |
---|
[ANN] Squirrel yet another scripting language albertodemichelis@hotmail.com (2003-09-09) |
Re: [ANN] Squirrel yet another scripting language visionary25@hotmail.com (Vis Mike) (2003-09-14) |
Re: [ANN] Squirrel yet another scripting language me@here.there.com (Peter Ashford) (2003-09-22) |
Re: [ANN] Squirrel yet another scripting language emonk@slingshot.co.nz (Corey Murtagh) (2003-09-22) |
Re: [ANN] Squirrel yet another scripting language nmm1@cus.cam.ac.uk (2003-09-23) |
Re: [ANN] Squirrel yet another scripting language joachim.durchholz@web.de (Joachim Durchholz) (2003-09-23) |
Re: [ANN] Squirrel yet another scripting language vbdis@aol.com (2003-09-27) |
Re: [ANN] Squirrel yet another scripting language visionary25@hotmail.com (Vis Mike) (2003-09-27) |
From: | "Vis Mike" <visionary25@hotmail.com> |
Newsgroups: | comp.compilers,comp.games.development.programming.misc |
Date: | 27 Sep 2003 13:57:13 -0400 |
Organization: | Compilers Central |
References: | 03-09-048 03-09-053 03-09-067 03-09-091 |
Keywords: | design |
Posted-Date: | 27 Sep 2003 13:57:13 EDT |
"Joachim Durchholz" <joachim.durchholz@web.de> wrote in message
> Corey Murtagh wrote:
> > C-style for statements are very easy to parse,
>
> Agreed.
This is the problem.. languages should be written for the user, not the
machine. A higher level language should be a translator from human thought
to machine code.
for( int i = 0; i < 10; i++ ) cout << i << endl;
for i in range( 1..10 ): print i, '\n'
(1..10) do: [ :i | Tr write: i; cr. ].
for i in 1..10 do puts( i ) end
1..10 do: i | puts: i
The last example is a mixture of Python, Smalltalk and Ruby, something
I have been working on. The fewer the symbols and repeated typing the
better -- up to a point of course.
I've been coding with C for over 10 years. (almost bought a C compiler
for my C-64), and C++ for almost as long. I don't have a probem wth C
style loops, but they are simply not as clear as other syntax.
Mike
[Right. This is DEFINITELY the last syntax theology message. -John]
Return to the
comp.compilers page.
Search the
comp.compilers archives again.