05-23-2025, 08:12 PM
if the code were c, microsoft quickc would have given a warning. somewhere in that code to indicate something suspicious. "long/short mismatch detected, conversion supplied." actually that was the message i got when assigning from 16-bit integer to 8-bit "char". or something alike.
there was a time where users of gcc. were encouraged to type-cast everything. even something felt obvious between two integer types. but going from "float" to "int" it was almost mandatory. otherwise use floor() and other such functions. or involve abs() in that test for "almost-equality."
once again we're shown that basic was supposed to handle messy details. without the programmer even noticing. until the programmer obtained surprising results.
something similar happened to me which produced incorrect behavior in my program. forced me to upgrade from single to double and from integer (always 16-bit in this basic dialect) to long.
there was a time where users of gcc. were encouraged to type-cast everything. even something felt obvious between two integer types. but going from "float" to "int" it was almost mandatory. otherwise use floor() and other such functions. or involve abs() in that test for "almost-equality."
once again we're shown that basic was supposed to handle messy details. without the programmer even noticing. until the programmer obtained surprising results.
something similar happened to me which produced incorrect behavior in my program. forced me to upgrade from single to double and from integer (always 16-bit in this basic dialect) to long.