Displaying 3 results from an estimated 3 matches for "personmonth".
Did you mean:
personmonths
2014 Dec 12
2
SUGGESTION: Force install.packages() to use ASCII encoding when parse():ing code?
...and that people may want
umlauted characters in their variable names, but where this catches on,
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 down these problems.
While many packages are used in-house at least initially, making a
package is a step towards releasing it, so I'd anticipate that having
an option to support weeding out any potentially troublesome identifiers
has the potential to do some...
2014 Dec 12
5
SUGGESTION: Force install.packages() to use ASCII encoding when parse():ing code?
Duncan Murdoch <murdoch.duncan at 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 variable names is dangerous.
--
Regards,
Bj?rn-Helge Mevik
2014 Dec 12
0
SUGGESTION: Force install.packages() to use ASCII encoding when parse():ing code?
...n Fri, Dec 12, 2014 at 12:34 PM, Jan Kim <jttkim at 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
> over tracking down these problems.
Then R should ban variable names from having 'l', 'i', '1', '0' and
'O' in them!
Barry