Re: bug#10522: Patch: Improve optional variable and keyword notation in manual

2013-03-09 Thread Andy Wingo 
On Sat 09 Mar 2013 02:58, Daniel Hartwig mand...@gmail.com writes:

  -- Scheme Procedure: eval-string string [#:module=#f] [#:file=#f]
   [#:line=#f] [#:column=#f] [#:lang=(current-language)]
   [#:compile?=#f]

 we see that there is some potential confusion between the close,
 unescaped (as with @code, ‘’) nesting of the parens/brackets.

Should we remove the brackets entirely? i.e

 -- Scheme Procedure: eval-string string #:module=#f #:file=#f
  #:line=#f #:column=#f #:lang=(current-language)
  #:compile?=#f

Or with @code{}:

 -- Scheme Procedure: eval-string string #:module=‘#f’ #:file=‘#f’
  #:line=‘#f’ #:column=‘#f’ #:lang=‘(current-language)’
  #:compile?=‘#f’

Dunno, just throwing more ideas out there...

Andy
-- 
http://wingolog.org/

Re: CPS Update

2013-03-09 Thread Andy Wingo 
On Fri 08 Mar 2013 23:57, Noah Lavine noah.b.lav...@gmail.com writes:

 Somewhat shockingly, I think that's almost every language feature.

Wow, nice work :-))

Sounds like great stuff.  I hope to join you in this work once 2.0.8 is
out.  It's really great that you're working on this!

Cheers,

Andy
-- 
http://wingolog.org/

Re: bug#10522: Patch: Improve optional variable and keyword notation in manual

2013-03-09 Thread Daniel Hartwig 
On 9 March 2013 16:25, Andy Wingo wi...@pobox.com wrote:
 Should we remove the brackets entirely? i.e

I would not.  The brackets are fairly standard for optional arguments.