<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Brandon Pearcy wrote:
<blockquote
cite="mid:e6daa70e0911011116w1c748f12q79561181e5b5a9b2@mail.gmail.com"
type="cite">Hi John,<br>
<br>
<div class="gmail_quote">On Thu, Oct 29, 2009 at 12:48 PM, John
McCall <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:rjmccall@apple.com">rjmccall@apple.com</a>></span>
wrote:
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000">Like I said in the bug, I
think there are common cases we can
green-light a warning for: for example, if we're passing an
uninitialized field by reference to a copy constructor, then sure,
let's warn about it. But for arbitrary function calls? No.</div>
</blockquote>
<div><br>
</div>
<div>Okay, I'm going to submit a new patch that does not attempt to
handle function calls w/ uninit arguments. You are right; it is not
smart to enforce style, and it is complicated to know if the function
is taking a pointer or reference, in combination with any operators
upon the field itself. It is easier (for now) to just whitelist the
function call case completely.</div>
<div><br>
</div>
</div>
Sound good?</blockquote>
<br>
I think that's a good call. If we become worried about function calls,
we can write the code to white-list it later.<br>
<br>
John.<br>
</body>
</html>