Announcement: PCOND
Have you ever wanted to perform pattern matching, bind variables, and do conditional branching all with one handy macro?
Well now you can!
I’ve just released a library called PCOND. I’ve posted about it before. You can read about it on cliki.
Basically, it’s a pattern matching conditional macro. Imagine COND with unification expressions and regular expression matching.
And a surprise for tomorrow . . .
While I was creating the ASDF package and setting up the ASDF-Install, I thought of something. Two packages that PCOND depends on, CL-UNIFICATION and LISP-UNIT, are not ASDF-Installable. This basically means that my package is not as simple as just ASDF-Installing my package for the users that don’t already have the dependencies.
So I had an idea . . . which you’ll read about tomorrow!
Popularity: 2% [?]
Filed under packages |3 Responses to “Announcement: PCOND”
Leave a Reply
This looks really cool! Thank you!
I’m excited to find out what your idea was.
Just a little note: it sounds like your package should only have one dependency, cl-unification. lisp-unit is one of the tools you use to develop/maintain your library, but presumably it’s not actually needed to *use* your library. If you put something like this in your system definition:
in-order-to ((test-op (load-op “lisp-unit”)))
then you’ll only depend on lisp-unit when performing your test-op. Or just make a pcond-test system.
I’ve actually chosen the second option. The PCOND-TEST system requires LISP-UNIT.
Thanks for the comment.