× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Scott Klement wrote:

> You'd still need something to delimit the end of a condition expression
> on your if statement.   Either you'd need to put parenthesis around
> the expression (like you do in C) or you'd need to put a word there
> (BASIC uses the word 'then')  or you'd need to say that the condition
> ends at the end of this source record, or something along those
> lines...  the point is, you need SOMETHING.
>
> Using a continuation character, as you suggest, would work, but only if
> you didn't allow multiple statements on the same line.

I would not allow multiple statements on one line, since I consider that
"bad habit" and a relic from the old Basic days og the VIC-20 and C-64 where
you gained speed and saved space (and needed to!).

There's no need to use multiple statements on the same line, and it doesn't
improve readability either (IMO).

> But, at any rate, this issue was throroughly beat into the ground BEFORE
> the new compiler was released.   Now that it has been, there's little
> point in arguing it further.  It's done.   Either use it and learn to
> like it, or keep using the fixed-format lines.  It can't be changed.

Seems like I have to make a pre-processor (like I've done for MI) to add the
semicolons before compilation.

IBM *could* make the format a compile-option if they "wanted" to(ie was
pressed repeatedly).

BTW, I never liked the RLU either. :)




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.