The problem is on both branches then. I've fixed it on unstable. I
don't intend to back patch, although the patch is trivial if someone
wants to make it.
Ian
On May 12, 2008, at 7:55 PM, Ryszard Szopa wrote:
Huh... This is one of those things that are kind of hard to admit
publicly... Ap
On Mon, 2008-05-12 at 10:55 +0300, Alex Mizrahi wrote:
> GT> What do you all think about allowing two different versions of
> GT> Elephant to be installed at the same time?
>
> that's pretty easy.
>
> let's suppose that "stable" elephant is somewhere on your
> asdf:*central-registry* path.
>
On Mon, 2008-05-12 at 08:42 -0400, Ian Eslick wrote:
> #+sbcl :sb-posix is the way to go.
>
> I hadn't realized that SBCL didn't include that by default like the
> rest of the lisps. Easy fix!
>
> Robert, any indication as to the source of your clsql errors?
I will look into tonight, when
Huh... This is one of those things that are kind of hard to admit
publicly... Apparently, I tricked myself into thinking that I was
using elephant-unstable, while in fact I was using Elephant stable
(please don't ask how this was possible). So, the bug I've mentioned
in this thread and for which I'
On Mon, May 12, 2008 at 8:34 PM, Ian Eslick <[EMAIL PROTECTED]> wrote:
> map-index was missing a check for a valid key after the first value query.
> I've patched, verified and pushed a fix along with the test case to
> elephant-unstable.
>
> Thank you for finding this!
My pleasure.
Thank you fo
map-index was missing a check for a valid key after the first value
query. I've patched, verified and pushed a fix along with the test
case to elephant-unstable.
Thank you for finding this!
Ian
On May 12, 2008, at 2:24 PM, Ian Eslick wrote:
That test was great. I reproduced this on my Ma
That test was great. I reproduced this on my Mac under Allegro with
BDB 4.6. Will let you know what I find... I also added the test to
testindexing.lisp.
On May 12, 2008, at 2:08 PM, Ryszard Szopa wrote:
Hey,
map-inverted-index shows some strange behavior. When you pass it
`start' and `
I thought I had fixed all of these - I'll look into it...
Ian
On May 12, 2008, at 2:08 PM, Ryszard Szopa wrote:
Hey,
map-inverted-index shows some strange behavior. When you pass it
`start' and `end' arguments and there are no objects that satisfy the
range, it maps over the first object gre
Hey,
map-inverted-index shows some strange behavior. When you pass it
`start' and `end' arguments and there are no objects that satisfy the
range, it maps over the first object greater than end. I haven't have
time to investigate it thoroughly, but I have written a 5am unit-test
(you are using thi
On May 12, 2008, at 10:23 AM, Leslie P. Polzer wrote:
- Currently cached slots are not rolled back to their initial value
if
transaction aborts. I can add a facility to push the cached value on
the initial read into a per-transaction list that can be used to
reset
the cached slots on an
> - Currently cached slots are not rolled back to their initial value if
> transaction aborts. I can add a facility to push the cached value on
> the initial read into a per-transaction list that can be used to reset
> the cached slots on an abort.
Would it be possible to automatically restore t
> What is the status of this bug/issue?
>
> I'm losing track of all the bugs in the system. It would be very
> helpful (and your bug is less likely to be forgotten) if you could
> file Trac bugs against 1.0 for these reports?
This thing was meant for discussion, not as a bug report.
I haven't be
> Does this bug still occur?
Given that nothing changed in stable: I must suspect so, yes.
I cannot reproduce it, though.
Leslie
___
elephant-devel site list
elephant-devel@common-lisp.net
http://common-lisp.net/mailman/listinfo/elephant-devel
Cached slots:
-
- Currently cached slots are not rolled back to their initial value if
transaction aborts. I can add a facility to push the cached value on
the initial read into a per-transaction list that can be used to reset
the cached slots on an abort. Should this be by d
Does this bug still occur?
On May 6, 2008, at 7:18 AM, Leslie P. Polzer wrote:
Do you mean in an index? A slot can have nil as a value and being
nil
is different than being unbound. Same thing is true with slot
indices. An unbound slot produces no index key, a nil slot
produces a
nil
What is the status of this bug/issue?
I'm losing track of all the bugs in the system. It would be very
helpful (and your bug is less likely to be forgotten) if you could
file Trac bugs against 1.0 for these reports?
It's easy enough to get a common-lisp.net account to sign onto Trac.
Than
#+sbcl :sb-posix is the way to go.
I hadn't realized that SBCL didn't include that by default like the
rest of the lisps. Easy fix!
Robert, any indication as to the source of your clsql errors?
Removing the explicit load is good and looks easy. I'll let you check
these fixes in.
Als
RLR> (:depeonds-on ) expressions without dependence on SBCL? Can we just
RLR> use a compiler pragma like:
RLR> :depends-on (:uffi
RLR> #+sbcl :sb-posix
RLR> :cl-base64))
sure
RLR> in our asdf files? If so we will have to do something similar for
RLR> each supported system (see os.lisp):
R
GT> What do you all think about allowing two different versions of
GT> Elephant to be installed at the same time?
that's pretty easy.
let's suppose that "stable" elephant is somewhere on your
asdf:*central-registry* path.
but you want to load "unstable" version that resides in
"~/elephant-unst
19 matches
Mail list logo
