Re: [Rd] Hello! I got error in C - R

2009-04-02 Thread Mathieu Ribatet
Dear Ick Hoon Jin, Your problem is probably due to a misspecification in memory allocation within your C code. To solve this you can: * check by yourself whenever there is C memory allocation - by the way I think it's best to use R memory allocation i.e. R_alloc * use valgrind

[Rd] Hello! I got error in C - R

2009-04-02 Thread kentjin
Hello, My name is Ick Hoon Jin and I am Ph. D. student in Texas A & M Univ.. When I run the C embedded in R in the Linux system, I confront the following error after 6,000 iteration. By googling I found this error is from the problem in C. *** caught segfault *** address (nil), cause 'memory not m

Re: [Rd] Compiler options for Makefile.win

2009-04-02 Thread cstrato
Dear Gabor, Thank you for your suggestion. I forgot to mention that the build process ended with the following dialog box: Runtime Error! Program: c:\Programme\R\R-2.9.0alpha\bin\Rterm.exe R6034 An application has made an attempt to load the C runtime library incorrectly. Please contact the

Re: [Rd] Compiler options for Makefile.win

2009-04-02 Thread cstrato
Dear Uwe, My problem is that this is the only mailing list I know where to ask this question, since this problem is definitely related to R. When I compile my source code as stand alone library using NMAKE then both compiler options, /MD and /MT, work fine and I can use the compiled library

Re: [Rd] what is the preferred method to create a package local variable?

2009-04-02 Thread Duncan Murdoch
On 4/2/2009 9:41 AM, Whit Armstrong wrote: Thanks to everyone for the suggestions. The package local environment (per Roger Peng) works well. .localstuff <- new.env() .localstuff$bbg.db.conn <- dbConnect(...) However, there is one thing that I'm confused about. Why must the .localstuff variabl

Re: [Rd] what is the preferred method to create a package local variable?

2009-04-02 Thread Duncan Murdoch
On 4/2/2009 9:49 AM, Roger Peng wrote: The use of an environment gets around the fact that package namespaces are locked, so that values can't be changed once the package is loaded. However, elements of environments can be changed. Oops, I forgot about that. So use a NAMESPACE plus an environm

Re: [Rd] what is the preferred method to create a package local variable?

2009-04-02 Thread Whit Armstrong
aha! Now it makes sense. Thanks, Roger. -Whit On Thu, Apr 2, 2009 at 9:49 AM, Roger Peng wrote: > The use of an environment gets around the fact that package namespaces > are locked, so that values can't be changed once the package is > loaded. However, elements of environments can be changed

Re: [Rd] what is the preferred method to create a package local variable?

2009-04-02 Thread Roger Peng
The use of an environment gets around the fact that package namespaces are locked, so that values can't be changed once the package is loaded. However, elements of environments can be changed. -roger On Thu, Apr 2, 2009 at 9:41 AM, Whit Armstrong wrote: > Thanks to everyone for the suggestions.

Re: [Rd] what is the preferred method to create a package local variable?

2009-04-02 Thread Whit Armstrong
Thanks to everyone for the suggestions. The package local environment (per Roger Peng) works well. .localstuff <- new.env() .localstuff$bbg.db.conn <- dbConnect(...) However, there is one thing that I'm confused about. Why must the .localstuff variable be an environment? I've tried the followin

Re: [Rd] actual argument matching does not conform to the definition (PR#13636)

2009-04-02 Thread Waclaw . Marcin . Kusnierczyk
Thomas Lumley wrote: > > The explanation is that quote() is a primitive function and that the > argument matching rules do not apply to primitives. That section of > the R Language definition should say that primitives are excluded; it > is documented in ?.Primitive. thanks. indeed, the documen

Re: [Rd] actual argument matching does not conform to the definition (PR#13634)

2009-04-02 Thread Wacek Kusnierczyk
Thomas Lumley wrote: > > The explanation is that quote() is a primitive function and that the > argument matching rules do not apply to primitives. That section of > the R Language definition should say that primitives are excluded; it > is documented in ?.Primitive. thanks. indeed, the documen

Re: [Rd] actual argument matching does not conform to the definition (PR#13635)

2009-04-02 Thread tlumley
The explanation is that quote() is a primitive function and that the argument matching rules do not apply to primitives. That section of the R Language definition should say that primitives are excluded; it is documented in ?.Primitive. -thomas On Thu, 2 Apr 2009 w...@idi.ntnu.no wrot

Re: [Rd] actual argument matching does not conform to the definition (PR#13634)

2009-04-02 Thread Thomas Lumley
The explanation is that quote() is a primitive function and that the argument matching rules do not apply to primitives. That section of the R Language definition should say that primitives are excluded; it is documented in ?.Primitive. -thomas On Thu, 2 Apr 2009 w...@idi.ntnu.no wrot

Re: [Rd] Compiler options for Makefile.win

2009-04-02 Thread Gábor Csárdi
On Sun, Mar 29, 2009 at 9:31 PM, cstrato wrote: [...] > - - - - - - - - > Created c:\home\Rabbitus\CRAN\xps\chm\xps.chm, 166,306 bytes > Compression decreased file by 442,726 bytes. > ** building package indices ... > ** MD5 sums > * DONE (xps) > * creating vignettes ...Terminating on signal SIGIN

Re: [Rd] Compiler options for Makefile.win

2009-04-02 Thread Uwe Ligges
I fear the number of R users under Windows that make use of a non-gcc compiler and is reading this list is quite close to 0. Hence you will probably have to find it out yourself. Uwe Ligges cstrato wrote: Dear all, For certain reasons I have to compile the source code of my package on

Re: [Rd] Assignment to string

2009-04-02 Thread Wacek Kusnierczyk
Stavros Macrakis wrote: > On Wed, Apr 1, 2009 at 5:11 PM, Wacek Kusnierczyk < > waclaw.marcin.kusnierc...@idi.ntnu.no> wrote: > > >> Stavros Macrakis wrote: >> ... >> i think this concords with the documentation in the sense that in an >> assignment a string can work as a name. note that >> >>

[Rd] actual argument matching does not conform to the definition (PR#13634)

2009-04-02 Thread waku
Full_Name: Wacek Kusnierczyk Version: 2.10.0 r48269 OS: Ubuntu 8.04 Linux 32 bit Submission from: (NULL) (129.241.199.164) In the following example (and many other cases): quote(a=1) # 1 the argument matching is apparently incorrect wrt. the documentation (The R Language Definition, v 2.8

Re: [Rd] [R] Definition of = vs. <-

2009-04-02 Thread Wacek Kusnierczyk
Wacek Kusnierczyk wrote: > > and btw. the following is also weird: > > quote(a=1) > # 1 > > not because '=' works as named argument specifier (so that the result > would be something like `=`(a, 1)), i meant to write: not because '=' does not work as an assignment operator (or otherwise t

Re: [Rd] [R] Definition of = vs. <-

2009-04-02 Thread Wacek Kusnierczyk
Peter Dalgaard wrote: > Wacek Kusnierczyk wrote: >> Stavros Macrakis wrote: `->` >>> Error: object "->" not found >>> >> >> that's weird! > > Why??? > partly because it was april fools. but more seriously, it's because one could assume that in any syntactic expression with an o