search for: 0x10l

On 01/05/2007 7:21 AM, Stephan wrote: > Hi, > >> 0x10L > returns: int 0 > > I would expect: int 16? > This happens with all integer constants given by hexadecimal notation. > It's a bug? Certainly looks like one; I've cc'd this to the bug list (but won't be able to look into fixing it). Duncan Murdoch > > &gt...

Hi, > 0x10L returns: int 0 I would expect: int 16? This happens with all integer constants given by hexadecimal notation. It's a bug? > sessionInfo() R version 2.5.0 (2007-04-23) i386-pc-mingw32 locale: LC_COLLATE=German_Germany.1252;LC_CTYPE=German_Germany.1252;LC_MONETARY=German_Germany.1252;LC_NU...

...qr.coef() were not pivoted to match. (PR#9623) o UseMethod() could crash R if the first argument was not a character string. o R and Rscript on Unix-alikes were not accepting spaces in -e arguments (even if quoted). o Hexadecimal integer constants (e.g. 0x10L) were not being parsed correctly on platforms where the C function atof did not accept hexadecimal prefixes (as required by C99, but not implemented in MinGW as used by R on Windows). (PR#9648) o libRlapack.dylib on Mac OS X had no version information and som...

...qr.coef() were not pivoted to match. (PR#9623) o UseMethod() could crash R if the first argument was not a character string. o R and Rscript on Unix-alikes were not accepting spaces in -e arguments (even if quoted). o Hexadecimal integer constants (e.g. 0x10L) were not being parsed correctly on platforms where the C function atof did not accept hexadecimal prefixes (as required by C99, but not implemented in MinGW as used by R on Windows). (PR#9648) o libRlapack.dylib on Mac OS X had no version information and som...

I recently started using R 2.7.2, and noticed a surprising change in the behavior of var() on NA data: R 2.6.1 (Patched), 2007-11-26, svn.rev 43541, x86_64-unknown-linux-gnu: > stdev(rep(NA,3), na.rm=F) [1] NA > stdev(rep(NA,3), na.rm=T) [1] NA > var(rep(NA,3), na.rm=T, use="complete.obs") [1] NA R 2.7.2 (Patched), 2008-09-02, svn.rev 46491,

...g when being parsed, e.g. "\." where probably "\\." was intended. ("\." is valid, but the same as ".".) Thanks to Bill Dunlap for the suggestion. o Introduced the suffix L for integer literals to create integer rather than numeric values, e.g. 100L, 0x10L, 1e2L. o Set the parser to give verbose error messages in case of syntax errors. o The class "LinearMethodsList" has been extended and will be used to create list versions of methods, derived from the methods tables (environments). The older recursive "MethodsList"...

...g when being parsed, e.g. "\." where probably "\\." was intended. ("\." is valid, but the same as ".".) Thanks to Bill Dunlap for the suggestion. o Introduced the suffix L for integer literals to create integer rather than numeric values, e.g. 100L, 0x10L, 1e2L. o Set the parser to give verbose error messages in case of syntax errors. o The class "LinearMethodsList" has been extended and will be used to create list versions of methods, derived from the methods tables (environments). The older recursive "MethodsList"...

> Thanks all point about security, I''ll do as follows. > I thought that the point was the following two. > > > 1. Storage place of encrypted password > Should I store it in /etc/xen/passwd ? > Or, should I wait for DB of Xen that will be released in > the future? The xend life cycle management patches were posted by Alistair a couple of months back.