You might also find many of the tools provided in the 'session'
package helpful for interacting with R in this way.
'session' package description:
Utility functions for interacting with R processes from external
programs. This package includes functions to save and restore session
informat
On Tue, 2007-12-11 at 10:30 +, Prof Brian Ripley wrote:
> I think everyone who commented has overlooked that the defaults for these
> postscript() arguments are set by ps.options(), so in fact we are talking
> about the defaults for the defaults. Unfortunately, the documentation on
> this
Bjarni Juliusson wrote:
> Prof Brian Ripley wrote:
>
>> On Tue, 11 Dec 2007, Bjarni Juliusson wrote:
>>
>>> I'm developing R integration for a project called Bioclipse at Uppsala
>>> University. The current implementation works by simply forking an R and
>>> sending it text (with some subst
Here is my current understanding: this area has changed a bit recently.
S4 generics of the same name in different packages are regarded as
different. If you define a generic show() in your package, it will not
have any of the methods defined on methods::show, and likely mask the
latter. So use
Agreed. It turns out a similar hack is done in the lme4
package for printMer ...
Martin Morgan wrote:
> Ben --
>
> My vote would be against overriding the generic for show. If for some
> reason your version proves inadequate, you force the user to
> (conditional on loading your package) disamb
Ben --
My vote would be against overriding the generic for show. If for some
reason your version proves inadequate, you force the user to
(conditional on loading your package) disambiguate 'show' to get the
methods package behavior.
?show says in part
Formal methods for 'show' will usually
Prof Brian Ripley wrote:
> I don't think that is the right fix. All methods for min/max should
> now support na.rm=3DTRUE (but not finite=3DTRUE), so range.default shou=
ld
> just call min and max with that argument.
>
> I'd need to verify those 'should's first
>
OK, that why I didn't touch t
I don't think that is the right fix. All methods for min/max should now
support na.rm=TRUE (but not finite=TRUE), so range.default should just
call min and max with that argument.
I'd need to verify those 'should's first
Brian
On Tue, 11 Dec 2007, Peter Dalgaard wrote:
> (Drats! Jitterb
(Drats! Jitterbug is playing tricks with the PR# again. Attempting to
refile so that we can kill PR#10509)
Peter Dalgaard wrote:
> [EMAIL PROTECTED] wrote:
> =20
>> --- Start of forwarded message ---
>> Date: Tue, 13 Nov 2007 21:44:57 +0100
>> To: Steve Mongin <[EMAIL PROTECTED]>
>> Cc: [
Prof Brian Ripley wrote:
> On Tue, 11 Dec 2007, Bjarni Juliusson wrote:
>> I'm developing R integration for a project called Bioclipse at Uppsala
>> University. The current implementation works by simply forking an R and
>> sending it text (with some substitutions on it) down a pipe, getting the
>>
(Drats! Jitterbug is playing tricks with the PR# again. Attempting to
refile so that we can kill PR#10509)
Peter Dalgaard wrote:
> [EMAIL PROTECTED] wrote:
>
>> --- Start of forwarded message ---
>> Date: Tue, 13 Nov 2007 21:44:57 +0100
>> To: Steve Mongin <[EMAIL PROTECTED]>
>> Cc: [EM
[EMAIL PROTECTED] wrote:
> --- Start of forwarded message ---
> Date: Tue, 13 Nov 2007 21:44:57 +0100
> To: Steve Mongin <[EMAIL PROTECTED]>
> Cc: [EMAIL PROTECTED]
> Subject: Re: range( , na.rm =3D TRUE )
> In-Reply-To: <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> From: Kurt Hornik
[EMAIL PROTECTED] wrote:
> --- Start of forwarded message ---
> Date: Tue, 13 Nov 2007 21:44:57 +0100
> To: Steve Mongin <[EMAIL PROTECTED]>
> Cc: [EMAIL PROTECTED]
> Subject: Re: range( , na.rm = TRUE )
> In-Reply-To: <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> From: Kurt Hornik <[
On Tue, 11 Dec 2007, Bjarni Juliusson wrote:
> Hi list!
>
> I'm developing R integration for a project called Bioclipse at Uppsala
> University. The current implementation works by simply forking an R and
> sending it text (with some substitutions on it) down a pipe, getting the
> printed output b
--- Start of forwarded message ---
Date: Tue, 13 Nov 2007 21:44:57 +0100
To: Steve Mongin <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Subject: Re: range( , na.rm = TRUE )
In-Reply-To: <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
From: Kurt Hornik <[EMAIL PROTECTED]>
X-AntiVirus: checked by
Hi list!
I'm developing R integration for a project called Bioclipse at Uppsala
University. The current implementation works by simply forking an R and
sending it text (with some substitutions on it) down a pipe, getting the
printed output back up another pipe. This of course works fine, except
I think everyone who commented has overlooked that the defaults for these
postscript() arguments are set by ps.options(), so in fact we are talking
about the defaults for the defaults. Unfortunately, the documentation on
this was full of errors, including not pointing out that some of the
ps.o
Thanks, Chuck. Very nice! :-)
Jay
On 12/10/07, Charles C. Berry <[EMAIL PROTECTED]> wrote:
>
> On Mon, 10 Dec 2007, G. Jay Kerns wrote:
>
> > Hello,
> >
> > I have been interested in setdiff() for data frames that operates
> > row-wise. I looked in the documentation, mailing lists, etc., and
> >
The default generic method for "show" has arguments
show(object) -- (no "...") -- which precludes any kind
of arguments like "digits", etc.
Is it impossible, or a horrible idea, to override the
generic definition? (The "arm" package has defined a
new generic, "display", which does a simila
19 matches
Mail list logo
