Re: Parallel Common-Lisp with at least 64 processors?
- From: Marco Antoniotti <marcoxa@xxxxxxxxx>
- Date: Wed, 25 Jun 2008 07:38:17 -0700 (PDT)
On 24 Giu, 13:44, Jon Harrop <j...@xxxxxxxxxxxxxxxxx> wrote:
Pascal J. Bourguignon wrote:
Jon Harrop <j...@xxxxxxxxxxxxxxxxx> writes:
Pascal J. Bourguignon wrote:
Well ok. Indeed, lisp has no native pattern matcher. But it has
something better: smooth and easy meta-programming.
Mathematica has both pattern matching and easy metaprogramming. Could a
next generation Lisp also bundle both?
The question is still whether this is something that needs to be done
at the implementation level.
Most of lisp just doesn't need specific implementation support, but
can be implemented directly over a core lisp. (Without going down to
the theorical pure lambda calculus, you could implement CL just with
its 17 special operators, and all the rest implemented above them).
If we were talking about Scheme I'd agree but isn't the point of Lisp that
you take a bare bones metacircular evaluator and add lots of useful
features in a standard library such that users have a decent foundation to
build upon?
So the point is that if you, as a lisp programmer, feel the need for a
pattern matcher, then you can implement it yourself in lisp as a
library, and it will be as integrated to the language as any other CL
operator, such as CLOS or LOOP for example.
But I don't remember you citing any feature of pattern matching that
would need implementation level support. On the contrary, we have
the example of several pattern matcher libraries.
That is precisely the problem. Users don't want a multitude of crap pattern
matching libraries and the ability to Greenspun their own. Users want a
single decent implementation.
... as in CL-UNIFICATION (shameless plug: http://common-lisp.net/project/cl-unification)?
:)
And no. It is *NOT* integrated with the compiler. Don't start
confusing levels again.
The point is that, given CL-UNIFICATION, DEFINE-COMPILER-MACRO and the
MOP you could in principle build fast pattern matching function
definitions and calls directly in CL.
Cheers
--
Marco
.
- References:
- Re: Parallel Common-Lisp with at least 64 processors?
- From: Jon Harrop
- Re: Parallel Common-Lisp with at least 64 processors?
- From: John Thingstad
- Re: Parallel Common-Lisp with at least 64 processors?
- From: Jon Harrop
- Re: Parallel Common-Lisp with at least 64 processors?
- From: Ariel
- Re: Parallel Common-Lisp with at least 64 processors?
- From: Jon Harrop
- Re: Parallel Common-Lisp with at least 64 processors?
- From: Robert Maas, http://tinyurl.com/uh3t
- Re: Parallel Common-Lisp with at least 64 processors?
- From: Jon Harrop
- Re: Parallel Common-Lisp with at least 64 processors?
- From: Patrick May
- Re: Parallel Common-Lisp with at least 64 processors?
- From: Jon Harrop
- Re: Parallel Common-Lisp with at least 64 processors?
- From: George Neuner
- Re: Parallel Common-Lisp with at least 64 processors?
- From: Jon Harrop
- Re: Parallel Common-Lisp with at least 64 processors?
- From: George Neuner
- Re: Parallel Common-Lisp with at least 64 processors?
- From: Jon Harrop
- Re: Parallel Common-Lisp with at least 64 processors?
- From: Pascal Costanza
- Re: Parallel Common-Lisp with at least 64 processors?
- From: Jon Harrop
- Re: Parallel Common-Lisp with at least 64 processors?
- From: Pascal J. Bourguignon
- Re: Parallel Common-Lisp with at least 64 processors?
- From: Jon Harrop
- Re: Parallel Common-Lisp with at least 64 processors?
- Prev by Date: Re: Parallel Common-Lisp with at least 64 processors?
- Next by Date: Re: SBCL is now faster than Java, as fast as Ocaml, and getting better
- Previous by thread: Re: Parallel Common-Lisp with at least 64 processors?
- Next by thread: Re: Parallel Common-Lisp with at least 64 processors?
- Index(es):
Relevant Pages
|
Loading