Gabor Grothendieck wrote:
> This is what I get:
>
>> as.missing <- force
>> f <- function(y, x=1) {cat(missing(x)) ; x}
>> g <- function(x=as.missing()) f(3,x)
>> g()
> FALSEError in as.missing() : argument "x" is missing, with no default
>> traceback()
> 3: as.missing()
> 2: f(3, x)
> 1: g()
>> t
Dear R-developers,
I just realized that rank() behaves inconsistent if combining one of na.last in
{TRUE|FALSE} with a ties.method in {"average"|"random"|"max"|"min"}.
The documentation suggests that e.g. with na.last=TRUE NAs are treated like the
last (=highest) value, which obviously is not th
Dear list-subscriber,
in the process of writing a general code snippet to extract coefficients
in an expression (in the example below: 0.5 and -0.7), I stumbled over
the following peculiar (at least peculiar to me:-) ) sorting behaviour
of the function all.names():
> expr1 <- expression(x3 = 0.5
Hi Everyone
I have a function f which does something using a function g. Function f
is in a library and g has a default stub in the library but will be mainly
overloaded in a later R script. For example:
## In a compiled package 'P' #
g <- function() {
cat("Origi
Rewrite
expr2 <- expression(x3 <- 0.5 * x1 - 0.7 * x2)
like this:
expression(`<-`(x3, `-`(`*`(0.5, x1), `*`(0.7, x2
and it becomes clear.
On 10/27/06, Pfaff, Bernhard Dr. <[EMAIL PROTECTED]> wrote:
> Dear list-subscriber,
>
> in the process of writing a general code snippet to extra
Rewrite
expr2 <- expression(x3 <- 0.5 * x1 - 0.7 * x2)
like this:
expr2 <- expression(`<-`(x3, `-`(`*`(0.5, x1), `*`(0.7, x2
and it becomes clear.
On 10/27/06, Pfaff, Bernhard Dr. <[EMAIL PROTECTED]> wrote:
> Dear list-subscriber,
>
> in the process of writing a general code snippet
A problem with callNextMethod, which is caching an inherited method as
if it was not inherited, causing confusion on the next search. Should
be fairly easy to fix, but may be a while before I get time to do so.
By the way, I hope your simplified example does not reflect what happens
in the act
Thanks for the typo, it might have taken a while to find this one otherwise!
In 2.5.0 and 2.4patched, the subclass information attempts to be
complete. That subclass information needs to be removed from all
superclasses when the class is redefined, and currently isn't. The
particular supercla
Bjørn-Helge Mevik wrote:
>Gabor Grothendieck wrote:
>
>
>
>>This is what I get:
>>
>>
>>
>>>as.missing <- force
>>>f <- function(y, x=1) {cat(missing(x)) ; x}
>>>g <- function(x=as.missing()) f(3,x)
>>>g()
>>>
>>>
>>FALSEError in as.missing() : argument "x" is missing, with no defaul
Paul Gilbert <[EMAIL PROTECTED]> writes:
> >I.e., when x is missing in g, and g calls f(3,x), f will use its
> >default value for x.
> >
> >
> Yes, that is the behaviour I am looking for. That is, f should do what
> it normal would do if it were called with x missing.
But if x has a default i
On Fri, 27 Oct 2006 14:49:15 +0100, Paul Roebuck <[EMAIL PROTECTED]>
wrote:
> On Fri, 27 Oct 2006, Tom McCallum wrote:
>
>> I have a function f which does something using a function g. Function f
>> is in a library and g has a default stub in the library but will be
>> mainly
>> overloaded in
Hi,
I use RMySQL to connect to MySQL server where I have a couple of stored
procedures.
I know that the function for the stored procedures "is not yet
implemented", but I was trying to
get around the problem connecting like that:
drv <- dbDriver("MySQL")
con <- dbConnect(drv,user=MyUser, passw
On Fri, 27 Oct 2006 15:54:40 +0100, Tom McCallum <[EMAIL PROTECTED]>
wrote:
> On Fri, 27 Oct 2006 14:49:15 +0100, Paul Roebuck <[EMAIL PROTECTED]>
> wrote:
>
>> On Fri, 27 Oct 2006, Tom McCallum wrote:
>>
>>> I have a function f which does something using a function g. Function
>>> f
>>> is i
On 10/27/2006 10:24 AM, Peter Dalgaard wrote:
> Paul Gilbert <[EMAIL PROTECTED]> writes:
>
>> >I.e., when x is missing in g, and g calls f(3,x), f will use its
>> >default value for x.
>> >
>> >
>> Yes, that is the behaviour I am looking for. That is, f should do what
>> it normal would do if
On Fri, 27 Oct 2006, Henrik Bengtsson wrote:
> In Section "Package subdirectories" in "Writing R Extensions" [2.4.0
> (2006-10-10)] it says:
>
> "Only ASCII characters (and the control characters tab, formfeed, LF
> and CR) should be used in code files. Other characters are accepted in
> comments,
Peter Dalgaard wrote:
>Paul Gilbert <[EMAIL PROTECTED]> writes:
>
>
>
>>>I.e., when x is missing in g, and g calls f(3,x), f will use its
>>>default value for x.
>>>
>>>
>>>
>>>
>>Yes, that is the behaviour I am looking for. That is, f should do what
>>it normal would do if it were ca
On Fri, Oct 27, 2006 at 11:14:25AM +0200, Jens Oehlschl?gel wrote:
> rather, but in fact NAs seem to be always treated ties.method =
> "first". I have no idea in which situation one could desire
> e.g. ties.method = "average" except for NAs!?
Interesting. I was aware of the S-Plus vs. R differen
Duncan Murdoch wrote:
> On 10/27/2006 10:24 AM, Peter Dalgaard wrote:
>
>> Paul Gilbert <[EMAIL PROTECTED]> writes:
>>
>>> >I.e., when x is missing in g, and g calls f(3,x), f will use its
>>> >default value for x.
>>> > >
>>> Yes, that is the behaviour I am looking for. That is, f should do
Paul Gilbert <[EMAIL PROTECTED]> writes:
> Peter Dalgaard wrote:
>
> >Paul Gilbert <[EMAIL PROTECTED]> writes:
> >
> >
> >>>I.e., when x is missing in g, and g calls f(3,x), f will use its
> >>>default value for x.
> >>>
> >> Yes, that is the behaviour I am looking for. That is, f should do
> >>
Peter Dalgaard wrote:
>Paul Gilbert <[EMAIL PROTECTED]> writes:
>
>
>
>>Peter Dalgaard wrote:
>>
>>
>>
>>>Paul Gilbert <[EMAIL PROTECTED]> writes:
>>>
>>>
>>>
>>>
>I.e., when x is missing in g, and g calls f(3,x), f will use its
>default value for x.
>
>
>>>
On 10/26/06, Gabor Grothendieck <[EMAIL PROTECTED]> wrote:
> This is what I get:
>
> > as.missing <- force
> > f <- function(y, x=1) {cat(missing(x)) ; x}
> > g <- function(x=as.missing()) f(3,x)
> > g()
> FALSEError in as.missing() : argument "x" is missing, with no default
> > traceback()
> 3: as
There are lot of subtle issues involved here. We should think through
carefuly exactly what semantics we want for missing value propagation
before making any changes. Making usage easy at top level is
genearlly a good thing, but for usage within functions eliminating
error messages by making more
It occurred to me that we could have an optional file called TESTIMONIALS
that comes with each package which could be a list of short testimonials from
users indicating success with that package and possibly a few details of
the successful application, e.g. it was used to analyse xyz data.
Users w
Hi John,
John Chambers wrote:
> A problem with callNextMethod, which is caching an inherited method as
> if it was not inherited, causing confusion on the next search. Should
> be fairly easy to fix, but may be a while before I get time to do so.
>
> By the way, I hope your simplified example do
Hi,
I have a question about the availability of tarballs for 2.4.0-patched.
I routinely compile and install fresh versions of R-patched as well as
R-devel every few days. I do it mostly "for fun" but also to check for
possible build problems or problems with my development environment
(Win2000,
Full_Name: Earl Kinney
Version: 2.4.0
OS: Red Hat Enterprise Linux 4
Submission from: (NULL) (140.247.116.214)
At HMDC, we make use of the cross building tools to build Windows R libraries on
Linux. Recently when attempting to update the cross building environment to
2.4.0 we encountered a linke
Gabor Grothendieck wrote:
> It occurred to me that we could have an optional file called TESTIMONIALS
> that comes with each package which could be a list of short testimonials from
> users indicating success with that package and possibly a few details of
> the successful application, e.g. it was
Luke Tierney <[EMAIL PROTECTED]> writes:
> There are lot of subtle issues involved here. We should think through
> carefuly exactly what semantics we want for missing value propagation
> before making any changes. Making usage easy at top level is
> genearlly a good thing, but for usage within fu
[EMAIL PROTECTED] writes:
> Hi,
>
> I have a question about the availability of tarballs for 2.4.0-patched.
>
> I routinely compile and install fresh versions of R-patched as well as
> R-devel every few days. I do it mostly "for fun" but also to check for
> possible build problems or problems w
On 10/28/06, Thomas Lumley <[EMAIL PROTECTED]> wrote:
> On Fri, 27 Oct 2006, Henrik Bengtsson wrote:
>
> > In Section "Package subdirectories" in "Writing R Extensions" [2.4.0
> > (2006-10-10)] it says:
> >
> > "Only ASCII characters (and the control characters tab, formfeed, LF
> > and CR) should
Full_Name: Manfred Georg
Version: 2.4.0
OS: linux
Submission from: (NULL) (128.252.166.190)
Hello,
I would like to see a command line flag
--interactive (--no-interactive)
or similar, to explicitly set whether we are in interactive mode on startup
(default, of course, remaining whether input is
hi Jim,
if i partition the file, then for further operation like merging the
partitioned files and after that doing some analysis on whole data set
would again require the same amount of memory. If i am not able to do or
if i am not having memory then i feel there should be serious thinking
o
32 matches
Mail list logo
