AFAIK, these packages often extend a part of the Sweave driver, which
consists of several components, e.g. only modify the
'RweaveLatexRuncode' part in
> RweaveLatex
function ()
{
list(setup = RweaveLatexSetup, runcode = RweaveLatexRuncode,
writedoc = RweaveLatexWritedoc, finish = RweaveLatexFinish,
checkopts = RweaveLatexOptions)
}
<environment: namespace:utils>
So they are based on Sweave instead of a re-implementation. However,
it is unpredictable whether they will be updated when Sweave gets
updated (depending on the package authors), because (IMHO) Sweave was
not designed to be readily extensible (it is, however, extensible to
some degree), i.e. if we want to replace or modify a very small part
of its functionality, we have to copy all the source code and do our
modification. A typical example is that currently it is difficult to
add an extra graphics device such as png() to Sweave without touching
the source code of Sweave.
We might rely on some tools to update our revisions automatically,
such as SVN (merge the changes), but I have no idea of the
difficulties. What I can see is the pgfSweave authors have been trying
to keep up with the updates of Sweave from R core.
Regards,
Yihui
--
Yihui Xie <xieyi...@gmail.com>
Phone: 515-294-2465 Web: http://yihui.name
Department of Statistics, Iowa State University
2215 Snedecor Hall, Ames, IA
On Sat, Jan 1, 2011 at 6:54 AM, Liviu Andronic <landronim...@gmail.com> wrote:
> (slightly off-topic)
> Hello
>
>
> On Sat, Jan 1, 2011 at 12:20 AM, Yihui Xie <x...@yihui.name> wrote:
>> I still recommend the pgfSweave package (as usual) -- you can cache
>> both data objects (using cacheSweave) and graphics (using pgf).
>>
> Do these packages re-implement Sweave, or just use it as a dependency?
> For example, if Sweave gets updated, will the changes be automatically
> available for pgfSweave users or not?
>
> Regards
> Liviu
>
>
>> Regards,
>> Yihui
>> --
>> Yihui Xie <xieyi...@gmail.com>
>> Phone: 515-294-2465 Web: http://yihui.name
>> Department of Statistics, Iowa State University
>> 2215 Snedecor Hall, Ames, IA
>>
>>
>>
>> On Fri, Dec 31, 2010 at 2:35 PM, Lars Bishop <lars...@gmail.com> wrote:
>>> Hi,
>>>
>>> Maybe I'm missing the point here...but let's suppose you are working with
>>> "large" data sets and using functions that take a significant amount of time
>>> to run in R. I woulnd't like to run these functions every time I call
>>> Sweave("myfile.Rnw") within R. What is the "common" practice to use Sweave
>>> in these situations. I would just run the function once, save the results
>>> and only load them each time I run Sweave on the .Rnw file. Makes sense?
>>>
>>> Sorry, the question seems silly, but I'd appreciate your thoughts.
>>>
>>> Thanks,
>>> Lars.
>>>
>>> [[alternative HTML version deleted]]
>>>
>>> ______________________________________________
>>> R-help@r-project.org mailing list
>>> https://stat.ethz.ch/mailman/listinfo/r-help
>>> PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
>>> and provide commented, minimal, self-contained, reproducible code.
>>>
>>
>> ______________________________________________
>> R-help@r-project.org mailing list
>> https://stat.ethz.ch/mailman/listinfo/r-help
>> PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
>> and provide commented, minimal, self-contained, reproducible code.
>>
>
>
>
> --
> Do you know how to read?
> http://www.alienetworks.com/srtest.cfm
> http://goodies.xfce.org/projects/applications/xfce4-dict#speed-reader
> Do you know how to write?
> http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail
>
______________________________________________
R-help@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.
