READ Command problems

[blueb]

I read about an issue that the READ command can return unexpected results if not used properly...

see: viewtopic.php?p=525159#p525159

Command: Read[.<type>] <variable>
.<type> should not be optional as the 'default' (.i) can lead to unexpected results.

This happens enough that the compiler should throw an error for naked Read's.

Code: Select all

Read.i  <-- Allowed
Read    <-- Error

I agree with Skywalk, even if PB just issued a warning, it would alert the programmer of unexpected results. Besides, with Data.TypeName statement, the Typename is required.

[#NULL]

Is there a use case where the Read-type would be different than the variable type? Otherwise it could just be inferred.

[Fred]

I agree it would be safer to always specify the Read type, like for Data. You can read double data into long variable without any issue for example.