#724: [bug] Parrot fails numeric conversion of ucs2 strings
----------------------+-----------------------------------------------------
Reporter: pmichaud | Owner:
Type: bug | Status: reopened
Priority: normal | Milestone:
Component: core | Version: 1.2.0
Severity: medium | Resolution:
Keywords: | Lang:
Patch: | Platform:
----------------------+-----------------------------------------------------
Comment(by doughera):
Replying to [comment:11 pmichaud]:
> In a larger sense, most groups seem to have accepted that "inf" and
"nan"
> conversions should be case-insensitive for parsing. Displaying the
> mixed-case "Inf" and "NaN" on output is (afaik) a P6-only phenomenon,
> most other languages seem to consistently do either "inf" or "INF"
> (often by simply deferring to whatever atof does).
For output from C, the story is quite mixed. The output of printf() may
differ depending on the conversion flags (%f vs. %F vs. %g) and on the
precision (printing "Infinity" rather than "Inf" when the requested
precision is high enough), as well as on any compiler flags dictating C99
compliance. In short, even on the same system, it's quite possible to run
into programs that output any of inf, Inf, INF, Infinity, INFINITY, nan,
NaN, or NAN, either with or without a leading minus sign. I would think
parrot ought to accept them all.
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/724#comment:12>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
