Btw, I think this is lazy way to use the S4 classes in my personal package without having to use the 'NAMESPACE' file, but now I have an incentive to define the S4 classes properly using the export mechanisms detailed in Section 1.6.6 of "Writing R Extensions".<br>
<br>Best,<br><br>Thiago<br><br><div class="gmail_quote">On Sun, Jun 26, 2011 at 12:48 PM, Thiago Guerrera <span dir="ltr"><<a href="mailto:thigm85@gmail.com">thigm85@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
That's because each function contain classes related to each other, like a grouping to make things more organized, then I would have a .First.lib that look like this:<br> <br>.First.lib <- function(libname, pkgname, where) {<br>
<br> if( !require(methods) ) stop()<br> where <- match(paste("package:", pkgname, sep=""), search())<br><br> .initGENERICS(where)<br> .initCLASSES_GROUP1(where)<br> .initCLASSES_GROUP2(where)<br> .initCLASSES_METHOD_FOR_GROUP1(where)<br>
<br>}<br><br>I am not sure if this is ideal, but makes things clear for me. Any suggestion for the organization of S4 classes?<br><br>Best,<br><br>Thiago<div><div></div><div class="h5"><br><br><div class="gmail_quote">On Sun, Jun 26, 2011 at 12:04 PM, Toby Dylan Hocking <span dir="ltr"><<a href="mailto:Toby.Hocking@inria.fr" target="_blank">Toby.Hocking@inria.fr</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">You are correct: inlinedocs can currently only generate documentation<br>
for S4 classes defined in the usual way, as indicated in the<br>
examples.<br>
<br>
Out of curiousity, why do you define S4 classes inside of functions?<br>
</blockquote></div><br><br clear="all"><br></div></div><font color="#888888">-- <br>Thiago Guerrera Martins<br><br>
</font></blockquote></div><br><br clear="all"><br>-- <br>Thiago Guerrera Martins<br><br>