zsh-workers
 help / color / mirror / code / Atom feed
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: Pattern matching
Date: Fri, 30 Jul 1999 13:27:51 +0400	[thread overview]
Message-ID: <000901beda6d$cb8034e0$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <9907281225.AA34297@ibmth.df.unipi.it>


>
> Just discovered this.  It will have to wait to be fixed --- it's been
> around for years and no-one's complained.  I'm planning a rewrite of the
> pattern matching code anyway.
>

Just using the occasion. I once suggested to replace ad hoc code with conversion
to standard regexps. I believe, now a days all systems have standard POSIX
regexps available. This will be much more clean and I hope faster. Zsh patterns
are pretty close to normal regular experssions so it should be not a problem
(even SAMBA takes this course for wildcard matching :-) Just some points:

 - currently code scans pattern for every match. This may really be inefficient
for globbing (even more so, as code has to dequote string every time). Using
rgexps pattern can be compiled once - for recursive globbing quite a gain.

 - this may automatically solve the original problem of this post. Regexps are
required to match the longest string, even if every subregexp is not the longest
one.

regards

/andrej




  reply	other threads:[~1999-07-30  9:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-28 12:25 Numeric range bug Peter Stephenson
1999-07-30  9:27 ` Andrej Borsenkow [this message]
1999-07-30  9:29   ` Pattern matching Peter Stephenson

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='000901beda6d$cb8034e0$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).