unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel@gnu.org
Subject: Re: (sxml match)
Date: Wed, 26 May 2010 16:12:36 +0200	[thread overview]
Message-ID: <87hblurbu3.fsf@gnu.org> (raw)
In-Reply-To: <m38w76vnva.fsf@pobox.com> (Andy Wingo's message of "Wed, 26 May 2010 14:39:05 +0200")

Hi Andy!

Andy Wingo <wingo@pobox.com> writes:

> On Tue 25 May 2010 23:42, ludo@gnu.org (Ludovic Courtès) writes:

>> I integrated the doc in the manual.  Unfortunately it can’t be made to
>> appear close to the automatically generated doc of (sxml simple), so it
>> actually appears before.  I’m open to suggestions to improve that.
>
> You could put the documentation in the module commentary of (sxml
> match), as texinfo. Or you could extend module-commentary somehow to
> look for commentaries in other sources. Probably easiest just to paste
> the texinfo you already wrote into the commentary, no?

Actually I don’t want that much Texinfo in a Scheme file, and I don’t
want the automatically-generated “Usage” subsection.

Besides, I initially started by just putting ‘@include sxml-match.texi’
in the module’s commentary but that didn’t work (I forgot the details.)

>> The test suite reveals an interesting psyntax “problem”: renaming the
>> ‘xyzpq’ variable in sxml-match-tests.ss to ‘x’ leads to:
>>
>> ERROR: In procedure macroexpand:
>> ERROR: identifier out of context in subform `x' of `(quote (d (a 1 2 3) (a 4 5) (a 6 7 8) (a 9 10)))'
>>
>> Ideas?
>>
>> (Would be good if psyntax error reporting contained source location
>> info.)
>
> It would certainly be possible to maintain a stack of source locations
> in the expander, and modify syntax-violation to look in that stack.
>
> There is also the possibility of simply inspecting the syntax objects
> given to syntax-violation for source info, but it might not be there --
> best to have a stack to at least give approximate info.

Thanks for the hints, I’ll try to look into it.

I note that you subtly omitted to comment on the issue above.  :-)

Thanks,
Ludo’.



  reply	other threads:[~2010-05-26 14:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-25 21:42 (sxml match) Ludovic Courtès
2010-05-26 12:39 ` Andy Wingo
2010-05-26 14:12   ` Ludovic Courtès [this message]
2010-05-26 15:47     ` Andy Wingo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87hblurbu3.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guile-devel@gnu.org \
    --cc=wingo@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).