Thread overview
[Issue 15887] invalid char/wchar/dchar values are inconsistently accepted/rejected
Apr 06, 2016
ag0aep6g@gmail.com
Apr 04
Basile-z
April 06, 2016
https://issues.dlang.org/show_bug.cgi?id=15887

ag0aep6g@gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Hardware|x86_64                      |All
                 OS|Linux                       |All
           Severity|enhancement                 |normal

--
April 04
https://issues.dlang.org/show_bug.cgi?id=15887

Basile-z <b2.temp@gmx.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |b2.temp@gmx.com
         Resolution|---                         |WONTFIX

--- Comment #1 from Basile-z <b2.temp@gmx.com> ---
hex strings are about to be removed, so this is a WONTFIX.

--
April 08
https://issues.dlang.org/show_bug.cgi?id=15887

anonymous4 <dfj1esp02@sneakemail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|rejects-valid               |spec

--- Comment #2 from anonymous4 <dfj1esp02@sneakemail.com> ---
Unicode code points are limited to 16 planes, so it's unclear if 0xFF_FF_FF_FF
should be accepted or not. Some think that it should be seen as a possible
value, because it is possible. As to whether it should be allowed as a
literal...
Should invalid utf8 text in string literals be accepted too?

--