Hi Raymond et al., Before proceeding much further, one question I'd like to clarify is what form this documentation will take eventually.
Will it become part of the documentation for ellint_Kcomp, ellint_Ecomp and ellipke (what one would see when typing "help function_name" at the octave prompt)? If so, then should the documentation effort underway take the form of patches to ellpke.m and buildgsl_sf.sh? Working on a LaTeX based document is fine for me, but if the goal is to eventually improve the functions' documentation, perhaps switching to the structure described in the "Octave Documentation Strings Tips" [1] soon should be considered. I bring this up since I think this may impact the structure of the documentation. For example, the current document has all forms of the elliptic integrals defined in the GSL section whereas for online documentation, I think something will be needed in the ellipke.m section. Two technical points: I would remove the general Legendre form definitions from the documentation. I think the important point to document is that the definitions used by ellipke and ellint_[KE]comp are different. ellipke accepts n x 1 arrays as you wrote, but also n x m arrays, if m >= 2. Kristjan [1] http://www.gnu.org/software/octave/doc/interpreter/Documentation-Tips.html#Documentation-Tips ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Octave-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/octave-dev
