I tried WHILE...WEND and DO...LOOP but they both don't work (I get a syntax error when it reaches the LOOP or the WEND command)

10 For I = 0 to 200
20 [action]
.
.
.
100 next I

In this fornext-loop, [action] is being executed 201 times.

10 Print "MSX Resource Center"
20 goto 10

This is an endless loop

10 gosub 40
20 print "Is cool"
30 end
40 print "MSX Resource Center"
50 Return

And this is a relative jump....Uh, no loop

i already knew those, but they look so ugly (except for the FOR but i need somethin gelse because i want to do things like WHLE NOT EOF (1):...WEND)
so there is no way to do loops except for simulating them by using IF, GOTO and GOSUB?

what a rotten BASIC!
oh well, i expected something like this to happen, after all it's still Microsoft

Yeah there is, but you still need the command "GOTO"

10 i=0 ' initialize
20 'Do
30 'do the loop instructions
40 if i<5 then goto 20 'Loop while i<5

Rotton ? well, what did you expect? these machines are 15..20 yrs old!

Quote:

i already knew those, but they look so ugly ...

I'd say give NestorPreTer (www.konamiman.com/msx/msx-e.html#nestorpreter) a try. Should "de-clutter" your sources once you get the hang of it.
And while you're at it, don't forget to use NestorBASIC.

WHILE/WEND and DO/LOOP are PASCAL statements. They have migrated to some of the more recent BASIC dialects, like QBASIC, but MSX-BASIC doesn't have them yet.

While using line-numbers and 2-character variables may seem old-fashioned to you now, in it's day, MSX-BASIC was the most advanced BASIC available. And it still beats modern BASIC's in some areas.

hm.. I beg to differ

Quote:

hm.. I beg to differ

I know that's your new favourite sentence, but I'll bite anyway. Why?

Why, well .. did you take a look at the specs of blitzbasic (blitz2d, blit3d or blitz+ (win GUI style) ?

I wouldn't want to change a single feature with the msx-basic version, for sure there are some features that you miss in some new basic dialects, but not in ALL new basic dialects for sure.

Sorry to burst your bubble, but regardless how great blitzbasic is, it's DEFINITELY not BASIC.
Even the creater himself calls it a BASIC and C hybrid.

Quote:

Sorry to burst your bubble, but regardless how great blitzbasic is, it's DEFINITELY not BASIC. Even the creater himself calls it a BASIC and C hybrid.

So when a language beats msx-basic it is not basic anymore.

He calls it that a basic/c hybrid because BB has some things that the classic basics don't have (block IF's, select cases, functions, while loops etc.). But QBasic also had all these additions.
I'd call BB, the (yet to be released) BlitzMax in this case, a hybride as soon as it supports OOP, (classes, function pointers etc.).

Where do you define the border between basic and non-basic ?

Does 'basic' equal linenumbers and gotos ? And does 'basic' equal single-line IF's, and just gosubs to define subroutines?

I don't know how to decide what's basic or what's not. Visual Basic doesn't look that basic to me either. Let's call something basic when it's called basic. So blitzbasic is still a basic-dialect. Modern basics are more pascal-like than basic-like anyway.

While wend is not from Pascal...
is Pascal its while, begin / end