Full_Name: Maria Rizzo
Version: 2.10.1 (2009-12-14)
OS: Windows XP SP3
Submission from: (NULL) (72.241.75.222)
platform i386-pc-mingw32
arch i386
os mingw32
system i386, mingw32
statu
Looking at shash in unique.c, from R-2.10.1 I'm wondering if it makes sense
to hash the pointer itself rather than the string it points to?
In other words could the SEXP pointer be cast to unsigned int and the usual
scatter be called on that as if it were integer?
shash would look like a sligh
On 20.02.2010 00:04, Paul Johnson wrote:
On Thu, Feb 18, 2010 at 2:20 PM, Jens Elkner wrote:
On Thu, Feb 18, 2010 at 11:33:14AM -0600, Paul Johnson wrote:
I'm pursuing an experiment to make RPM files for R packages
on-the-fly. Any time I install an R package successfully, I want to
wrap up t
I am trying to compile R on Linux using SunStudio. Configure flags are
mostly as suggested in the R install guide.
CC=/opt/sun/sunstudio12.1/bin/suncc
CFLAGS="-g -xc99 -xlibmil -xlibmieee"
MAIN_CFLAGS=-g
SHLIB_CFLAGS=-g
CPPFLAGS="-I. -I/opt/sun/sunstudio12.1/prod/include
-I/opt/sun/sunstudio12.1/p
The following seems to me to be at least a perverse trap, if not an =
outright
bug:
> is.numeric(unit(1,"npc"))
[1] TRUE
> is.numeric(1*unit(1,"npc"))
[1] FALSE
> is.numeric(unit(0,"npc") +unit(1,"npc"))
[1] FALSE
...etc.
i.e. is.numeric() appears to be TRUE for class "unit" but false for =
class
clang is compiler http://clang.llvm.org, it is fast and better c compiler then
gcc, yesterday i use clang and gfortran compile R.
The only two change in source code is :
1. the configure file (in confiure when test include wctype.h,gcc can compile
but clang need include both wchar.h wctype.h),so
Hi all,
I'm hoping someone could tell me what best practices are as far as
keeping programs organized in R. In most languages, I like to keep
things organized by writing small functions. So, suppose I want to
write a function that would require helper functions or would just be
too big to write
On 22/02/2010 9:49 PM, Ben wrote:
Hi all,
I'm hoping someone could tell me what best practices are as far as
keeping programs organized in R. In most languages, I like to keep
things organized by writing small functions. So, suppose I want to
write a function that would require helper function
As you mention ease of debugging basically precludes subfunctions so
style 1 is left.
Functions can be nested in environments rather than in other functions
and this will allow debugging to still occur.
The proto package which makes it particularly convenient to nest
functions in environments giv
Ben--
FWIW my general take on this is:
- Namespaces solve the collision issue.
- Style 2 tends to make for unreadably long code inside Foo, unless the
subfunctions are really short.
- Style 3 is too hard to work with
- So I usually use a variant on style 1:
### Style 4 (m
configure is a generated file, and so should not be edited directly.
You have not told us what version of R these patches were against, but
it looks to me as if wchar.h is included already in current R
(R-patched/R-devel) -- certainly in the second case before wctype.h.
(It really should not be
11 matches
Mail list logo
