unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: <tomas@tuxteam.de>
To: guile-user@gnu.org
Subject: Re: sxml-match bad pattern syntax
Date: Tue, 28 Dec 2021 11:06:55 +0100	[thread overview]
Message-ID: <Ycrhv9wZ1Cb+gFkI@tuxteam.de> (raw)
In-Reply-To: <875yr9dqzg.fsf@gnuvola.org>

[-- Attachment #1: Type: text/plain, Size: 1016 bytes --]

On Tue, Dec 28, 2021 at 04:21:39AM -0500, Thien-Thi Nguyen wrote:
> 
> () <tomas@tuxteam.de>
> () Tue, 28 Dec 2021 09:28:32 +0100
> 
>    > Ah, right!  The ellipses are a tail that need to follow a
>    > head.
> 
>    No, the ellipses tell the matcher that the symbol to its left

[...]

> I think we're saying the same thing, but in any case, i
> understand what you're saying.

I see now. I was mis-reading you.

[...]

> I think the ‘otherwise’ clause is a bit unwieldy; it presumes
> normal form 3 (attribute lists always present).  However, i
> couldn't find a way to match "any element".  ISTM the element
> portion (first symbol in the form) MUST be non-variable.

At first blush it seems so. At least, when I try [1], it yells at
me with something something

  Throw to key `sxml-match-error' with args `(#f "bad pattern syntax (not an element pattern)" ...

Hm.

Cheers

[1] what I try is matching the tag to an unquoted var, like
   so (match ((,tag ...))).
-- 
t

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

      reply	other threads:[~2021-12-28 10:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-28  6:21 sxml-match bad pattern syntax Thien-Thi Nguyen
2021-12-28  7:19 ` tomas
2021-12-28  7:58   ` Thien-Thi Nguyen
2021-12-28  8:28     ` tomas
2021-12-28  9:21       ` Thien-Thi Nguyen
2021-12-28 10:06         ` tomas [this message]

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=Ycrhv9wZ1Cb+gFkI@tuxteam.de \
    --to=tomas@tuxteam.de \
    --cc=guile-user@gnu.org \
    /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).