Re: Interpreter for old basic programs from the line number era

On Sat, 8 Mar 2008 01:56:45 -0800 (PST), thomas.mertes@[EMAIL PROTECTED]
 wrote:

>On 8 Mrz., 01:53, ArarghMail803NOS...@[EMAIL PROTECTED]
 wrote:
>> On Fri, 7 Mar 2008 23:58:56 +0000 (UTC), "Auric__"
>>
>> <not.my.r...@[EMAIL PROTECTED]
> wrote:
>>
>> <snip>
>>
>> >Yeah, I know, I shouldn't complain, especially after Python or
>> >whatever language it is where whitespace is important.
>>
>> Wouldn't touch such a language with a 10 foot pole.  :-)
>
>The importance of whitespace can have several degrees:
>- There are languages where whitespace is needed to
>  separate symbols that would otherwise be recogniced as
>  one symbol. This is the '107ELSE' problem from above.
Only a problem if floating point numbers are allowed.

>  Btw.: Almost every programming language has such problems.
>- There are languages where spaces are used as statement
>  terminators.
I have only found one place where an end of line condition is required
in order to parse Basic correctly, in the 'IF' statement to decide if
it is the single line form or multi line form.

Single line: "IF <expr> THEN <expr> [ELSE <expr>]"

Multi line: "IF <expr> THEN <eol>"
	....

If the single line form required an 'END IF', then I wouldn't have
that problem.


>- Then there are languages which I wouldn't touch with
>  a 10 meter pole: The identation has a meaning.
>
>Generally I am sceptical to the last 2 reasons
>for whitespace.
>
<snip>
-- 
ArarghMail803 at [drop the 'http://www.'
from ->] http://www.arargh.com
BCET Basic Compiler Page: http://www.arargh.com/basic/index.html

To reply by email, remove the extra stuff from the reply address.