Hi!
On Sat, 01 Jul 2006 15:57:26 +0200, Frédéric Jolliton <cl-ppcre-devel(a)frederic.jolliton.com> wrote:
> The first patch add a (?.<name>) syntax, where <name> designate a
> keyword, and is case sensitive. The ?. was chosen to match the idea
> of the #. reader macro. It includes the synonym parse tree from the
> corresponding keyword while the regex is parsed.
Thanks for this patch, but as you wrote in your email, I think this
one is a little bit too hackish. It also breaks compatibility with
Perl syntax.
> The second patch add the (:REGEX <regex>) construct to use regex
> string into parse tree. It's the opposite idea of the former patch.
And thanks for this one as well. I've made a new release (1.2.15)
which incorporates your changes.
Cheers,
Edi.
_______________________________________________
cl-ppcre-announce mailing list
cl-ppcre-announce(a)common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/cl-ppcre-announce
Rudi Schlatte wrote:
> Hmm, muproc-compat.lisp (in your proposal below) would be essentially
documentation, and would only be loaded on otherwise unsupported Lisp
implementations. In that light, would it make sense to create
muproc-compat.txt (or porting.txt) and document the muproc-compat
interface there? Alternatively, the documentation could also be written
as comments in the :exports section of the defpackage form for the
cl-muproc.compat package.
There's a new version of cl-muproc incorporating Rudi's new with a few
modifcations... I decided that with implementation specific files,
muproc-compat.lisp did not make much sense. I think the package
definition for cl-muproc.compat defines the required implementation
specific functionality adequately, and decided to add a PORTING file
briefly describing the intended structure of implementation specific
code instead.
The new version compiles without warnings and passes the test on Lispworks.
Enjoy.
-Klaus.
_______________________________________________
cl-muproc-announce mailing list
cl-muproc-announce(a)common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/cl-muproc-announce
The latest release of the Elephant persistent object store is now
available.
It is numbered 0.6.0. It may be obtained from the project page either
as a downloaded tgz file, or you make access it via anonymous CVS.
http://common-lisp.net/project/elephant/
Ian Eslick made most of the code contributions to this release, which
features a very elegant method of indexing the slots of a persistent
class.
For developers, the internals of Elephant were also significantly
refactored
by Ian. Additionally, a layer of data management on top of Elephant
that
implements a Director-like pattern called Data Collection Management has
been added to the contrib directory.
In addition to personally thanking Ian, I would like to say that I
personally
think Elephant has grown into an extraordinarily useful project. Let
me
just review the major advantages of Elephant as a persistent object
store:
1) Extraordinarily convenient for the programmer,
2) An extensive test suite,
3) Tested on several major LISP implementations (ACL, SBCL, OpenMCL),
4) Ability to use multiple back-end data repositories and to migrate
whole
data stores seamlessly between those repositories,
5) Ability to BerkeleyDB, PostGres, SQLite 3, and probably other back-
end
databases,
6) Extremely convenient slot and functional indexing that can be
dynamically
changed.
The overall effect of these features together is that Elephant is very
flexible for
serious application development: you can change fundamental
implementation
decisions easily as your application evolves.
----
Robert L. Read, PhD read &T
robertlread.net
Consider visiting Progressive Engineering:
http://robertlread.net/pe
In Austin: 912-8593 "Think
globally, Act locally." -- RBF
_______________________________________________
elephant-announce site list
elephant-announce(a)common-lisp.net
http://common-lisp.net/mailman/listinfo/elephant-announce