You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
see Documenting classes, generics and methods.
I think what is happening is predict.bayesreg is a predict generic function for a class bayesreg. I do not know how to set a class, or whether output objects automatically have classes? I suggest we just change all functions from . to _ . For example, predict.bayesreg becomes predict_bayesreg
The text was updated successfully, but these errors were encountered:
The convention on functions and object names are already written in the README. Have a look at the first and second bullet points in styleguide section:
function names are explicit and with CamelCased verbs, e.g. SimulatesNicheModel.
objects are declared with lowercase, underscores and small caps, e.g. trophic_level
I'll change tomorrow all the names already declared in the package according to these.
Cheers,
Steve
I think we are accidentally creating S3 export methods (i.e a predict generic class), by mistake. I noticed that.
For example, the function cannot be called, but is exported and documented.
works fine.
http://r-pkgs.had.co.nz/man.html
see Documenting classes, generics and methods.
I think what is happening is predict.bayesreg is a predict generic function for a class bayesreg. I do not know how to set a class, or whether output objects automatically have classes? I suggest we just change all functions from . to _ . For example, predict.bayesreg becomes predict_bayesreg
The text was updated successfully, but these errors were encountered: