From ebo at sandien.com  Wed Sep  3 18:12:15 2008
From: ebo at sandien.com (EBo)
Date: Wed, 3 Sep 2008 10:12:15 MDT
Subject: [Rd] suggestion of new API function for embedded programming.
In-Reply-To: <alpine.LFD.1.10.0809031106210.28931@nokomis.stat.uiowa.edu>
References: <twig.1220449912.10283@swcp.com>,
	<twig.1220449912.10283@swcp.com> <twig.1220454941.83227@swcp.com>,
	<twig.1220454941.83227@swcp.com>
Message-ID: <twig.1220458335.76209@swcp.com>

Luke Tierney <luke at stat.uiowa.edu> said:

> On Wed, 3 Sep 2008, EBo wrote:
> 
> > Luke Tierney <luke at stat.uiowa.edu> 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 public API.
> >
> > What is your objection with making something like this a part of the public
> > API?  I understand that having to use the IOBuffer seems a bit much, but I do
> > not understand your concern.
> 
> We need the freedom to completely change these internals if doing so
> proves useful.

Ah, that makes perfect sense.

Thanks,

  EBo --



[Rd] suggestion of new API function for embedded programming.
EBo