From reddaly at gmail.com Tue Jul 14 23:01:30 2009 From: reddaly at gmail.com (Red Daly) Date: Tue, 14 Jul 2009 16:01:30 -0700 Subject: [elephant-devel] Class Heirarchies and Queries In-Reply-To: <7239FF41-4CEA-4E2E-B7B5-4F20D29330DD@media.mit.edu> References: <42c0ab790809151731l52b36eb7i42b4cc9c23294f57@mail.gmail.com> <62591.84.157.46.71.1221557338.squirrel@mail.stardawn.org> <3237650F6D014CF19571172A4E5B386C@killer> <61103.84.157.46.71.1221565997.squirrel@mail.stardawn.org> <7239FF41-4CEA-4E2E-B7B5-4F20D29330DD@media.mit.edu> Message-ID: On Tue, Sep 16, 2008 at 7:20 AM, Ian Eslick wrote: > There is an :inherit slot keyword option for indexed slots. It causes > subclasses of the defining class to share the index of the base class. You > can inhibit subclass sharing by re-defining the slot in the base class. I > found a bug in unstable and patched it so this works again. As far as I can tell, this feature is now missing. Am I mistaken? > > > Calling map-inverted-index (and the top-level API fn's > get-instances-by-value/range) from the base or subclasses will return > instances for all classes that share that base index. We could add some > refinements such as mapping from a subclass filters out any superclass > instances during the traversal. > > We can easily add a keyword arg to map-class and get-instances-by-class to > return all subclass instances as well. > > Ian Red -------------- next part -------------- An HTML attachment was scrubbed... URL: From eslick at media.mit.edu Wed Jul 15 04:21:24 2009 From: eslick at media.mit.edu (Ian Eslick) Date: Tue, 14 Jul 2009 21:21:24 -0700 Subject: [elephant-devel] Class Heirarchies and Queries In-Reply-To: References: <42c0ab790809151731l52b36eb7i42b4cc9c23294f57@mail.gmail.com> <62591.84.157.46.71.1221557338.squirrel@mail.stardawn.org> <3237650F6D014CF19571172A4E5B386C@killer> <61103.84.157.46.71.1221565997.squirrel@mail.stardawn.org> <7239FF41-4CEA-4E2E-B7B5-4F20D29330DD@media.mit.edu> Message-ID: Works for me on the elephant-1.0 repository. You have to indicate in the base class that subclasses will inherit its index. Then you do get-instances-by-value/range on any class on the inherited slotname to get all instances inheriting from the base. Ian On Jul 14, 2009, at 4:01 PM, Red Daly wrote: > On Tue, Sep 16, 2008 at 7:20 AM, Ian Eslick > wrote: > There is an :inherit slot keyword option for indexed slots. It > causes subclasses of the defining class to share the index of the > base class. You can inhibit subclass sharing by re-defining the > slot in the base class. I found a bug in unstable and patched it so > this works again. > > As far as I can tell, this feature is now missing. Am I mistaken? > > > > Calling map-inverted-index (and the top-level API fn's get-instances- > by-value/range) from the base or subclasses will return instances > for all classes that share that base index. We could add some > refinements such as mapping from a subclass filters out any > superclass instances during the traversal. > > We can easily add a keyword arg to map-class and get-instances-by- > class to return all subclass instances as well. > > Ian > > Red > > _______________________________________________ > elephant-devel site list > elephant-devel at common-lisp.net > http://common-lisp.net/mailman/listinfo/elephant-devel -------------- next part -------------- An HTML attachment was scrubbed... URL: From sky at viridian-project.de Wed Jul 22 13:50:38 2009 From: sky at viridian-project.de (Leslie P. Polzer) Date: Wed, 22 Jul 2009 15:50:38 +0200 (CEST) Subject: [elephant-devel] Release 1.0b1 In-Reply-To: <0353c4742dfdb80f8c8f6d3e3c214428.squirrel@mail.stardawn.org> References: <0353c4742dfdb80f8c8f6d3e3c214428.squirrel@mail.stardawn.org> Message-ID: <498feefea17bf4f021324fb94cad5533.squirrel@mail.stardawn.org> 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 From eslick at media.mit.edu Thu Jul 23 01:55:16 2009 From: eslick at media.mit.edu (Ian Eslick) Date: Wed, 22 Jul 2009 21:55:16 -0400 Subject: [elephant-devel] Release 1.0b1 In-Reply-To: <498feefea17bf4f021324fb94cad5533.squirrel@mail.stardawn.org> References: <0353c4742dfdb80f8c8f6d3e3c214428.squirrel@mail.stardawn.org> <498feefea17bf4f021324fb94cad5533.squirrel@mail.stardawn.org> Message-ID: 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 > > > _______________________________________________ > elephant-devel site list > elephant-devel at common-lisp.net > http://common-lisp.net/mailman/listinfo/elephant-devel From sky at viridian-project.de Sat Jul 25 18:29:04 2009 From: sky at viridian-project.de (Leslie P. Polzer) Date: Sat, 25 Jul 2009 20:29:04 +0200 (CEST) Subject: [elephant-devel] Release 1.0b1 In-Reply-To: References: <0353c4742dfdb80f8c8f6d3e3c214428.squirrel@mail.stardawn.org> <498feefea17bf4f021324fb94cad5533.squirrel@mail.stardawn.org> Message-ID: 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