[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Part_combine_iterator::last_playing_ notinitialized
From: |
Keith OHara |
Subject: |
Re: Part_combine_iterator::last_playing_ notinitialized |
Date: |
Sun, 21 Aug 2011 20:39:37 +0000 (UTC) |
User-agent: |
Loom/3.14 (http://gmane.org/) |
Phil Holmes <mail <at> philholmes.net> writes:
> >> "Dan Eble" <dan <at> faithful.be> wrote in message
> >> news:loom.20110821T044324-635 <at> post.gmane.org...
> >>
> >> > % valgrind reports that a member of Part_combine_iterator is used
> >> > % before being initialized. Initializing last_playing_ = SOLO1 in
> >> > % the constructor makes the warning go away.
>
> You want this adding to the tracker?
>
Probably that was Dan's intent, but I would not add it, because there is no
behavior of LilyPond to test. The issue has existed since 2004 or before.
(You could add it as a suggested patch if you like.)
If no-one suggests differently I'll add an initialization in a couple days,
along with fixing a couple other un-initialized variables.
-Keith
Re: Part_combine_iterator::last_playing_ not initialized, Dmytro O. Redchuk, 2011/08/22