lci/test/1.3-Tests/7-Operators/18-ExplicitRecast/4-ToFloat/5-FromString/2-EmptyString/test.lol

HAI 1.3
	I HAS A var ITZ ""
	var IS NOW A NUMBAR
	VISIBLE var
KTHXBYE
Added variable type initialization 2010-09-02 03:06:15 +00:00			`HAI 1.3`
Initial project import 2010-08-09 07:01:59 +00:00			`I HAS A var ITZ ""`
			`var IS NOW A NUMBAR`
relax numeric conversions from string The spec does not establish any particular constraints to observe in casting from `YARN` to `NUMB(A)R`. Presently, `lci` checks that the string consists only of numeric characters prior to attempting the conversion, halting with an error if it's found not to be the case. This behavior is often more inconvenient than helpful. Many numeric strings encountered in the wild are "roughly numeric", and it would be wise to account for this observation. As a simple example, a user may be prompted to input a number; in the case of their inadvertently providing leading or trailing whitespace, a naive program will crash rather than gracefully extracting the otherwise sensible input. This patch removes the `isDecString()` function and instead leverages the `strtoll()` and `strtof()` functions to handle casts from `YARN` to `NUMBR` and `NUMBAR`, respectively. Thus, strings to be converted are permitted to contain leading whitespace, and trailing non-numeric characters are ignored. Additionally, `YARN`s to be cast to `NUMBR` may lead with `"0"` or `"0x"` to indicate that the string should be interpreted as an octal or hexadecimal value, respectively. This change required the modification of several tests which previously checked that casting an empty or completely non-numeric `YARN` resulted in an error. These now verify that such a conversion results in a zero of the appropriate type. 2015-08-15 23:43:05 +00:00			`VISIBLE var`
Initial project import 2010-08-09 07:01:59 +00:00			`KTHXBYE`