Re: Compiled COMPILE forms at load time Bug
Raymond Toy <[email protected]>
| Newsgroups | gmane.lisp.cmucl.devel |
|---|---|
| Message-ID | <[email protected]> |
On 3/16/10 7:16 AM, Helmut Eller wrote: > For (defun some-existing-accessor ..) I'd like to see a warning at > compile time--if it can be done easily. This already happens. A simple test shows that we get the warning when compiling, and another warning when loading the fasl. > > > At load time, a cerror if the whole structure gets removed; no warning > if only the accessor gets overwritten. We have already definition locks > which can be used for more delicate accessor names. > I didn't quite follow you here. We already get a cerror if we redefine a structure. So if an accessor is redefined, we just silently allow it? > > On one side (setf (fdefinition ..)) should delete/overwrite the stuff > that a previous %%defun left in the info db. On the other hand, if the > user wants to update the info db he can and should use defun. > Hmm.. actually I prefer the latter, i.e. what CMUCL does currently. > > Sounds good to me. Ray