@RichFelker so the problem is that the conditions were not sequenced properly? i'm not sure why initializing the value matters here...
-
-
-
@jduck See commit message. The patch that moved the assignment across the the use would have produced warnings if not for the default-init. -
@jduck Setting l=1 by default rather than having "else l=1;" in the appropriate place prevented the compiler from diagnosing the mistake. -
@jduck This is also why I don't like adding dummy initialization to quiet "may be used uninitialized" warnings. -
@RichFelker fair enough! you're one of the few out there that even pays any mind to warnings anyway :-) -
@jduck@RichFelker Oh I do to. "May be" and "Is" are 2 diff warnings. Second is real, silence first with "int a = a;" at declaration. -
-
- 4 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.