------- Comment #10 from bart dot vanassche at gmail dot com 2010-02-24 19:10 ------- (In reply to comment #9) > I think there is no reasonable way to get reliable uninitialized variable > warnings for incoming pointed-to memory. The only way we can warn here > is by inlining the constructor into the caller to see either a static > variable or the memory allocation.
Why would inlining the constructor be necessary ? Does this mean that it is not possible to mark member variables as uninitialized in gcc ? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19808
