QB64TUTORIAL.COM is ready

[mnrvovrfc]

Thank you for designing this tutorial, well-explained like the everlasting patience of a teacher. Lots of bright colors on black background hurt my eyes but it's my fault I lived a half-century so far.

I don't know, I believe information about the empty string should be given (how it differs from CHR$(0)), and especially caution using it with "ASC()".

If there's going to be information about QB64-only functionality, also indicate the second parameter to "ASC()" has to be within range of the string in the first parameter, for the same reason.

This is something a beginner could trip with. Take it from me, from programming on the Color Computer 2 then 3, and becoming disgusted M$QB also returned "error #5" for <code>ASC("")</code>.

[TerryRitchie]

Thank you for designing this tutorial, well-explained like the everlasting patience of a teacher. Lots of bright colors on black background hurt my eyes but it's my fault I lived a half-century so far.

I don't know, I believe information about the empty string should be given (how it differs from CHR$(0)), and especially caution using it with "ASC()".

If there's going to be information about QB64-only functionality, also indicate the second parameter to "ASC()" has to be within range of the string in the first parameter, for the same reason.

This is something a beginner could trip with. Take it from me, from programming on the Color Computer 2 then 3, and becoming disgusted M$QB also returned "error #5" for <code>ASC("")</code>.

Could you show some code examples of what you are referring to? I've never encountered any issues with these commands but if there are some I'll add that information.

Also, does the yellow text on dark blue also bother others?

[PhilOfPerth]

Hi Terry.
I find the colours quite acceptable (and I'm past the "3 score and ten" age). I'm enjoying working through your examples; they clarify things a lot for me.
I found something interesting while looking at lesson 3, the "NoNoGoto" example: When I changed the start value (count%) to an EVEN negative number (eg -4) everything was sweet, but when I used an ODD negative number (eg -3), the first result (for -3) was EVEN. Curiouser and curiouser!

[Pete]

My letterman's jacket is blue and gold, so no. Don't tell David, he'll want it back.

Pete

[TerryRitchie]

Hi Terry.
I find the colours quite acceptable (and I'm past the "3 score and ten" age). I'm enjoying working through your examples; they clarify things a lot for me.
I found something  interesting while looking at lesson 3, the "NoNoGoto" example: When I changed the start value (count%) to an EVEN negative number (eg -4) everything was sweet, but when I used an ODD negative number (eg -3), the first result (for -3) was EVEN. Curiouser and curiouser!

Well that's odd? -3 MOD 2 is -1, so with a remainder <> 0 it should GOTO ODD

[Pete]

Not odd at all, even. It's because it is set up to always go even on the first iteration, because no matter what you set the start value as, the initial remainder, which determines odd or even, is always zero.

Pete

[TerryRitchie]

Not odd at all, even. It's because it is set up to always go even on the first iteration, because no matter what you set the start value as, the initial remainder, which determines odd or even, is always zero.

Pete

Yep, yep. I see it now.

[PhilOfPerth]

I knew that !!!
(well, I would've, eventually).
Thanks, Pete.

[Pete]

Absolutely historical. Terry warned everyone about the dangers of using GOTO, and oddly enough, he even screwed himself!

Pete

- IF pete = smartascii THEN GOTO hello_world

[PhilOfPerth]

@Terry:
Just noticed, in lesson 2, in your CONSTANTS explanation, line 13, you give the circumference of a circle as R*(pi squared), instead of R*pi*2. (As you know, R*(pi squared) is the area).