>
> No problem, Benoit, I see the advantages. After all, my problem was due
> to sloppy programming... ;)
>
> But in BASIC, one is used to everything being converted from one format
> to another without raising an error that can stop the program. So in
> normal BASIC thinking, if val() cannot find
Am 02.11.2016 17:16, schrieb Benoît Minisini:
> Le 02/11/2016 à 16:49, Rolf-Werner Eilert a écrit :
>> The new behaviour of val() drove me nuts when it appeared first ;) I had
>> used it in so many places, and all over my code. Sometimes it lasts for
>> weeks until your program hits this place, an
Le 02/11/2016 à 16:49, Rolf-Werner Eilert a écrit :
> The new behaviour of val() drove me nuts when it appeared first ;) I had
> used it in so many places, and all over my code. Sometimes it lasts for
> weeks until your program hits this place, and AGAIN val() Arrgh... :)
>
> So in most cases, I en
The new behaviour of val() drove me nuts when it appeared first ;) I had
used it in so many places, and all over my code. Sometimes it lasts for
weeks until your program hits this place, and AGAIN val() Arrgh... :)
So in most cases, I ended up either checking for null before (somewhat
roundabou
This is just noting the change in case it might help someone else - not
a plea for a change.
In g2, the Val function would ignore that part of its input string after
the first space, so that, for instance Val("12 3 5") would return the
integer value 12.
Here and there, I use this feature when
