I must have missed this, thank you.
Good night
Christian
Benilton Carvalho wrote:
> Biobase itself does.
> b
>
> On Mar 16, 2007, at 7:43 PM, cstrato wrote:
>
>> Thank you, I have already read the R-exts manual, but the collate
>> field is optional.
>> Do you know a package which uses the Collat
Biobase itself does.
b
On Mar 16, 2007, at 7:43 PM, cstrato wrote:
> Thank you, I have already read the R-exts manual, but the collate
> field is optional.
> Do you know a package which uses the Collate field so that I can
> study it?
>
> Best regards
> Christian
>
> Benilton Carvalho wrote:
Thank you, I have already read the R-exts manual, but the collate field
is optional.
Do you know a package which uses the Collate field so that I can study it?
Best regards
Christian
Benilton Carvalho wrote:
> The Collate field gives the order that the files are going to be
> concatenated. If t
The Collate field gives the order that the files are going to be
concatenated. If they're concatenated using the "wrong" order, your
installation might fail (for example, the generic is defined after
the method).
A recommended source is the "Writing R Extensions"
http://cran.r-project.org/
I agree, but I hope that "AllGeneric.R" is not the only possibility.
BTW, what is a collate field?
Best regards
Christian
Benilton Carvalho wrote:
> Well, my understanding is that if you "need" to define it (the
> generic) twice you're doing something wrong.
>
> Do you have a collate field in yo
Well, my understanding is that if you "need" to define it (the
generic) twice you're doing something wrong.
Do you have a collate field in your description file? IMHO, the
"AllGeneric.R"/"AllClasses.R" approach is the way to go... keeping
your code organized is always a good thing, right?
b
Dear Benilton
Yes, but the error disappears only when I define it twice.
For my package I create three files:
1. MyClasses.R:
Here I define the classes only using
setClass("baseClass")
setClass("derivedClass")
2. methods.baseClass.R
Here I define the methods for baseClass
setGeneric("export", f
do you have a generic for 'export'?
On Mar 16, 2007, at 5:38 PM, cstrato wrote:
> Dear Benilton
>
> Thank you, now my package works.
>
> Do you have an explanation for my second problem:
>
> * Installing *source* package 'mytest' ...
> ** R
> ** save image
> Error in setMethod("export", "derivedC
Dear Benilton
Thank you, now my package works.
Do you have an explanation for my second problem:
* Installing *source* package 'mytest' ...
** R
** save image
Error in setMethod("export", "derivedClass", export.derivedClass) :
no existing definition for function "export"
Error: unable to
your namespace probably contains:
useDynLib(testS4)
but you don't have any compiled code...
remove that line and everything will be fine.
btw, if you're playing with S4, you must import 'methods'
b
On Mar 16, 2007, at 4:55 PM, cstrato wrote:
> Dear all,
>
> Currently, I am trying to create a
Dear all,
Currently, I am trying to create a test package "testS4" using S4 classes,
which I am attaching.
Running R CMD check gives the following error:
coeurebooks-computer:/Volumes/CoreData/CRAN cs$ R CMD check
testS4_0.1.1.tar.gz
* checking for working latex ...sh: line 1: latex: command
11 matches
Mail list logo
