Thu, 26 May 2005 12:09:23 +0200
Christophe Pouzat <[EMAIL PROTECTED]> wrote.
> Hi,
>
> here is the "configure" command line I used for an Intel PIV processor
> with icc, ifort and the intel mkl:
(snip)
> In my experience using "FPICFLAGS=-shared" is mendatory to get the
> compilation working. Th
> "PD" == Peter Dalgaard <[EMAIL PROTECTED]>
> on 28 Jun 2005 14:57:42 +0200 writes:
PD> "Liaw, Andy" <[EMAIL PROTECTED]> writes:
>> The issue is not with boxplot, but with split. boxplot.formula()
>> calls boxplot(split(split(mf[[response]], mf[-response]), ...),
>>
On Fri, 1 Jul 2005, Kurt Hornik wrote:
>> Robin Hankin writes:
>
>> Professor Ripley
>> On Jul 1, 2005, at 02:58 pm, Prof Brian Ripley wrote:
>
>>> Search for uses of Rcomplex in package source code. The only
>>> packages on CRAN which use it are ifs and rimage.
>
>
>> Thank you for this
> Robin Hankin writes:
> Professor Ripley
> On Jul 1, 2005, at 02:58 pm, Prof Brian Ripley wrote:
>> Search for uses of Rcomplex in package source code. The only
>> packages on CRAN which use it are ifs and rimage.
>>>
> Thank you for this: either is perfect for my purposes. How did yo
Professor Ripley
On Jul 1, 2005, at 02:58 pm, Prof Brian Ripley wrote:
> Search for uses of Rcomplex in package source code. The only
> packages on CRAN which use it are ifs and rimage.
>>
Thank you for this: either is perfect for my purposes. How did you
search the
packages' source code?
Search for uses of Rcomplex in package source code. The only packages on
CRAN which use it are ifs and rimage.
On Fri, 1 Jul 2005, Robin Hankin wrote:
> Hi
>
> one of my packages has a severe bottleneck at a particular function
> and I
> suspect that replacing the R code with C code would spee
On Fri, 1 Jul 2005, Oleg Sklyar wrote:
> Dear community,
>
> this is just a suggestion, but might be useful for the following R
> releases.
It might be useful for future suggestions if you read the relevant manual
before posting. The developers are way ahead of you on this one.
> I was program
Hi
one of my packages has a severe bottleneck at a particular function
and I
suspect that replacing the R code with C code would speed it up.
The function takes complex arguments and returns a complex value.
I would like to follow Best Practice here. None of the C code in my
packages includes
Dear community,
this is just a suggestion, but might be useful for the following R
releases.
I was programming some C code for R and my compiler constantly showed me
some crazy messages that a stdc++ macro length() was supplied with 4
arguments whereas only one was required. The problem could be
