Re: procedure docstrings / documentation

2017-09-23 Thread tantalum
i don't know of common conventions, but here is what i do: * i don't repeat the procedure name and parameter names because that can be queried at run-time or automatically extracted * most of the time i write a type signature in the first line of docstrings because i find that information

Re: procedure docstrings / documentation

2017-09-23 Thread Matt Wette
> On Sep 23, 2017, at 1:56 PM, Christopher Howard > wrote: > > No thoughts related to this subject? > > On Wed, 2017-09-20 at 16:18 -0800, Christopher Howard wrote: >> Is there any convention on content/formatting for a procedure >> docstring? E.g., should I

Re: procedure docstrings / documentation

2017-09-23 Thread Christopher Howard
No thoughts related to this subject? On Wed, 2017-09-20 at 16:18 -0800, Christopher Howard wrote: > Is there any convention on content/formatting for a procedure > docstring? E.g., should I repeat the procedure name and arguments? > Should I insert newlines to maintain a certain text width? > >

Re: guile 2.2 : syntax-rules failure?

2017-09-23 Thread Taylan Ulrich Bayırlı/Kammer
Matt Wette writes: > difference in behavior from guile 2.0 to guile 2.2: > > === foo.scm = > (define-module (foo) > #:export (foo-mac)) > > (define bar 1) > > (define-syntax foo-mac > (syntax-rules (bar) > ((_ (bar none)) #t))) > > === demo.scm