@TempodiBasic
We can also see this on the page https://qb64phoenix.com/qb64wiki/index.php/Variable :
"Variables in QB64 can be any name except the names of QB64 or QBasic keywords and may not contain spaces or non-alphabetical/non-numerical characters (except "." and "_"). Numerical characters cannot be used as the first character of a variable or array name! QB64 reserves the use of a leading underscore to QB64 procedural or variable type names only!"
I notice that with OPTION _EXPLICIT we no longer get “Illegal string-number conversion” but instead:
“Variable ‘glop__ASCII_CHR_046__w__ASCII_CHR_046__element__ASCII_CHR_046__i’ (SINGLE) not defined”
I will now prefer using an underscore instead of a dot when naming variables; by using the dot exclusively for variables in a UDT, I’ll avoid triggering the parser bug.
And from now on, I’ll be using OPTION _EXPLICIT.
We can also see this on the page https://qb64phoenix.com/qb64wiki/index.php/Variable :
"Variables in QB64 can be any name except the names of QB64 or QBasic keywords and may not contain spaces or non-alphabetical/non-numerical characters (except "." and "_"). Numerical characters cannot be used as the first character of a variable or array name! QB64 reserves the use of a leading underscore to QB64 procedural or variable type names only!"
I notice that with OPTION _EXPLICIT we no longer get “Illegal string-number conversion” but instead:
“Variable ‘glop__ASCII_CHR_046__w__ASCII_CHR_046__element__ASCII_CHR_046__i’ (SINGLE) not defined”
I will now prefer using an underscore instead of a dot when naming variables; by using the dot exclusively for variables in a UDT, I’ll avoid triggering the parser bug.
And from now on, I’ll be using OPTION _EXPLICIT.
