They should both stay, people may want access to the primitives (for
example a set of sets) and there is no reason not to provide it.
Ian
On Jun 29, 2008, at 10:22 AM, Glenn Tarcea wrote:
Ian,
The set-valued-slots are very nice. I've been playing around with
them to write the documentatio
Ian,
The set-valued-slots are very nice. I've been playing around with
them to write the documentation and have found they will cleanup some
code I had written using make-pset. One question: Should the write up
on PSETs remain in the documentation, or should there be a write up
to migrate
> (set-list object 'slotname)
I'd call it set->list, but that's probably a matter of
personal preference...
___
elephant-devel site list
elephant-devel@common-lisp.net
http://common-lisp.net/mailman/listinfo/elephant-devel
Great stuff!
To answer a couple of questions:
- Cached slots aren't ready yet; I'll document when I can work out the
kinks:
- Indexed slots are the same as the existing indexed-slots
descriptions, except for
the :inherit slot option so you should be able to copy & paste
existing content
Attached are updates to the documentation. Specifically I updated:
1. Section: Setting Up Berkeley DB - to include the additional flags
(:berkeley-db-max-locks and :berkeley-db-max-objects) along with
their descriptions and updated the list of of parameters in the my-
config.sexp
2. Added
I started this from Ian's posted list and added my own. Please add to,
delete from or change as appropriate.
1) Update all class indexing docs, especially derived indices (dropped
explicit API, hierarchical indexed slots)
2) Document new slot options in defpclass
3) Document associations
4)
