Newsgroups: comp.lang.lisp
Path: cantaloupe.srv.cs.cmu.edu!das-news2.harvard.edu!oitnews.harvard.edu!purdue!haven.umd.edu!ames!eos!kronos.arc.nasa.gov!ptolemy.arc.nasa.gov!kpc
From: k p c <kpc@ptolemy.arc.nasa.gov>
Subject: Re: Doing a grep-like search-and-replace in lisp?
In-Reply-To: felciano@camis.stanford.edu's message of Fri, 15 Dec 1995
	20:08:16 -0800
Message-ID: <1995Dec17.045817.12000@ptolemy-ethernet.arc.nasa.gov>
To: felciano@camis.stanford.edu (Ramon M. Felciano)
X-Disclaimer: No organization, company, or government is represented here.
X-Attribution: kpc
Lines: 20
Sender: usenet@ptolemy-ethernet.arc.nasa.gov (usenet@ptolemy.arc.nasa.gov)
Nntp-Posting-Host: phenotype.arc.nasa.gov
Reply-To: kpc@ptolemy.arc.nasa.gov
Cc: kpc@ptolemy.arc.nasa.gov
Organization: NASA Ames Research Ctr., AI Research and Aero. Facil. Branches.
	Disclaimer: neither a civil servant nor a representative.
References: <felciano-1512952008160001@smi-mac-146.stanford.edu>
Date: Sun, 17 Dec 1995 05:06:45 GMT

CL is worth using, but CL regexp capabilities are behind the times.

	o There are regexp-like pattern-replacement packages in the archive
	o I think GCL has regexps now
	o You can use foreign functions
	o You can use a CL regexp package from the archive
	o There are string and vector functions in CL
	o You can call a program to do the regexp parsing

IMHO a well-thought-out efficient regexp facility should be part of
the CL standard (that'll draw flames.  :-)).

If you post a followup to this article, I would appreciate a courtesy
verbatim copy by email to help work around potentially unreliable feeds.

---
kpc@ptolemy.arc.nasa.gov.  AI, multidisciplinary neuroethology, info filtering.
Play fairly; offer takebacks; connect edge with center; neither play too thinly
nor engage too readily; take stones early; divide and conquer; don't allow them
to invade; pick your battles; see the whole board; use solid connections; grow.
