ugBASIC forum

I get an error when compiling this because of the string variable in the READ statement and I assume it has to defining the DATA as a type.
How should I correct this to read in the data string/integer pair?

Just wondering...
Would something like this help?
(I'm at work so I can't check if it runs)

Hi jjarrell and ervin!

jjarrell wrote: ↑Thu Feb 06, 2025 10:42 pm I get an error when compiling this because of the string variable in the READ statement and I assume it has to defining the DATA as a type.
How should I correct this to read in the data string/integer pair?

First of all, thank you for the code fragment. Actually the compilation error was a real compiler error that I fixed in this evening's COLDFIX (COLDFIX v1.17 [rev. 20250207]), and I'll try to explain the rationale.

First of all, let's start from the assumption that BASIC (and therefore ugBASIC) do not need to define variables before being used. This is due to the so-called "implicit definition". However, the implicit definition does not carry the type with it. To overcome this limitation, you can use type suffixes, as you (rightly) wrote. And here comes the error: the syntax did not provide for the use (even optional) of the type when indicating the identifier for the READ command. So your example was correct.

ervin wrote: ↑Thu Feb 06, 2025 10:51 pm Would something like this help?

Almost. In fact, this syntax can be useful for optimizing the code produced (as long as one uses the DEFINE READ FAST directive). However, in this case one must be sure of the type one is reading, otherwise the program may break.

Thank you again!

Good news. It compiles with no errors and prints the QTY value.

However, there seems to be some odd behavior in the way it treats the QTY variable.
With the example below if you use the freshly read qty in a for/next, QTY appears to be treated as a 0.
When it is part of a calculation, total=total+qty, it adds it correctly.
If you give QTY a value, qty=10, it will work in the for/next loop.

What do I need to do to get the READ QTY to work in the for/next loop?

Hi jjarrell, thank you for the feedback and the example!

jjarrell wrote: ↑Mon Feb 10, 2025 4:39 pm What do I need to do to get the READ QTY to work in the for/next loop?

Sorry for the problem. It was a fault of mine. I introduced a regression, in order to save space on code generation for FOR...NEXT. You need to update your compiler, since an HOTFIX has been published today for cpc target (to fix bug#1195), and I just built the one for coco3. Sandbox has been fixed, too, so you could try also on that.

Thank you again!

Thanks for your help. It works as intended.
Also, thanks Ervin your suggestions.

I've cleaned up the example and posting it in the snippet area.