On Wed, 15 Feb 2006, Prof Brian Ripley wrote:
> Torsten,
>
> The error is that .__S3MethodsTable__. ends up in the global environment.
> Are you importing sctest (I can't see it)? I think that's the problem.
>
yes. But `strucchange' has no namespace and so I can't import `sctest' in
the NAMESP
Follow up:
You said
>> which is exported in party's namespace
>>
>> S3method(sctest, mob)
but that's not true: it is registered not exported. You need to export it
as strucchange does not have a namespace.
On Wed, 15 Feb 2006, Prof Brian Ripley wrote:
> Torsten,
>
> The error is that ._
On Wed, 15 Feb 2006, Prof Brian Ripley wrote:
> Follow up:
>
> You said
>
>>> which is exported in party's namespace
>>>
>>> S3method(sctest, mob)
>
> but that's not true: it is registered not exported. You need to export it
> as strucchange does not have a namespace.
>
export(sctes
Torsten,
The error is that .__S3MethodsTable__. ends up in the global environment.
Are you importing sctest (I can't see it)? I think that's the problem.
>From R-exts:
The standard method for S3-style @code{UseMethod} dispatching might fail
to locate methods defined in a package that is importe
Good morning,
we recently observed a problem with importing S3 generics from a foreign
package (without namespace), defining a S3 method in a package _with_
namespace and the `cleanEx()' function which is automatically generated
and executed before examples are run by R CMD check.
To be more
