Re: Issue 1316 in lilypond: Enhancement: improved << \\ >> polyphonic shortcut notation

[lilypond]

Comment #2 on issue 1316 by x.scheuer: Enhancement: improved << \\ >>  
polyphonic shortcut notation
http://code.google.com/p/lilypond/issues/detail?id=1316

I am really pleased to see LilyPond's founder replying to this issue,
although (as a user) I have no idea of the meaning of what he said.
;-p
But I suspect it is not good news for the resolution of this issue...
:-(

I have an additional suggestion:
I'd like the second voice, created *within* the << \\ >> construct,
to be named from first "main" voice's name (from outside the polyphony).

For example, if first, main, voice is called "PianoUpper", then the
second voice, created *within* the << \\ >> construct, would be called
"PianoUpper2".

As an example, the << { ... } \\ { ... } >> construct in the case of
"PianoUpper" would be equivalent to the following polyphony
(with instantied voices):

pianoUpper = \new Voice = "PianoUpper" {
  % beginning of "PianoUpper", not polyphonic

  <<
    {
      % continuation of the main Voice "PianoUpper" from outside the
      % polyphony
      \voiceOne
      ...
    }
    \context Voice = "PianoUpper2" {  % see the name here?
      \voiceTwo
      ...
    }
  >> \oneVoice
  % following of "PianoUpper", not polyphonic


http://lists.gnu.org/archive/html/lilypond-devel/2010-11/msg00199.html