>here is the FINAL VERSION of the compo rules, i hope! I also hope that no
>more changes will be requested 'couse if we continue this way the compo
will
>never start.
Again a remark I made before:
>2) Basic accelerator:
> - not allowed if they don't come with the standard you are using (msx
>1/2/2+ or tr)
So: this will totally outlaw any compiler, since there's never been a
"standard" compiler.
Suggested rule for compilers:
-ONLY XBASIC/KUN-BASIC: using CALL TURBO ON and CALL TURBO OFF to activate
or deactivate compiler.
-No use of extra features of compiler, just plain basic
I've never used NESTOR BASIC (heck, I've been too lazy to look at its
features) but if it is XBASIC/KUN-BASIC compatible this is also accepted.
You might wonder why I want the use of a compiler be "legal". Simple: since
the day I heard about it's existence I've been using this piece of software
for almost any graphical program I made for MSX. Because of the nature of
compo-demo's which are usually graphic to get the most stunning fx, the use
of compiler is required to make these effects even possible.
I really wonder what your basic-programs WITHOUT compiler look like, but
mine will look really SHIT and will take WEEKS to finish precalculation...
I would like to hear other opinions about this problem.
Randy
****
MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put
in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the
quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
****
