Re: Issue 1322 in lilypond: \context must die (whenever \new can be used instead)

[lilypond]

Comment #4 on issue 1322 by Carl.D.Sorensen: \context must die (whenever  
\new can be used instead)
http://code.google.com/p/lilypond/issues/detail?id=1322

I actually *prefer* to use

\context Staff = "upper"

instead of

\new Staff = "upper"


If  I use \context Staff = "upper", then if I already have an upper staff  
defined, it doesn't create a new one.  That's the behavior I want.  This is  
very convenient when combining multiple input files in different ways to  
produce multiple editions.

What is the problem you see with using \context Staff = "upper", or the  
equivalent?  Why make the user decide what is the first use of a particular  
context, when the parser can do it just fine?

In my opinion, the only time \new should be used is when creating *unnamed*  
contexts.

Since we have the difference of opinion on this, it seems to me to be very  
premature to be proposing that we root out valid syntax from the  
documentation.

I'll be happy to have this discussion as part of GLISS.