Thanks again all. Essentially, this is the section of the code that is
causing trouble. This is part of the (exported) function which calls
contr.none (not exported). As mentioned, when I call the exported function
it complains with the error described before.
oldcontrasts <- unlist(options("co
Thanks Gabriel. Your explanation is very clear.
Seeing the example above, I made a mistake. If I export(timestwo) (and not
multiply), then calling timestwo in the package works fine.
However, in my real package I have a situation like the above:
contr.none <- function(n, contrasts) {
if (leng
Hi,
I'm trying to make sense of the output of getParseData(). The "parent" column
is supposed to refer to the "id" of the parent of the given item, but there are
numbers in the parent column that do not exist in the id column. Example:
> p <- parse(text="f<-function(){if(TRUE)1 else 2}")
> df <
On 14-01-25 2:47 PM, Axel Urbiz wrote:
Thanks Dirk. Sorry...It's my misunderstanding about "export" in the
NAMESPACE then. Essentially, as I understand it now, I should export all
functions that are used in the package? Why would I not export a certain
function?
In the example above, say I wante
I haven't seen all of your code, but are you using get to obtain the object
yourself? If so, that is likely your problem, as that is (roughly)
equivalent to typing the name at the prompt, it won't see unexported
functions. It shouldn't be necessary to do, though.
contrasts = switch(ctr,
"contr.non
Axel,
R CMD check and CRAN's submission guidelines do not allow undocumented
*user facing* (i.e. exported) functions or objects in packages.
If you want the users of your package to be able calling the timestwo
function directly, it needs to be documented (and exported).
If, on the other hand, t
Thanks Dirk. Sorry...It's my misunderstanding about "export" in the
NAMESPACE then. Essentially, as I understand it now, I should export all
functions that are used in the package? Why would I not export a certain
function?
In the example above, say I wanted to avoid documenting the function
"time
Dirk and Uwe, many thanks both for your responses. I'm still having the
same issue. Here's in more detail:
As Dirk suggested, I've done the following:
* I've created a package named {foo}.
* {foo} only has one file named test.R which includes exactly the following
code:
multiply <- function(x,y
On 25 January 2014 at 20:26, Axel Urbiz wrote:
| Dirk and Uwe, many thanks both for your responses. I'm still having the same
| issue. Here's in more detail:
|
| As Dirk suggested, I've done the following:
|
| * I've created a package named {foo}.
|
| * {foo} only has one file named test.R whi
On 25.01.2014 14:53, Dirk Eddelbuettel wrote:
On 25 January 2014 at 14:38, Axel Urbiz wrote:
| Hello,
|
| I'm building a package. My code is stored in foo.R. This code has two
| functions FUN1 and FUN2. FUN1 calls FUN2. FUN1 is listed in export() under
| the package NAMESPACE but NOT FUN2. Aft
On 25 January 2014 at 14:38, Axel Urbiz wrote:
| Hello,
|
| I'm building a package. My code is stored in foo.R. This code has two
| functions FUN1 and FUN2. FUN1 calls FUN2. FUN1 is listed in export() under
| the package NAMESPACE but NOT FUN2. After building the package when I call
| FUN1 is giv
Hello,
I'm building a package. My code is stored in foo.R. This code has two
functions FUN1 and FUN2. FUN1 calls FUN2. FUN1 is listed in export() under
the package NAMESPACE but NOT FUN2. After building the package when I call
FUN1 is giving me an error that cannot find FUN2.
I solved this by add
Hi Sandip,
you are right on SUSE 11 I found Fortran 4.3 but I installed also Fortran
3.3 and tried to install R under gcc33 with compilation errors.
After this I installed after an advice from Prof Brian R 2.2 (old Version
from 2005) and got the same problems with gcc33 and gcc.
after the comman
13 matches
Mail list logo
