On 9/19/12, Eric Botcazou <ebotca...@adacore.com> wrote: > > The language syntax would bind the conditional into the > > intializer, as in > > > > if (varpool_node *vnode = (node->try_variable () > > && vnode->finalized)) > > varpool_analyze_node (vnode); > > > > which does not type-match. > > > > So, if you want the type saftey and performance, the cascade > > is really unavoidable. > > Just write: > > varpool_node *vnode; > > if ((vnode = node->try_variable ()) && vnode->finalized) > varpool_analyze_node (vnode); > > This has been the standard style for the past 2 decades and > trading it for cascading if's is really a bad idea.
Assignments in if statements are known to cause confusion. The point of the change is to limit the scope of the variable to the if statement, which prevents its unintended use later. It acts like a type switch. Why do you think cascading ifs is a bad idea? -- Lawrence Crowl
