[Roxygen-devel] Status of R5 support

[Rob Tirrell]

Basically, if you could point me at the problem I'd be willing to work on
it. Are you (the Roxygen team) satisfied with your basic approach, and then
adding support for setRefClass is just a logical extension of the existing
parser? Otherwise, what are the next steps?

Thanks again!
--
Robert Tirrell | rpt at stanford.edu | (607) 437-6532
Program in Biomedical Informatics | Butte Lab | Stanford University



On Thu, Mar 17, 2011 at 12:55, Rob Tirrell <rpt at stanford.edu> wrote:

> Yeah, I think that would be the goal - to descend into each class and read
> tags, as if they were naked functions plus some context derived from the
> enclosing call to setRefClass. I don't know how this would work with the
> inline documentation reference classes allow.
> As far as that commit message, I don't exactly recall what prompted it. I
> initially had some misundertsandings about how Rd2 works.
> --
> Robert Tirrell | rpt at stanford.edu | (607) 437-6532
> Program in Biomedical Informatics | Butte Lab | Stanford University
>
>
>
> On Thu, Mar 17, 2011 at 11:54, Peter Danenberg <pcd at roxygen.org> wrote:
>
>> Quoth Rob Tirrell on Sweetmorn, the 3rd of Discord:
>> > As a quick followup: I've been working on an database abstraction
>> > package (https://github.com/rtirrell/databasr) that makes extensive
>> > use of reference classes.
>>
>> Thanks, Rob; I now have a better intuition of how refclasses might
>> work.
>>
>> Using JoinClause as an example, you'd like Roxygen to descend into the
>> class definition; documenting e.g. the individual methods?
>>
>>  #' Represents a JOIN clause.
>>  JoinClause <- setRefClass('JoinClause',
>>
>>          [...]
>>
>>          methods = list(
>>
>>                  [...]
>>
>>                  #' Add children to this JOIN clause.
>>                  #'
>>                  #' This sets the type based on the last element we add.
>>                  #' @param ... arguments to add as children.
>>                  #' @return \code{.self}
>>                  add_children = function(...) {
>>
>>                    [...]
>>
>>                  }
>>
>>                  [...]))
>>
>> Also, one of your last commit-messages was "damn roxygen;" do you
>> remember what the specific frustration was?
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.r-forge.r-project.org/pipermail/roxygen-devel/attachments/20110407/5cef56f5/attachment.htm>