Re: <ftream> errors under g++ 3.2.2

From: Allan Bowhill (abowhill_at_blarg.net)
Date: 06/29/03

  • Next message: Evan S.: "palm issues" 
    To: "Patrick Hartling" <patrick@137.org>
Date: Sun, 29 Jun 2003 14:56:20 -0700

    > 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
    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"

  • Next message: Evan S.: "palm issues"

    Relevant Pages

    • RE: Redhat 9.0 development environment wierdness...
      ... It still has the warnings you posted. ... setup depends on you or the project you are trying to compile. ... Redhat 9.0 development environment wierdness... ... need to install on our servers and if I can't even get through these I ...
      (RedHat)
    • Re: does VS C++ 2005 actually work????
      ... may be the same size as a pointer, they have nothing logically to do with ... sizeofand size_t generating warnings when used in the context of API ... I can't compile ... justified criticism regarding the reliability of Windows. ...
      (microsoft.public.vc.mfc)
    • Re: 2.6.23.9-rt13
      ... If I compile -rt13 I get some compile warnings on ARM: ... Both warnings are fixed by the attached patch, but warning 2 needs some review. ... New changes by Steven Rostedt, Gregory Haskins, ... Revert lazy disable irq from simple irq handler ...
      (Linux-Kernel)
    • Re: <ftream> errors under g++ 3.2.2
      ... > gives error messages about implicit typenames being deprecated, ... is nothing you can do to your code to prevent the warnings. ... From your output, I don't see compile failures, I see warnings. ... I am surprised that a GCC header would have an implicit ...
      (freebsd-current)
    • Re: Using unused variables
      ... I get loads of "unused variable" warnings during compile ... Compiler switches that disable reporting of unused variables are out of ... which may draw dead code diagnostics from aggressive optimizing compilers. ...
      (comp.lang.fortran)