Date: Sun, 29 Jun 2003 14:56:20 -0700 From: "Allan Bowhill" <abowhill@blarg.net> To: "Patrick Hartling" <patrick@137.org> Cc: fbsd-current <freebsd-current@freebsd.org> Subject: Re: <ftream> errors under g++ 3.2.2 Message-ID: <01ae01c33e89$46904ed0$0200000a@io> References: <013601c33e6a$eb312d70$0200000a@io> <3EFF308B.6060200@137.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> I do a lot of C++ development on -current, and I have been seeing these > exact warnings. The problem is in the fstream header, however, so there > is nothing you can do to your code to prevent the warnings. You could > modify /usr/include/g++/fstream to silence the warnings, but it would > get overwritten if you upgrade your system. Oh good :) I was thinking there was something I needed to add to make the code compliant. > From your output, I don't see compile failures, I see warnings. Do you > have -Werror turned on somewhere that wouldn't show up during normal > usage--like some environment variable or something? I was able to > compile and run your code without issue here. > > Honestly, I am surprised that a GCC header would have an implicit > typename since the compiler clearly complains loudly about them. At any > rate, I think the update to GCC 3.3 in -current is going to happen quite > soon, and presumably, the updated GCC C++ headers will have warnings > such as these fully eliminated. You're right. These are warnings, and it does compile. I guess I got a bit stuck on trying to determine why the messages were occuring. Thanks for your comments. --Allan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?01ae01c33e89$46904ed0$0200000a>