Luke Tierney <[EMAIL PROTECTED]> said:
> On Wed, 3 Sep 2008, EBo wrote:
>
> > Luke Tierney <[EMAIL PROTECTED]> said:
> >
> >> ...
> >>> do something like the following:
> >>>
> >>> R_Expr = R_Parse1Buffer(&R_ConsoleIob, 0, &status);
> >>> if (PARSE_OK==status) {
> >>>...
> >>>value = ev
On Wed, 3 Sep 2008, EBo wrote:
Luke Tierney <[EMAIL PROTECTED]> said:
...
do something like the following:
R_Expr = R_Parse1Buffer(&R_ConsoleIob, 0, &status);
if (PARSE_OK==status) {
...
value = eval(R_CurrentExpr, rho);
...
}
We definitely do NOT want this frozen into the publ
Luke Tierney <[EMAIL PROTECTED]> said:
> ...
> > do something like the following:
> >
> > R_Expr = R_Parse1Buffer(&R_ConsoleIob, 0, &status);
> > if (PARSE_OK==status) {
> >...
> >value = eval(R_CurrentExpr, rho);
> >...
> > }
>
> We definitely do NOT want this frozen into the publ
On Wed, 3 Sep 2008, EBo wrote:
While doing some embedded programming and trying to figure out how to generate
a hand coded SEXP equivalent of the line
"t.test(x,conf.level=(1-p))$conf.int[2]" I had an idea for an addition to the
embedded API.
There are a number of hidden or static parse functi
While doing some embedded programming and trying to figure out how to generate
a hand coded SEXP equivalent of the line
"t.test(x,conf.level=(1-p))$conf.int[2]" I had an idea for an addition to the
embedded API.
There are a number of hidden or static parse functions (R_ParseBuffer,
R_Parse1Buffer
The behaviour of the plot function when used with xlim/ylim and the
matplot function as in the following simple example changed between
R2.6.1 and 2.7.0+ producing ugly plots in the new versions. In case of
plot it looks like the pretty function is called with wrong arguments
(i.e. range of supplie
