[Issue 3610] isNumeric(3.14w) is false.

2014-01-04 Thread d-bugmail
https://d.puremagic.com/issues/show_bug.cgi?id=3610 --- Comment #8 from Vladimir Panteleev thecybersha...@gmail.com 2014-01-05 06:55:27 EET --- Created an attachment (id=1311) draft patch The current implementation of isNumeric works just fine with wchar and dchar strings. However, making the

[Issue 3610] isNumeric(3.14w) is false.

2012-04-21 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=3610 SomeDude lovelyd...@mailmetrash.com changed: What|Removed |Added CC|

[Issue 3610] isNumeric(3.14w) is false.

2012-04-21 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=3610 --- Comment #7 from Jonathan M Davis jmdavisp...@gmx.com 2012-04-21 15:12:25 PDT --- No. I don't think so. The one overload of isNumeric which hasn't been deprecated is the one that takes in char[]. With the deprecated ones removed, it'll be

[Issue 3610] isNumeric(3.14w) is false.

2011-06-05 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=3610 --- Comment #1 from Andrei Alexandrescu and...@metalanguage.com 2011-06-05 16:35:20 PDT --- I find isNumeric quite a silly function. It has definitions for the following cases: bool isNumeric(cons char[], bool allowSep = false); bool

[Issue 3610] isNumeric(3.14w) is false.

2011-06-05 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=3610 Jonathan M Davis jmdavisp...@gmx.com changed: What|Removed |Added CC|

[Issue 3610] isNumeric(3.14w) is false.

2011-06-05 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=3610 --- Comment #3 from Jonathan M Davis jmdavisp...@gmx.com 2011-06-05 17:31:26 PDT --- Actually, thinking about it a bit more, given the issues of possible negative sign and possible decimal point, perhaps keeping a version of isNumeric around

[Issue 3610] isNumeric(3.14w) is false.

2011-06-05 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=3610 --- Comment #4 from Andrei Alexandrescu and...@metalanguage.com 2011-06-05 17:35:27 PDT --- The main issue I'm having with isNumeric is that it's almost as much work as actually parsing the thing. So why not just parse it as a double and see

[Issue 3610] isNumeric(3.14w) is false.

2011-06-05 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=3610 --- Comment #5 from Jonathan M Davis jmdavisp...@gmx.com 2011-06-05 17:50:20 PDT --- Well, in order to properly determine whether a string is fully numeric and convertible to an int or float or whatever, I believe that you _do_ have to parse

[Issue 3610] isNumeric(3.14w) is false.

2011-01-08 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=3610 Andrei Alexandrescu and...@metalanguage.com changed: What|Removed |Added Status|NEW |ASSIGNED