From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Peter Stephenson" <pws@ibmth.df.unipi.it>,
"Zsh hackers list" <zsh-workers@sunsite.auc.dk>
Subject: Bug? RE: Un-patch: new pattern matching code
Date: Mon, 9 Aug 1999 12:10:14 +0400 [thread overview]
Message-ID: <001801bee23e$9c19d160$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <9908061547.AA37737@ibmth.df.unipi.it>
> Anyone who knows any computer science will probably notice that, while it's
> pretty much a finite state machine, some states are more finite than
> others. In particularly, backtracking on excluded matches, where in
> (foo~bar)rod the `bar' only has to match the `foo' and the `rod' is
> irrelevant, need some extra state recording, and I have retained the old
> trick that eliminates infinite loops and prevents exponential behaviour
> when failing to match against things like `(f#o#)#' (the version of perl
> here goes into an infinite loop when given `(f*o*)*', so it isn't trivial).
> This has meant leaving holes for pointers in the compiled expression, which
> ought to work (I've tried to make sure everything is aligned to pointer
> size anyway) but is probably the most dubious part of the proceedings.
>
bor@itsrm2:~%> foo=ab12xy
bor@itsrm2:~%> print ${foo/[[:digit:]]#}
abxy
bor@itsrm2:~%> print ${(S)foo/[[:digit:]]#}
ab12xy
bor@itsrm2:~%> print ${foo//[[:digit:]]#}
abxy
bor@itsrm2:~%> print ${(S)foo//[[:digit:]]#}
here zsh hangs completely.
next prev parent reply other threads:[~1999-08-09 8:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-06 15:47 Peter Stephenson
1999-08-07 9:02 ` Andrej Borsenkow
1999-08-07 17:48 ` Bart Schaefer
1999-08-08 10:04 ` Extended glob patterns in ${...#..} " Andrej Borsenkow
1999-08-09 4:25 ` Bart Schaefer
1999-08-09 6:25 ` Andrej Borsenkow
1999-08-09 17:10 ` Bart Schaefer
1999-08-09 8:21 ` Andrej Borsenkow
1999-08-09 17:23 ` Bart Schaefer
1999-08-09 8:10 ` Andrej Borsenkow [this message]
1999-08-09 8:42 Bug? " Sven Wischnowsky
1999-08-09 17:29 ` Bart Schaefer
1999-08-09 11:33 Sven Wischnowsky
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='001801bee23e$9c19d160$21c9ca95@mow.siemens.ru' \
--to=andrej.borsenkow@mow.siemens.ru \
--cc=pws@ibmth.df.unipi.it \
--cc=zsh-workers@sunsite.auc.dk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).