> "ashenfluff" == ashenfluff <[EMAIL PROTECTED]>
> on Wed, 22 Oct 2003 22:29:23 +0200 (MET DST) writes:
ashenfluff> Full_Name: Ben K.
ashenfluff> Version: 1.8.0
ashenfluff> OS: win2k
ashenfluff> Submission from: (NULL) (208.243.20.222)
ashenfluff> This fails:
> Peter Dalgaard writes:
> Kurt Hornik <[EMAIL PROTECTED]> writes:
>> > (Argh. The test builds of 1.8.0 were actually against tcl8.0, but
>> > apparently our testing procedures skip any attempt to load the dynlib.
>> > Automated tests of tcl/tk are difficult because Tk will protest if
>> > the
> maechler writes:
> "Duncan" == Duncan Murdoch <[EMAIL PROTECTED]>
> on Wed, 22 Oct 2003 08:17:32 -0400 writes:
Duncan> I've now tried the code
> set.seed(1)
> x <- rnorm(50)
> y <- rnorm(50)
> cor.test(x,y,method="spearman")
> x <- rnorm(50)
> y <- rnorm(50)
> cor.test
Kurt Hornik <[EMAIL PROTECTED]> writes:
> > maechler writes:
>
> > "Duncan" == Duncan Murdoch <[EMAIL PROTECTED]>
> > on Wed, 22 Oct 2003 08:17:32 -0400 writes:
>
> Duncan> I've now tried the code
>
> > set.seed(1)
> > x <- rnorm(50)
> > y <- rnorm(50)
> > cor.test(x,y,met
Kurt Hornik <[EMAIL PROTECTED]> writes:
> > maechler writes:
>
> > "Duncan" == Duncan Murdoch <[EMAIL PROTECTED]>
> > on Wed, 22 Oct 2003 08:17:32 -0400 writes:
>
> Duncan> I've now tried the code
>
> > set.seed(1)
> > x <- rnorm(50)
> > y <- rnorm(50)
> > cor.test(x,y,met
> Peter Dalgaard writes:
> Kurt Hornik <[EMAIL PROTECTED]> writes:
>> > maechler writes:
>>
>> > "Duncan" == Duncan Murdoch <[EMAIL PROTECTED]>
>> > on Wed, 22 Oct 2003 08:17:32 -0400 writes:
>>
Duncan> I've now tried the code
>>
>> > set.seed(1)
>> > x <- rnorm(50)
>> >
> Peter Dalgaard writes:
> Kurt Hornik <[EMAIL PROTECTED]> writes:
>> > maechler writes:
>>
>> > "Duncan" == Duncan Murdoch <[EMAIL PROTECTED]>
>> > on Wed, 22 Oct 2003 08:17:32 -0400 writes:
>>
Duncan> I've now tried the code
>>
>> > set.seed(1)
>> > x <- rnorm(50)
>> >
[EMAIL PROTECTED] writes:
> > Probably, but of a nasty kind which I think we need to get to the
> > bottom of. As I see it there are two possible causes
>
> > 1. A bug in a Windows library or compiler. Potentially that could
> >affect everything else.
> > 2. A bug in ctest that just happens o
On 23 Oct 2003, Peter Dalgaard wrote:
> [EMAIL PROTECTED] writes:
>
> > > Probably, but of a nasty kind which I think we need to get to the
> > > bottom of. As I see it there are two possible causes
> >
> > > 1. A bug in a Windows library or compiler. Potentially that could
> > >affect every
On 23 Oct 2003, Peter Dalgaard wrote:
> [EMAIL PROTECTED] writes:
>
> > > Probably, but of a nasty kind which I think we need to get to the
> > > bottom of. As I see it there are two possible causes
> >
> > > 1. A bug in a Windows library or compiler. Potentially that could
> > >affect every
I encountered several strange issues when linking to R.dll on Windows
and I wonder if anyone of the Windows savvy-folks here had seen some of
the issues before and have some explanation.
My Rserve links to R dynamic library. That works perfectly on unix
boxes and worked fairly well with older M
(RFC := Request For Comments)
> "Tim" == Tim Keighley <[EMAIL PROTECTED]>
> on Thu, 23 Oct 2003 11:45:22 +1000 writes:
Tim> Hi Martin,
Tim> In October 2000 you wrote to r-help:
>>> which reminds me that I've had a desire for something like
>>> the old S function [from
I was told that direct linking against foo.dll is not supported. One
problem is that the link priority order gets broken, and R.dll gets used
for things it should not be used for (malloc springs to mind).
You should be able to use libR.a, though. It does not need to export
R_Home, as you should
> Martin Maechler writes:
> (RFC := Request For Comments)
My preference would be that we start by adding a version of sscanf().
-k
> "Tim" == Tim Keighley <[EMAIL PROTECTED]>
> on Thu, 23 Oct 2003 11:45:22 +1000 writes:
Tim> Hi Martin,
Tim> In October 2000 you wrote to r-help:
I have encountered an issue while preparing some of the Bioconductor
packages for our upcoming release, and Duncan Murdoch suggested that I
bring one of the related points up here.
The background is that we are building our packages under Windows with
"Rcmd install --build" which will flag the zi
Jeff Gentry wrote:
...
The issue that Duncan suggested I raise is whether or not it should be
considered accepted behaviour for a package author to be accessing files
in \data (at this time I don't know the reasoning behind the specific
example here, I just know that that's what they've done) or i
On Thu, 23 Oct 2003, Paul Gilbert wrote:
> Jeff Gentry wrote:
>
> >...
> >The issue that Duncan suggested I raise is whether or not it should be
> >considered accepted behaviour for a package author to be accessing files
> >in \data (at this time I don't know the reasoning behind the specific
> >
I am currently writing a (private) package in which I produce pdf
files from within R using LaTeX. To do so I mainly copied some lines
from the buildVignettes() function in the tools package. This uses the
texi2dvi which is included in R's bin directory:
system(paste(file.path(R.home(), "bin"
Hello.
I'm looking for documentation about the graphic device model in R.
I would understand it in the details, but it seems a bit complex :)
Thanks for any documents which will help me.
Laurent
__
[EMAIL PROTECTED] mailing list
https://www.stat.math.
Last time I tried texi2dvi did not work under the shell used under
Windows.
On Thu, 23 Oct 2003, Achim Zeileis wrote:
> I am currently writing a (private) package in which I produce pdf
> files from within R using LaTeX. To do so I mainly copied some lines
> from the buildVignettes() function
On Thu, 23 Oct 2003 14:21:08 +0200, you wrote:
>I encountered several strange issues when linking to R.dll on Windows
>and I wonder if anyone of the Windows savvy-folks here had seen some of
>the issues before and have some explanation.
I can help with one of them, but not the main one.
>Now,
Hi
[EMAIL PROTECTED] wrote:
Hello.
I'm looking for documentation about the graphic device model in R.
I would understand it in the details, but it seems a bit complex :)
Thanks for any documents which will help me.
I'm assuming you want to write a new device ...
Here are a couple of places to l
I'm assuming you want to write a new device ...
Yes. I plan to write a GLX device. The rgl package writed by Daniel Adler
is very interesting but don't correspond to what I want.
I want to write a full device, based on X11 at first, then add specific
features for 3D representation.
Here are a cou
Hot Pennies.net Special Situation Alert
Watch This Stock Trade!!!
STOCK DETAILS
Symbol: IPFS
Exchange: OTCBB
Shares Outstanding: 13,379,000
Current Price: $1.10
Industry: Wireless Manufacturing and Technology
COMPANY DETAILS
Integrated Performance Systems
Hi all,
> The issue that Duncan suggested I raise is whether or not it should be
> considered accepted behaviour for a package author to be accessing files
> in \data (at this time I don't know the reasoning behind the specific
> example here, I just know that that's what they've done) or if this
On Fri, 24 Oct 2003 [EMAIL PROTECTED] wrote:
> > The issue that Duncan suggested I raise is whether or not it should be
> > considered accepted behaviour for a package author to be accessing files
> > in \data (at this time I don't know the reasoning behind the specific
> > example here, I just kn
A couple of weeks back there was some discussion about documenting the
regular expressions as used in R. Several years ago the problem was that
this was OS-dependent, and to plug that problem we incorporated regexp
code from a version of GNU grep, later updated to grep-2.4.2 in R 1.2.0.
I hav
27 matches
Mail list logo
