[climacs-devel] Marks, Buffers and Panes

[Robert Strandh]

Hello, 

John Q Splittist writes:
 > In general this works very well - com-foo calls foo with (point
 > (current-window)), com-bar (numarg) calls bar with point and count, and
 > so on. Where it doesn't work is if foo or bar need to know what the
 > current syntax for a buffer is, because, for example, they call
 > end-of-definition, which specializes on syntax. The problem is that from
 > a supplied mark, the function foo can only access the implementation
 > buffer, not the enclosing delegating buffer, which is where the syntax is.
 > 
 > One answer would be to put a slot on delagatee buffers which points back
 > at their delegates. While convenient, I fear this breaks some part of
 > the abstraction. So I ask for comments.

I don't see why it would.  You could conveniently hide this in an 
methods (syntax buffer) and (setf (syntax buffer)) that call
themselves on the delegate.

-- 
Robert Strandh

---------------------------------------------------------------------
Greenspun's Tenth Rule of Programming: any sufficiently complicated C
or Fortran program contains an ad hoc informally-specified bug-ridden
slow implementation of half of Common Lisp.
---------------------------------------------------------------------