Duncan Murdoch murdoch.dun...@gmail.com 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
On 12/12/2014, 4:12 AM, Bjørn-Helge Mevik wrote:
Duncan Murdoch murdoch.dun...@gmail.com 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
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 murdoch.dun...@gmail.com writes:
users of other languages may want to have messages and variable names
in their native language, and ASCII might not be enough
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 murdoch.dun...@gmail.com writes:
users of other languages may want to have messages and variable names
in their native
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's
Duncan Murdoch murdoch.dun...@gmail.com writes:
On 12/12/2014, 4:12 AM, Bjørn-Helge Mevik wrote:
Duncan Murdoch murdoch.dun...@gmail.com 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 Fri, Dec 12, 2014 at 12:34 PM, Jan Kim jtt...@googlemail.com 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
On Fri, Dec 12, 2014 at 04:58:52PM +, Barry Rowlingson wrote:
On Fri, Dec 12, 2014 at 12:34 PM, Jan Kim jtt...@googlemail.com 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
SUGGESTION:
Would it make sense if install.packages() and friends always use an
ascii(*) encoding when parse():ing R package source code files?
I believe this should be safe, because R code files should be in ASCII
[http://en.wikipedia.org/wiki/ASCII] and only in source-code comments
you may use
On 11/12/2014 12:59 PM, Henrik Bengtsson wrote:
SUGGESTION:
Would it make sense if install.packages() and friends always use an
ascii(*) encoding when parse():ing R package source code files?
I think that would be a step backwards. It would be better to accept
other encodings. As an English
On Thu, Dec 11, 2014 at 10:47 AM, Duncan Murdoch
murdoch.dun...@gmail.com wrote:
On 11/12/2014 12:59 PM, Henrik Bengtsson wrote:
SUGGESTION:
Would it make sense if install.packages() and friends always use an
ascii(*) encoding when parse():ing R package source code files?
I think that
11 matches
Mail list logo
