Alright, I will update the site and announce b1 some time
next week. I've just spotted at least two tiny foreign
memory leaks in berkeley-db.lisp that I want to fix first.
Leslie
--
http://www.linkedin.com/in/polzer
___
elephant-devel site list
el
I don't have an objection. -Ian
On Jul 22, 2009, at 9:50 AM, Leslie P. Polzer wrote:
>
> How about it?
>
> A beta tested about 90% isn't all that bad, plus this one
> already fixes a bunch of bugs in a2.
>
> Leslie
>
> --
> http://www.linkedin.com/in/polzer
>
>
> __
How about it?
A beta tested about 90% isn't all that bad, plus this one
already fixes a bunch of bugs in a2.
Leslie
--
http://www.linkedin.com/in/polzer
___
elephant-devel site list
elephant-devel@common-lisp.net
http://common-lisp.net/mailman/li
I've also wondered what parts of syncing run inside a
transaction. ASDF compilation prevents async interruptions
at least but of course another thread could be in the middle
of some op when the sync happens.
Leslie
Synchronization in the sense of on-disk instance updates are all
degree-2 tr
On Sat, Jun 20, 2009 at 09:21:16PM -0700, Ian Eslick wrote:
> I'd like to do a thread-safety pass on the schema evolution code
> first. I'll maybe get to it next week. Anyone want to be a second
> pair of eyes?
Yes, but no guarantees how much time I'll actually be able
to put into it.
I've
I'd like to do a thread-safety pass on the schema evolution code
first. I'll maybe get to it next week. Anyone want to be a second
pair of eyes?
Ian
On Jun 20, 2009, at 9:58 AM, Leslie P. Polzer wrote:
>
> I suggest we release the first beta of 1.0 soon.
>
> Several fixes have made their w
