Topic: Paper: Fixing the specification of universal-character-names


Author: David Krauss <potswa@gmail.com>
Date: Sat, 28 Dec 2013 23:57:16 +0800
Raw View
I've drafted a proposal to replace undefined behavior of special cases
of UCNs with conditional support of more general concepts. This is
intended to supersede the recommendation in N3801 that specified
undefined behavior be changed to required diagnosis. The motivations are
essentially that there are many ill-specified behaviors that would be
unaffected by changing the specified cases, and that required diagnosis
requires excessive implementation, where no further implementation
should be required (following the principle of "standardize existing
practice").

https://www.dropbox.com/s/plak4iupdzcfick/Fixing%20UCNs.pdf

Another paper covering other instances of undefined behavior and holes
in the preprocessor specification will hopefully follow soon.

--

---
You received this message because you are subscribed to the Google Groups "ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an email to std-proposals+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
Visit this group at http://groups.google.com/a/isocpp.org/group/std-proposals/.

.


Author: Ville Voutilainen <ville.voutilainen@gmail.com>
Date: Sat, 28 Dec 2013 18:43:06 +0200
Raw View
On 28 December 2013 17:57, David Krauss <potswa@gmail.com> wrote:
> I've drafted a proposal to replace undefined behavior of special cases of
> UCNs with conditional support of more general concepts. This is intended to
> supersede the recommendation in N3801 that specified undefined behavior be
> changed to required diagnosis. The motivations are essentially that there
> are many ill-specified behaviors that would be unaffected by changing the
> specified cases, and that required diagnosis requires excessive
> implementation, where no further implementation should be required
> (following the principle of "standardize existing practice").
>
> https://www.dropbox.com/s/plak4iupdzcfick/Fixing%20UCNs.pdf
>
> Another paper covering other instances of undefined behavior and holes in
> the preprocessor specification will hopefully follow soon.

I suppose you could deliver such papers directly to SG12, their mailing
list is at http://www.open-std.org/mailman/listinfo/ub

--

---
You received this message because you are subscribed to the Google Groups "ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an email to std-proposals+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
Visit this group at http://groups.google.com/a/isocpp.org/group/std-proposals/.

.