>>> "David PONCE" <David.Ponce@...> seems to think that:
Good ideas. Please check them in.
>> These are good arguments. If a new user wrote a parser, and the
>> incremental step failed, how would they learn about this trick? Can
>> you think of a way to wrap a good name/function/variable around it
>> such that we can reference it in doc-strings to be easily found?
>Maybe that could be documented in the doc string of the function
>`semantic-edits-change-function-handle-changes' which provides the
>various change hooks. As its doc string already says it "Tracks when
>and how the buffer is re-parsed.", it seems natural to add here some
>explanation on the provided hooks and how they can be used to track
>changes (like does `semantic-highlight-edits-new-change-hook-fcn'), or
>to adapt changes to specific contexts (like does
>Also `semantic-edits-change-function-handle-changes' is already
>referenced from the doc string of `semantic-edits-incremental-parser',
>which is the obvious point to start from, when looking for
>documentation on the incremental parser :-)
>What do you thing?
>>>P.S.: What about the other changes in semantic-edit?
>> [ ... ]
>> That looked looked a good idea.
>So I can check my change in?
[ ... ]
Eric Ludlam: zappo@..., eric@...
Home: http://www.ludlam.net Siege: http://www.siege-engine.com
Emacs: http://cedet.sourceforge.net GNU: http://www.gnu.org