From h.wickham at gmail.com  Sat Jun 20 03:15:40 2009
From: h.wickham at gmail.com (hadley wickham)
Date: Fri, 19 Jun 2009 20:15:40 -0500
Subject: [Rd] Changes to Rd handling in R-devel
In-Reply-To: <4A3C1B57.4040708@stats.uwo.ca>
References: <4A3C1B57.4040708@stats.uwo.ca>
Message-ID: <f8e6ff050906191815i39753ad3sb62a696cda2680f1@mail.gmail.com>

On Fri, Jun 19, 2009 at 6:12 PM, Duncan Murdoch<murdoch at stats.uwo.ca> wrote:
> I've just committed some fairly big changes to R-devel. ?- There's a new tag
> \Sexpr which allows R code to be embedded within the Rd file, similar to
> Sweave, ?\RdOpts
> ? corresponds to \SweaveOpts.
> ?- The parser now mainly issues warnings, rather than errors, in case of
> syntax errors. ?It throws away a few tokens and tries to restart. ?This
> should let you see most of your errors in one pass, rather than one at a
> time. ?(Don't ignore the warnings -- you've lost some of your file if you
> get them!) ?(Romain: ?yes, this is done using the special "error" token in
> bison.)
> ?- There are also a number of bug fixes to the rendering code (e.g.
> Rd2HTML). ?I'm hoping to switch over soon to the new parser being used to
> produce all man pages.
>
> I need to write up more about \Sexpr, but the basic idea is that the format
> is
>
> \Sexpr{R code}
>
> or
>
> \Sexpr[options]{R code}
>
> Currently the R code is not executed unless you do it manually, but once
> we're using this engine for man pages, you'll be able to choose when to
> execute the code: ?build time, install time, or render time.

Can the R code emit top-level rdoc tags? i.e. could the complete rd
file just be \Sexpr{} ?

Hadley


-- 
http://had.co.nz/



[Rd] Changes to Rd handling in R-devel
hadley wickham