search for: mbcss

...the object is created, plus some internal components. It is implemented as an environment so that there can be multiple references to it. "srcref" is a reference to a particular range of characters (as the parser sees them; I think that really means bytes, but I haven't tested with MBCSs) in a source file. It is implemented as a vector of 4 integers (first line, first column, last line, last column), with the srcfile as an attribute. The parser attaches a srcref attribute to each complete statement as it gets parsed, if option("useSource") is TRUE. (I've left the o...

...characters. I've recently spotted many cases in which nchar() has been used with substr() which works in characters; this can lead to incorrect results. (This seems the commonest use of nchar() in packages.) There were two reasons why nchar() was left defaulting to bytes when we allowed MBCSs in R: 1) Many of the uses are of the form if(nchar(x)) or if(nchar(x)==0) or even if nchar(x) != 0. Computing the length of a string is an inefficient way to find out if it is non-empty, especially if it has to be converted to wchars to do so. 2) Once you allow multibyte characters, not all c...

completion is semi-broken in today's r-devel, and the reason seems to be some regular expression changes: > sessionInfo() R version 2.6.0 Under development (unstable) (2007-05-22 r41673) i686-pc-linux-gnu locale: [...] attached base packages: [1] "stats" "graphics" "grDevices" "utils" "datasets" "methods" [7]

...lt when creating a list matrix result. (Reported by Martin Morgan.) o besselI(x, nu, exp=TRUE) and besselY(x, nu) could give wrong answers for nu < 0. (Reported by Hiroyuki Kawakatsu.) o [g]sub could confuse a trailing byte '\' for a backreference in MBCSs where '\' can occur as a trailing byte (not UTF-8 nor EUC-JP, but SJIS and the CJK character sets used on Windows). (PR#9751) -- O__ ---- Peter Dalgaard ?ster Farimagsgade 5, Entr.B c/ /'_ --- Dept. of Biostatistics PO Box 2099, 1014 Cph. K (*)...

...lt when creating a list matrix result. (Reported by Martin Morgan.) o besselI(x, nu, exp=TRUE) and besselY(x, nu) could give wrong answers for nu < 0. (Reported by Hiroyuki Kawakatsu.) o [g]sub could confuse a trailing byte '\' for a backreference in MBCSs where '\' can occur as a trailing byte (not UTF-8 nor EUC-JP, but SJIS and the CJK character sets used on Windows). (PR#9751) -- O__ ---- Peter Dalgaard ?ster Farimagsgade 5, Entr.B c/ /'_ --- Dept. of Biostatistics PO Box 2099, 1014 Cph. K (*)...

...ymbol reported to be missing by .Fortran() is now the actual name. (What was reported to be an 'entry point' was missing the common leading underscore.) o print() on a MBCS character string now works properly a character at a time rather than a byte at time. (This does not affect MBCSs like UTF-8 and the Windows DBCSes which have non-ASCII lead bytes and always worked correctly.) o glm() now recalculates the null deviance whenever there is an offset (even if it is exactly zero to avoid a discontinuity in that case, since the calculations with and without offset are done...

...ymbol reported to be missing by .Fortran() is now the actual name. (What was reported to be an 'entry point' was missing the common leading underscore.) o print() on a MBCS character string now works properly a character at a time rather than a byte at time. (This does not affect MBCSs like UTF-8 and the Windows DBCSes which have non-ASCII lead bytes and always worked correctly.) o glm() now recalculates the null deviance whenever there is an offset (even if it is exactly zero to avoid a discontinuity in that case, since the calculations with and without offset are done...