Displaying 5 results from an estimated 5 matches for "rmumps".
2017 May 15
3
stopifnot() does not stop at first non-TRUE argument
.../05/2017 ? 12:48, Serguei Sokol a ?crit :
> Hello,
>
> I am a new on this list, so I introduce myself very briefly:
> my background is applied mathematics, more precisely scientific calculus
> applied for modeling metabolic systems, I am author/maintainer of
> few packages (Deriv, rmumps, arrApply).
>
> Now, on the subject of this discussion, I must say that I don't really understand
> Peter's argument:
>
> >>> To do it differently, you would have to do something like
> >>>
> >>> dots <- match.call(expand.dots=F...
2017 May 15
2
stopifnot() does not stop at first non-TRUE argument
>>>>> Herv? Pag?s <hpages at fredhutch.org>
>>>>> on Wed, 3 May 2017 12:08:26 -0700 writes:
> On 05/03/2017 12:04 PM, Herv? Pag?s wrote:
>> Not sure why the performance penalty of nonstandard evaluation would
>> be more of a concern here than for something like switch().
> which is actually a primitive. So it seems that
2017 May 15
0
stopifnot() does not stop at first non-TRUE argument
Hello,
I am a new on this list, so I introduce myself very briefly:
my background is applied mathematics, more precisely scientific calculus
applied for modeling metabolic systems, I am author/maintainer of
few packages (Deriv, rmumps, arrApply).
Now, on the subject of this discussion, I must say that I don't really understand
Peter's argument:
>>> To do it differently, you would have to do something like
>>>
>>> dots <- match.call(expand.dots=FALSE)$...
>>>...
2017 May 15
0
stopifnot() does not stop at first non-TRUE argument
...;> Hello,
>>
>> I am a new on this list, so I introduce myself very briefly:
>> my background is applied mathematics, more precisely scientific calculus
>> applied for modeling metabolic systems, I am author/maintainer of
>> few packages (Deriv, rmumps, arrApply).
>>
>> Now, on the subject of this discussion, I must say that I don't really understand
>> Peter's argument:
>>
>> >>> To do it differently, you would have to do something like
>> >>>
>> &g...
2017 May 15
3
stopifnot() does not stop at first non-TRUE argument
...t;
> >> I am a new on this list, so I introduce myself very briefly:
> >> my background is applied mathematics, more precisely scientific calculus
> >> applied for modeling metabolic systems, I am author/maintainer of
> >> few packages (Deriv, rmumps, arrApply).
> >>
> >> Now, on the subject of this discussion, I must say that I don't really understand
> >> Peter's argument:
> >>
> >> >>> To do it differently, you would have to do something like
> >...