Re: Chipmunk Basic arrays (Attn: Ron Nicholson)

On 9/5/07 6:36 PM, in article 6s9ud39bu2t1f6j2rg058npnucor0qokd5@[EMAIL PROTECTED]
"ArarghMail709NOSPAM@[EMAIL PROTECTED]
"
<ArarghMail709NOSPAM@[EMAIL PROTECTED]
> wrote:

> On 05 Sep 2007 20:55:27 GMT, "Auric__" <not.my.real@[EMAIL PROTECTED]
>
> wrote:
> 
> <snip>
>>> The MS 16-Basics do have a default DEFtype, so you need to specify
>>> something, unless you really want SINGLE.  I think that the later
>>> GUI VBs default to Varient (4,5,6).  I don't know about 1,2,3.
>> 
>> What I meant was, unless I use one of the DEFtype commands (DEFLNG or
>> whatever), what I get is compiler-dependant (single in QB & older,
>> variant in VB, long (I think) in PB/Win, etc.).
> 
> I guess we were both saying the same thing, but in different ways.
> 
>>> While BCET doesn't have any '#ifdef' kind of preprocessor ability,
>>> it does have a feature that allows somewhat of the same abilities.
>>> 
>>> for example:
>>> 
>>> REM $Ignore: #
>>>      totally ignores the next # lines.
>> 
>> That's absolutely awesome. What's the limit for # ?
> 2^32-1  :-)
> 
> However, it's not really useful for more than a few lines, BECAUSE,
> you have to remember to change it if you add or delete lines in its
> range.  I was working on a "$Ignore: Begin" and "$Ignore: END", but
> that doesn't work yet.
> 
> There is also an "REM $Ignore: SUB" version, which when included in
> front of a SUB or FUNCTION statement, totally ignores the entire sub
> or function.
> 

All this reminds me of TI Extended Basic's pre-scan functions (which
aren't
in the manual, only included in an addendum.)

TI Basics on the TI-99 pre-scans the program, to do various things
including
checking syntax (do FOR/NEXTs match?, generated symbol table for
variables,
etc - all an effort to speed up what would otherwise be a VERY slow
interpreter to just a slow interpreter). Anyway, the pre-scan can take
some
time, some programs I remember took over 30 seconds to almost a minute
before they'd start running, as the ENTIRE program is pre-scanned.

The addendum described the ability to turn off/on the pre-scan, using
!@[EMAIL PROTECTED]
 respectively.

There were some rules, including variables had to be pre-scanned, CALLs,
first DATA statement. A good way to do this kind-of enforced "declaring"
(sort of) your variables at the top of the program. Also, you would turn
on
pre-scanning before your SUBprograms.

10 goto 100
20 ! Section for pre-scan
30 a,b,c=0::a$,b$,c$=""::CALL CLEAR::CALL SOUND::CALL COLOR ! Syntax
doesn't
matter here
40 DATA 0,1,2,3
50 !@[EMAIL PROTECTED]
 ! Turn off pre-scan
100 ! Rest of program
..
..
..
999 !@[EMAIL PROTECTED]
 ! Turn on pre-scan for SUBs
1000 SUB MENU
..
..
..
32000 SUBEND ! End of subs