Re: Documenting PicoLisp code?

2017-03-29 Thread Danilo Kordic
I have to at least mention [[http://www.nongnu.org/skribilo/][Skribilo]] :) . IMHO that is how it should be done. -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: Documenting PicoLisp code?

2017-03-28 Thread Joh-Tob Schäg
My pleasure 2017-03-28 20:20 GMT+02:00 Tim Johnson : > * Joh-Tob Schäg [170328 10:09]: > > It is no doc string in the elisp sense even though function and syntax > are > > similar. > > > > (de do_nothing () "Does nothing") > > > > Does not behave as

Re: Documenting PicoLisp code?

2017-03-28 Thread Tim Johnson
* Joh-Tob Schäg [170328 10:09]: > It is no doc string in the elisp sense even though function and syntax are > similar. > > (de do_nothing () "Does nothing") > > Does not behave as expected. It returns the evaluated transient symbol > "Does nothing". > > (de return_null ()

Re: Documenting PicoLisp code?

2017-03-28 Thread Joh-Tob Schäg
It is no doc string in the elisp sense even though function and syntax are similar. (de do_nothing () "Does nothing") Does not behave as expected. It returns the evaluated transient symbol "Does nothing". (de return_null () "returns 0" 0) (de muliply_increase_add (A B C) (let N (* A B) "N is A

Re: Documenting PicoLisp code?

2017-03-24 Thread Joh-Tob Schäg
Either comments inside the code.# Like that Transistent Symbols at the beginn of the funtion. (de power (N E) "Calculates the exponent in a wastefull manner" (apply '* (need E N))) I have not seen another approach in Picolisp yet Am 24.03.2017 04:15 schrieb "Christopher Howard" <