[futurebasic] Re: [FB] LONG IF syntax change

Message: < previous - next > : Reply : Subscribe : Cleanse
Home   : February 2001 : Group Archive : Group : All Groups

From: pochas <pochas@...>
Date: Mon, 05 Feb 2001 12:35:21 -0500
> > Why shouldn't parsers be able to parse all of the following?
>     > 
>     > 
>     > if x > y: z++
>     > 
>     > 
>     > if x > y
>     > z++
>     > eif
>     > 
>     > 
>     > if x > y: z++ else done--
>     > 
>     > 
>     > if x > y
>     > z++
>     > else
>     > done--
>     > eif
>     > 
>     > The simpler the better.
> 
>     If you're not careful, if it gets to be too "simple" it starts to get harder
>     to read and understand. If we wanted that, we'd all go to C. I'm all for IF
>     x THEN/ELSE IF/END IF blocks, but using colons for "THEN" starts getting too
>     terse if you ask me.
> 
>     -- 
>     Robin

I agree that using the colon in place of THEN is not a good substitution
for beginners
and the "THEN" syntax should be retained.  However, the colon makes the
short form
of the if--  statement more useful simply because it takes up less space
on the line.
The teacher of beginning programming should prohibit it,  but it should
be available
to the advanced programmer, imho.  I don't agree that it detracts from
readability for
the advanced programmer.

What does detract from readability is when the simple variable
designators #$%&!
are absent.  When present, you know you are looking at a simple,
predefined type.
When absent, you know are looking at a record and now you have to dig
around to
find its definition.  In C, you have no idea what you are looking at.

I like how FB handles  record definitions using the "as pointer to"
type statements.  But the Pascal type dot syntax for arrays within
records should be adopted by FB without modification.

regards,

Charles P.