On Fri, Dec 12, 2014 at 04:58:52PM +, Barry Rowlingson wrote:
> On Fri, Dec 12, 2014 at 12:34 PM, Jan Kim wrote:
>
> > it's just a matter of time that people get characters into their code that
> > are different but indistinguishable in the font they use (I've seen this
> > with \H{o} rather
On Fri, Dec 12, 2014 at 12:34 PM, Jan Kim wrote:
> it's just a matter of time that people get characters into their code that
> are different but indistinguishable in the font they use (I've seen this
> with \H{o} rather than a \"{o}), and mega-personmonths are wasted puzzling
> over tracking dow
Duncan Murdoch writes:
> On 12/12/2014, 4:12 AM, Bjørn-Helge Mevik wrote:
>> Duncan Murdoch writes:
>>
>>> users of other languages may want to have messages and variable names
>>> in their native language, and ASCII might not be enough for that.
>>
>> Allowing for messages in non-ASCII encodi
> I'm would perhaps not go as far as calling them dangerous, but non-ASCII
> characters in code are a mixed blessing which personally I'd opt to not
> have, on balance. Being German I can understand that people may want
> umlauted characters in their variable names, but where this catches on,
> it'
On 12/12/2014, 7:34 AM, Jan Kim wrote:
> On Fri, Dec 12, 2014 at 06:01:22AM -0500, Duncan Murdoch wrote:
>> On 12/12/2014, 4:12 AM, Bj??rn-Helge Mevik wrote:
>>> Duncan Murdoch writes:
>>>
users of other languages may want to have messages and variable names
in their native language, and
On Fri, Dec 12, 2014 at 06:01:22AM -0500, Duncan Murdoch wrote:
> On 12/12/2014, 4:12 AM, Bj??rn-Helge Mevik wrote:
> > Duncan Murdoch writes:
> >
> >> users of other languages may want to have messages and variable names
> >> in their native language, and ASCII might not be enough for that.
> >
On 12/12/2014, 4:12 AM, Bjørn-Helge Mevik wrote:
> Duncan Murdoch writes:
>
>> users of other languages may want to have messages and variable names
>> in their native language, and ASCII might not be enough for that.
>
> Allowing for messages in non-ASCII encodings would probably be a good
> id
Duncan Murdoch writes:
> users of other languages may want to have messages and variable names
> in their native language, and ASCII might not be enough for that.
Allowing for messages in non-ASCII encodings would probably be a good
idea, but I think allowing non-ASCII variable names is dangerou
