A thing that works well in R is that arguments to functions have
a separate markup. When you use e.g. roxygen to write documentation, the
@params and @return elements make it clear what is what. This is
something I find lacking in Julia / Lexicon.jl
(and implementing it goes very much over my head)
This being said, I find the julia manual superior to R documentation:
the fact that all functions doing similare things are on the same page
made me realize there are better alternatives often.
t
Michael Borregaard (12/02 05:08):
> <
https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2FJuliaLang%2Fjulia%2Fblob%2Fmaster%2FCONTRIBUTING.md%23improving-documentation&sa=D&sntz=1&usg=AFQjCNFSu7VhGC5GE6j_5KDAKIdtnBsG4Q>
>
> As I understand it, the julia documentation format is still an evolving
> entity. Google-searching in R works well because of the massive number of
> google searches / site visits to R pages. When I started using R, during my
> PhD in 2006, it was almost impossible to google R functions, and there were
> all kinds of (not very functional) search engines to bring up R results.
> Today everybody just googles it. I feel completely confident that julia
> will have the same development, and a lot faster.
>
> Den fredag den 12. februar 2016 kl. 13.16.08 UTC+1 skrev J Luis:
> >
> > One main 'dislike' I find in the documentation is that, contrary to Matlab
> > and R examples that have one page for each function, in julia we have lots
> > of functions per page with short and often cryptic descriptions. Example
> >
> > std(*v*[, *region*])
--
Timothée Poisot, Ph.D.
Professeur adjoint
Quantitative and Computational Ecology
Department of Biological Sciences
Université de Montréal
WEB
http://poisotlab.io/
TWITTER @PoisotLab