From: Christopher Browne <cbbrowne@acm.org>
Subject: Re: On refining regexp by adding exceptions systematically
Date: 5 Oct 2002 19:46:11 GMT [thread overview]
Message-ID: <annfi3$g220e$3@ID-125932.news.dfncis.de> (raw)
In-Reply-To: 9e8ebeb2.0210030427.4544cb00@posting.google.com
Oops! gnuist007@hotmail.com (gnuist) was seen spray-painting on a wall:
> Here is regular expression in emacs lisp that initially seems to work
> for the job:
> [A-Z][A-Z][A-Z][0-9]+
> After running it on a number of uses, I find that there is an
> exception to it, namely PJP89898. Rather than rehashing the code
> after having forgotten it and reworking my regexp expression (every
> time I find an exception) in some convoluted way, is there a
> systematic way to add an exception or a series of exceptions to the
> regexp? I am sure that there are a number of ways to do this and
> each has its merits.
> I am using this regexp in two ways in a different program. In the
> first one (looking-at regexp) so that it assumes that cursor is on
> it. In the second one (search-forward-regexp regexp) in a narrowed
> region so that one is trying to find if there is one. It seems to
> me that it is a little tricky to do this. Perhaps an example code
> would help with exception implemented for searching on a line.
If your specification sucks, "adding exceptions" is just going to make
the code "suck worse" as you find more of them.
Maybe you need to do the design work up front to determine the /real/
specification for whatever it was that you were searching for.
And perhaps you should set up followup to your /favorite/ newsgroup?
This isn't really a Unix question, nor is it a Lisp question, so
discussion probably shouldn't continue in these newsgroups.
--
(reverse (concatenate 'string "moc.enworbbc@" "sirhc"))
http://cbbrowne.com/info/emacs.html
"Necessity is the mother of invention" is a silly proverb. "Necessity
is the mother of futile dodges" is much closer to the truth. The
basis of growth of modern invention is science, and science is almost
wholly the outgrowth of pleasurable intellectual curiosity.
-- Alfred N. Whitehead
prev parent reply other threads:[~2002-10-05 19:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-03 12:27 On refining regexp by adding exceptions systematically gnuist
2002-10-03 18:38 ` Kaz Kylheku
2002-10-03 23:04 ` Kaz Kylheku
[not found] ` <tvikna.obd.ln@lart.ca>
2002-10-07 14:13 ` Rodney Sparapani
2002-10-05 13:31 ` Alan Mackenzie
2002-10-05 16:11 ` Stefan Monnier <foo@acm.com>
2002-10-05 17:45 ` Alan Mackenzie
2002-10-06 3:02 ` Vassil Nikolov
2002-10-06 7:48 ` Alan Mackenzie
2002-10-05 19:46 ` Christopher Browne [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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='annfi3$g220e$3@ID-125932.news.dfncis.de' \
--to=cbbrowne@acm.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).