From what I can tell you are proposing that we make a hook into the
instance creation process to clean up these redefinition and change-
class issues. It sounds like you aren't concerned with fitting within
the existing MOP framework (a source of much of my concern). The
'toolkit' propos
> For example. In order to convert an instance of A to an instance of B
> we have to have a persistent function.
Let's stop right here. Why that?
What I had in mind was that the programmer keeps around, say, a file
full of those conversion functions, thereby providing legacy support
for her dat
On Dec 21, 2007, at 12:53 PM, Leslie P. Polzer wrote:
Please correct me if I'm wrong, but isn't this exactly what Lisp
does? If you assign the wrong type to a slot under SBCL, it doesn't
complain so in this sense Elephant behaves in the same way as Lisp
does with in-memory objects. At some
> Please correct me if I'm wrong, but isn't this exactly what Lisp
> does? If you assign the wrong type to a slot under SBCL, it doesn't
> complain so in this sense Elephant behaves in the same way as Lisp
> does with in-memory objects. At some point it is our responsibility
> not to shoot ourse
> which is pretty much exactly what convert-class is for, so we might just use
> this.
Yeah now, that should read "change-class" of course. Sorry.
Leslie
--
My personal blog: http://blog.viridian-project.de/
___
elephant-devel site list
elephant-
Leslie,
Please correct me if I'm wrong, but isn't this exactly what Lisp
does? If you assign the wrong type to a slot under SBCL, it doesn't
complain so in this sense Elephant behaves in the same way as Lisp
does with in-memory objects. At some point it is our responsibility
not to shoo
Hi Ian,
thanks for making it clear. Of course, I guessed this and the Elephant code
I looked at didn't say otherwise, but you're knowledge is obviously greater.
> The right user approach is to provide a function to walk over
> instances and update their representation or zero them out. Other
>
Hi Ian,
thanks for making it clear. Of course, I guessed this and the Elephant code
I looked at didn't say otherwise, but you're knowledge is obviously greater.
> The right user approach is to provide a function to walk over
> instances and update their representation or zero them out. Other
>
rats, Unfortunately I use the BDB backend and had not tested this with
postmodern.
After quick investigation my guess is that this has had adverse
effects regarding objects which have specialized intialize-instance
methods which are required to run an deserialization.
Unfortunately I'm leaving to
I have read Sean's thread about instance initialization when it was on the
list, but when it came to my special problem it didn't occur to me
that it would be solved by Sean's patch. Do you think this is the case,
Robert?
Sean's new methods recreate-instance-using-class and recreate-instance
migh
10 matches
Mail list logo
