Hi Elliott,
My apologies, this dropped off my radar. I'll review and promote
tomorrow. If anyone else has patches that haven't been committed,
please re-send them. I'll put in a fix for the lispworks bug as well.
Ian
On Feb 2, 2009, at 6:45 PM, Elliott Slaughter wrote:
> Just wondering i
Hi, Larry
I just checked, Elephant 1.0 on my LWL64 5.0.2 can be compiled and
loaded correctly. LWL64 5.1.2 failed on classes.lisp which you met.
In src/elephant/metaclasses.lisp, I found two definitions which
mentioned about LispWorks versions:
line 396:
#+(or :lispworks3 :lispworks4 (an
Is there anything I can do to improve on the below error report? I'd
like to use elephant but it doesn't compile on Lispworks for Linux
5.1. Am I missing something? Any help appreciated.
-- Larry
- Forwarded message from Larry Clapp -
> From: Larry Clapp
> Date: Sun, 25 Jan 2009 16:
Just wondering if there is any chance this patch will be reviewed and/or
integrated soon?
Thanks.
On Thu, Jan 8, 2009 at 1:14 AM, Elliott Slaughter <
elliottslaugh...@gmail.com> wrote:
> Hi,
>
> On Mon, Dec 15, 2008 at 11:03 PM, Elliott Slaughter <
> elliottslaugh...@gmail.com> wrote:
>>
>> I ju
Hi,
Thanks for working on this. I am particularly interested in the potential of
this backend because I need (a) speed and (b) the ability to build a binary
which will run on end-user machines without requiring them to install a
separate library.
If you send me the necessary patches (or get them i
Hi All,
I was inspired the other day to come up with a minimal, quick-and-
dirty, all-lisp data store for Elephant based on cl-prevalence. The
problem with cl-prevalence is that every access to a persistent slot
has to be explicitly transactionally protected so it can be
recovered. This i
