On 7/25/06, Prof Brian Ripley <[EMAIL PROTECTED]> wrote:
> The issue is that system() on Windows does not run a shell, so piping is
> not going to be available: used shell() instead. Then the problem is
> that the shell available is OS-specific, and pretty minimal on Windows
> 95/98/ME. If you c
The issue is that system() on Windows does not run a shell, so piping is
not going to be available: used shell() instead. Then the problem is
that the shell available is OS-specific, and pretty minimal on Windows
95/98/ME. If you can ignore those (and they are getting rarer), cmd.exe
can be
On 7/25/06, Robin Hankin <[EMAIL PROTECTED]> wrote:
> Hi
>
> I'm developing an R package that
> needs to execute some code written in pari/gp.
>
> I've used this before from an R package (elliptic) but the interface
> is very
> basic: the R function creates a string such as the following:
>
> strin
On Windows XP either of these work under R. Here echo and findstr
are builtin Windows commands but you could substitute others:
system("cmd /c echo abc | findstr a", intern = TRUE)
shell("echo abc | findstr a", intern = TRUE)
If its necessary to special case it then note that the
R variabl
Hi
I'm developing an R package that
needs to execute some code written in pari/gp.
I've used this before from an R package (elliptic) but the interface
is very
basic: the R function creates a string such as the following:
string <- echo ' ellwp ([ 2+0*I , 0+2*I ], 1+0*I )' | gp -q
And then
s
