Re: [cedet-eieio] Cleaning up the EIEIO namespace
David Engster <[email protected]> Thu, 14 Feb 2013 22:17:56 +0100
| Newsgroups | gmane.emacs.devel,gmane.emacs.eieio |
|---|---|
| Message-ID | <[email protected]> |
Stefan Monnier writes: >> setf is part of cl, and couldn't be used at runtime, so I mocked >> up the behavior with something matching aref/aset instead. > > Actually, there's a misunderstanding here: > - setf was indeed part of CL, but being a macro it was accepted > (i.e. you don't need to have it defined at run-time, since it's > macro-expanded during compilation). > - setf is part of core Elisp in Emacs-24.3. > So maybe we don't need oref/oset at all. Yes, although I like "(oset foo bar 'baz)" much better than the verbose (setf (cl-slot-value foo 'bar) 'baz) But I can understand that you want to get rid of it, and package writers can still define their own macros/accessors. Our problem on the CEDET side is that we want to stay compatible with older Emacsen, so we'll need some compat package. > We could even justify the "cl-" prefix by making cl-lib autoload > `cl-slot-value' from eieio.el. Or use the "eieio-" prefix everywhere > in eieio*.el and then define "cl-" aliases in cl-lib.el. Doesn't that mean that requiring cl-lib would load the full EIEIO package? -David