Re: [Rd] Reference Classes: removing methods -> implications for objects/instances of that class

2010-11-27 Thread Vitalie S.
"Janko Thyson" writes: > Dear list, > > just to make sure that I understand 'unregistering' methods for S4 reference > classes correctly: > > If I registered a method and want to 'unregister' (i.e. remove) this method > again, objects/instance created of the respective class still feature the > r

Re: [Rd] Ref classes: can I register fields as I register methods?

2010-11-27 Thread Vitalie S.
John Chambers writes: > Well, it's an interesting idea, and the current implementation would fit with > it. > > One catch is that it goes against any obvious notion of checking for valid > objects (admittedly, there are some difficulties in that already with active > bindings being used). > > Ano

[Rd] Bug in parseNamespaceFile or switch( , ... ) ?

2010-11-27 Thread Charles C. Berry
parseNamespaceFile() doesn't seem to detect misspelled directives. Looking at its code I see switch(as.character(e[[1L]]), , stop(gettextf("unknown namespace directive: %s", deparse(e)), call. = FALSE, domain = NA)) but this doesn't seem to function a

Re: [Rd] Bug in parseNamespaceFile or switch( , ... ) ?

2010-11-27 Thread Duncan Murdoch
On 27/11/2010 5:58 PM, Charles C. Berry wrote: parseNamespaceFile() doesn't seem to detect misspelled directives. Looking at its code I see switch(as.character(e[[1L]]), , stop(gettextf("unknown namespace directive: %s", deparse(e)), call. = FALSE, do

Re: [Rd] Bug in parseNamespaceFile or switch( , ... ) ?

2010-11-27 Thread Duncan Murdoch
On 27/11/2010 6:50 PM, Duncan Murdoch wrote: On 27/11/2010 5:58 PM, Charles C. Berry wrote: parseNamespaceFile() doesn't seem to detect misspelled directives. Looking at its code I see switch(as.character(e[[1L]]), , stop(gettextf("unknown namespace directive: %s",