Please forgive the unorthodox posting, but some marketing genius here has
decided I need a new corporate email address and has duly changed my outgoing
email without adequate notice to amend listserve subscriptions. The result is a
lot of unexpected bounces from R-help and R-devel. I'll try to f
Thanks. figured as much and submitted
On Thu, Jun 23, 2011 at 10:16 AM, Sascha Vieweg wrote:
> On 11-06-22 22:12, steven mosher wrote:
>
> I'm preparing to submit my first package to CRAN, thanks to the help of
>> too many people to mention.
>>
>
> [...]
>
>
> My package is pure R with no sour
On 11-06-22 22:12, steven mosher wrote:
I'm preparing to submit my first package to CRAN, thanks to the
help of too many people to mention.
[...]
My package is pure R with no source from other languages. My
questions are as follows. I've read the docs and just need a bit
of clarification.
The workaround is to use the package's namespace, as you did. That's
one of the reasons why pkgname is an argument to .onLoad().
Depending on what you want to do, you can either use the namespace as an
argument where= or get the class definition from the namespace and use
it in place of the c
Thank you david.. with R CMD build --binary I was seeing the deprecated
warning
On Wed, Jun 22, 2011 at 4:51 PM, David Scott wrote:
> On 23/06/11 08:34, Christophe Dutang wrote:
>
>> Hi,
>>
>> By default, R CMD build makes sources, you have to use --binary if you
>> want to get binaries. But
Hi,
I am facing with a strange behaviour of isClass and extends when these
are called in .onLoad in both R 2.12.1 and R 2.13.0. This is preventing
my package from doing some object initializations at a proper place
(i.e. in .onLoad).
Suppose one defines two S4 classes in a package, and that
