Re: [Lilypond-auto] Issue 2449 in lilypond: Redesign stream event class representation

[lilypond]

Comment #27 on issue 2449 by address@hidden: Redesign stream event class  
representation
http://code.google.com/p/lilypond/issues/detail?id=2449

I am not overly happy with the complete lack of feedback, seeing that this  
sketch reorganizes some more fundamental parts of LilyPond.  The "user  
interfaces" can't be considered coherent and/or complete.  However, this  
patch at least reorganizes parts of the internals in a manner that makes  
sense within the current framework, is reasonably efficient, and addresses  
the fundamental design error of \define-event-class, changing  
scheme-text-spanner.ly in the process to work in a saner manner.

The amount of tampering with internals that scheme-text-spanner does is  
still quite inappropriate for a snippet, but at least the current code  
violates fewer assumptions around which LilyPond has been designed and  
forms a better starting base for creating a user interface outside of the  
snippet itself, like issue 2503 is supposed to do.

So even while this was rather intended as a discussion/implementation base,  
it is an improvement over the current state of affairs, and as such I  
_will_ commit it even if no discussion actually happened.