[climacs-devel] update-syntax and delegating buffers
Aleksandar Bakic
a_bakic at yahoo.com
Mon Mar 7 18:55:09 UTC 2005
Hi,
Is your update-syntax method in the cvs? I tried not to break things, sorry...
I suppose we can move name-mixin into extended-standard-buffer's superclass
list. I thought we should perhaps not have extended-*-buffer or climacs-buffer
inherit just about anything, i.e., I'd like to hear arguments for and against
cases like yours.
The rationale for the delegating-buffer is to allow for specifying the buffer
implementation at run time. When implementing it, I found that, in order to
minimize changes in the existing code, the simplest solution was to delegate
the two syntax-related methods, too. However, I had not planned for this, so
please suggest how you would like it changed and I'll try to do it asap.
Regards,
Alex
> Hi,
>
> The change to delegating buffers has had a side effect for me: my
> UPDATE-SYNTAX method used to be able to obtain the name of the buffer
> it was updating for, but it can no longer, because the
> delegating-buffer method for update-syntax calls update-syntax on the
> implementation buffer, which doesn't mix in the name-mixin class.
>
> Is there a reason for this surrounding method? Is it simply to save a
> generic function call per buffer operation? Should I not be
> attempting to find the name of a buffer from within UPDATE-SYNTAX?
>
> Thanks,
>
> Christophe
__________________________________
Celebrate Yahoo!'s 10th Birthday!
Yahoo! Netrospective: 100 Moments of the Web
http://birthday.yahoo.com/netrospective/
More information about the climacs-devel
mailing list