"Steven E. Harris" <[EMAIL PROTECTED]> writes:

> In that case, your proposal to use an extra reference before the
> Musing constructor sounds like the best way to go, assuming that you
> can't trust people to follow a coding guideline forbidding
> temporaries as arguments to MM().

Which returns us to what I think was the original question: is there
some combination of code and gcc warning options that would
automatically enforce (or at least detect the violation of) such a
coding guideline?

(I don't think there is, but it's the kind of warning flag that
*ought* to exist, especially since the lifetime of temporaries has
changed not so long ago, so it's entirely possible I'm missing it in
the docs.)


_______________________________________________
Monotone-devel mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/monotone-devel

Reply via email to