* [Q] Pragma directive to shut up the Wefc++ messages from STL??
@ 1999-05-10 9:43 gcl++ Library Development
1999-05-31 21:36 ` gcl++ Library Development
0 siblings, 1 reply; 4+ messages in thread
From: gcl++ Library Development @ 1999-05-10 9:43 UTC (permalink / raw)
To: egcs, egcs-bugs
/*
newsgroups:
comp.lang.c++
mailing lists:
egcs@cygnus.com
egcs-bugs@cygnus.com
reply to :
vcvjetko@linux.rulz.zg.tel.hr
m.cvjetko@linux.rulz.rt.e-technik.uni-erlangen.de
by removing praising the best OS
[Q] Pragma directive to shut up the Wefc++ messages from STL??
Hi again!
Is there a pragma directive or something else to shut off the
messages produced with warning option -Wefc++.
Is there a plan to "correct" causes of these warnings in STL
in the future?
Thanx a lot
Miljenko
*/
# include <vector>
int
main ()
{
vector<int> v;
return 0;
};
/*
gcl@moljac:~/gcl/src/example/Tests/syntax_standard_comformance > g++ -v
-Wall -Weffc++ -I ~/gcl/src/include STL_egcs-1.1.2._Wefc++_TO_ASK.cpp
Reading specs from /usr/lib/gcc-lib/i586-pc-linux-gnu/egcs-2.91.66/specs
gcc version egcs-2.91.66 19990314 (egcs-1.1.2 release)
/usr/lib/gcc-lib/i586-pc-linux-gnu/egcs-2.91.66/cpp -lang-c++ -v -I
/home/gcl/gcl/src/include -undef -D__GNUC__=2 -D__GNUG__=2 -D__cplusplus
-D__GNUC_MINOR__=91 -D__ELF__ -Dunix -Di386 -D__i386__ -Dlinux -D__ELF__
-D__unix__ -D__i386__ -D__i386__ -D__linux__ -D__unix -D__i386 -D__linux
-Asystem(posix) -D__EXCEPTIONS -Wall -Weffc++ -Asystem(unix) -Acpu(i386)
-Amachine(i386) -Di386 -D__i386 -D__i386__ -Di586 -Dpentium -D__i586
-D__i586__ -D__pentium -D__pentium__ STL_egcs-1.1.2._Wefc++_TO_ASK.cpp
/tmp/ccPCTtn9.ii
GNU CPP version egcs-2.91.66 19990314 (egcs-1.1.2 release) (i386
Linux/ELF)
#include "..." search starts here:
#include <...> search starts here:
/home/gcl/gcl/src/include
/usr/include/g++
/usr/local/include
/usr/i586-pc-linux-gnu/include
/usr/lib/gcc-lib/i586-pc-linux-gnu/egcs-2.91.66/include
/usr/include
End of search list.
/usr/lib/gcc-lib/i586-pc-linux-gnu/egcs-2.91.66/cc1plus
/tmp/ccPCTtn9.ii -quiet -dumpbase STL_egcs-1.1.2._Wefc++_TO_ASK.cc -Wall
-Weffc++ -version -o /tmp/ccEVeZ0q.s
GNU C++ version egcs-2.91.66 19990314 (egcs-1.1.2 release)
(i586-pc-linux-gnu) compiled by GNU C version egcs-2.91.66 19990314
(egcs-1.1.2 release).
In file included from /usr/include/g++/stl_algobase.h:53,
from /usr/include/g++/vector:30,
from STL_egcs-1.1.2._Wefc++_TO_ASK.cpp:30:
/usr/include/g++/iostream.h:112: warning: `class ostream' has pointer
data members
/usr/include/g++/iostream.h:112: warning: but does not override
`ostream(const ostream&)'
/usr/include/g++/iostream.h:112: warning: or `operator=(const
ostream&)'
/usr/include/g++/iostream.h:224: warning: `class istream' has pointer
data members
/usr/include/g++/iostream.h:224: warning: but does not override
`istream(const istream&)'
/usr/include/g++/iostream.h:224: warning: or `operator=(const
istream&)'
/usr/include/g++/iostream.h: In method `class _IO_istream_withassign &
_IO_istream_withassign::operator =(class _IO_istream_withassign &)':
/usr/include/g++/iostream.h:237: warning: `operator=' should return a
reference to `*this'
/usr/include/g++/iostream.h: In method `class _IO_ostream_withassign &
_IO_ostream_withassign::operator =(class _IO_ostream_withassign &)':
/usr/include/g++/iostream.h:244: warning: `operator=' should return a
reference to `*this'
/usr/include/g++/stl_iterator.h: At top level:
In file included from /usr/include/g++/stl_algobase.h:56,
from /usr/include/g++/vector:30,
from STL_egcs-1.1.2._Wefc++_TO_ASK.cpp:30:
/usr/include/g++/stl_iterator.h:325: warning: postfix
`back_insert_iterator<Container>::operator ++(int)' should return
`back_insert_iterator<Container>'
/usr/include/g++/stl_iterator.h:325: warning: postfix
`back_insert_iterator<Container>::operator ++(int)' should return
`back_insert_iterator<Container>'
/usr/include/g++/stl_iterator.h:363: warning: postfix
`front_insert_iterator<Container>::operator ++(int)' should return
`front_insert_iterator<Container>'
/usr/include/g++/stl_iterator.h:363: warning: postfix
`front_insert_iterator<Container>::operator ++(int)' should return
`front_insert_iterator<Container>'
/usr/include/g++/stl_iterator.h:404: warning: postfix
`insert_iterator<Container>::operator ++(int)' should return
`insert_iterator<Container>'
/usr/include/g++/stl_iterator.h:404: warning: postfix
`insert_iterator<Container>::operator ++(int)' should return
`insert_iterator<Container>'
/usr/include/g++/stl_iterator.h:824: warning: postfix
`ostream_iterator<T>::operator ++(int)' should return
`ostream_iterator<T>'
/usr/include/g++/stl_iterator.h:824: warning: postfix
`ostream_iterator<T>::operator ++(int)' should return
`ostream_iterator<T>'
In file included from /usr/include/g++/vector:35,
from STL_egcs-1.1.2._Wefc++_TO_ASK.cpp:30:
/usr/include/g++/stl_bvector.h:65: warning: `struct __bit_reference' has
pointer data members
/usr/include/g++/stl_bvector.h:65: warning: but does not override
`__bit_reference(const __bit_reference&)'
/usr/include/g++/stl_bvector.h: In method `struct __bit_reference &
__bit_reference::operator =(const struct __bit_reference &)':
/usr/include/g++/stl_bvector.h:57: warning: `operator=' should return a
reference to `*this'
/usr/include/g++/stl_bvector.h: At top level:
/usr/include/g++/stl_bvector.h:150: warning: `struct __bit_iterator' has
pointer data members
/usr/include/g++/stl_bvector.h:150: warning: but does not override
`__bit_iterator(const __bit_iterator&)'
/usr/include/g++/stl_bvector.h:150: warning: or `operator=(const
__bit_iterator&)'
/usr/include/g++/stl_bvector.h:237: warning: `struct
__bit_const_iterator' has pointer data members
/usr/include/g++/stl_bvector.h:237: warning: but does not override
`__bit_const_iterator(const __bit_const_iterator&)'
/usr/include/g++/stl_bvector.h:237: warning: or `operator=(const
__bit_const_iterator&)'
as -V -Qy -o /tmp/ccniZDtx.o /tmp/ccEVeZ0q.s
GNU assembler version 2.9.1 (i486-linux), using BFD version 2.9.1.0.15
/usr/lib/gcc-lib/i586-pc-linux-gnu/egcs-2.91.66/collect2 -m elf_i386
-dynamic-linker /lib/ld-linux.so.2 /usr/lib/crt1.o /usr/lib/crti.o
/usr/lib/gcc-lib/i586-pc-linux-gnu/egcs-2.91.66/crtbegin.o
-L/usr/lib/gcc-lib/i586-pc-linux-gnu/egcs-2.91.66
-L/usr/i586-pc-linux-gnu/lib /tmp/ccniZDtx.o -lstdc++ -lm -lgcc -lc
-lgcc /usr/lib/gcc-lib/i586-pc-linux-gnu/egcs-2.91.66/crtend.o
/usr/lib/crtn.o
*/
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Q] Pragma directive to shut up the Wefc++ messages from STL??
1999-05-10 9:43 [Q] Pragma directive to shut up the Wefc++ messages from STL?? gcl++ Library Development
@ 1999-05-31 21:36 ` gcl++ Library Development
0 siblings, 0 replies; 4+ messages in thread
From: gcl++ Library Development @ 1999-05-31 21:36 UTC (permalink / raw)
To: egcs, egcs-bugs
/*
newsgroups:
comp.lang.c++
mailing lists:
egcs@cygnus.com
egcs-bugs@cygnus.com
reply to :
vcvjetko@linux.rulz.zg.tel.hr
m.cvjetko@linux.rulz.rt.e-technik.uni-erlangen.de
by removing praising the best OS
[Q] Pragma directive to shut up the Wefc++ messages from STL??
Hi again!
Is there a pragma directive or something else to shut off the
messages produced with warning option -Wefc++.
Is there a plan to "correct" causes of these warnings in STL
in the future?
Thanx a lot
Miljenko
*/
# include <vector>
int
main ()
{
vector<int> v;
return 0;
};
/*
gcl@moljac:~/gcl/src/example/Tests/syntax_standard_comformance > g++ -v
-Wall -Weffc++ -I ~/gcl/src/include STL_egcs-1.1.2._Wefc++_TO_ASK.cpp
Reading specs from /usr/lib/gcc-lib/i586-pc-linux-gnu/egcs-2.91.66/specs
gcc version egcs-2.91.66 19990314 (egcs-1.1.2 release)
/usr/lib/gcc-lib/i586-pc-linux-gnu/egcs-2.91.66/cpp -lang-c++ -v -I
/home/gcl/gcl/src/include -undef -D__GNUC__=2 -D__GNUG__=2 -D__cplusplus
-D__GNUC_MINOR__=91 -D__ELF__ -Dunix -Di386 -D__i386__ -Dlinux -D__ELF__
-D__unix__ -D__i386__ -D__i386__ -D__linux__ -D__unix -D__i386 -D__linux
-Asystem(posix) -D__EXCEPTIONS -Wall -Weffc++ -Asystem(unix) -Acpu(i386)
-Amachine(i386) -Di386 -D__i386 -D__i386__ -Di586 -Dpentium -D__i586
-D__i586__ -D__pentium -D__pentium__ STL_egcs-1.1.2._Wefc++_TO_ASK.cpp
/tmp/ccPCTtn9.ii
GNU CPP version egcs-2.91.66 19990314 (egcs-1.1.2 release) (i386
Linux/ELF)
#include "..." search starts here:
#include <...> search starts here:
/home/gcl/gcl/src/include
/usr/include/g++
/usr/local/include
/usr/i586-pc-linux-gnu/include
/usr/lib/gcc-lib/i586-pc-linux-gnu/egcs-2.91.66/include
/usr/include
End of search list.
/usr/lib/gcc-lib/i586-pc-linux-gnu/egcs-2.91.66/cc1plus
/tmp/ccPCTtn9.ii -quiet -dumpbase STL_egcs-1.1.2._Wefc++_TO_ASK.cc -Wall
-Weffc++ -version -o /tmp/ccEVeZ0q.s
GNU C++ version egcs-2.91.66 19990314 (egcs-1.1.2 release)
(i586-pc-linux-gnu) compiled by GNU C version egcs-2.91.66 19990314
(egcs-1.1.2 release).
In file included from /usr/include/g++/stl_algobase.h:53,
from /usr/include/g++/vector:30,
from STL_egcs-1.1.2._Wefc++_TO_ASK.cpp:30:
/usr/include/g++/iostream.h:112: warning: `class ostream' has pointer
data members
/usr/include/g++/iostream.h:112: warning: but does not override
`ostream(const ostream&)'
/usr/include/g++/iostream.h:112: warning: or `operator=(const
ostream&)'
/usr/include/g++/iostream.h:224: warning: `class istream' has pointer
data members
/usr/include/g++/iostream.h:224: warning: but does not override
`istream(const istream&)'
/usr/include/g++/iostream.h:224: warning: or `operator=(const
istream&)'
/usr/include/g++/iostream.h: In method `class _IO_istream_withassign &
_IO_istream_withassign::operator =(class _IO_istream_withassign &)':
/usr/include/g++/iostream.h:237: warning: `operator=' should return a
reference to `*this'
/usr/include/g++/iostream.h: In method `class _IO_ostream_withassign &
_IO_ostream_withassign::operator =(class _IO_ostream_withassign &)':
/usr/include/g++/iostream.h:244: warning: `operator=' should return a
reference to `*this'
/usr/include/g++/stl_iterator.h: At top level:
In file included from /usr/include/g++/stl_algobase.h:56,
from /usr/include/g++/vector:30,
from STL_egcs-1.1.2._Wefc++_TO_ASK.cpp:30:
/usr/include/g++/stl_iterator.h:325: warning: postfix
`back_insert_iterator<Container>::operator ++(int)' should return
`back_insert_iterator<Container>'
/usr/include/g++/stl_iterator.h:325: warning: postfix
`back_insert_iterator<Container>::operator ++(int)' should return
`back_insert_iterator<Container>'
/usr/include/g++/stl_iterator.h:363: warning: postfix
`front_insert_iterator<Container>::operator ++(int)' should return
`front_insert_iterator<Container>'
/usr/include/g++/stl_iterator.h:363: warning: postfix
`front_insert_iterator<Container>::operator ++(int)' should return
`front_insert_iterator<Container>'
/usr/include/g++/stl_iterator.h:404: warning: postfix
`insert_iterator<Container>::operator ++(int)' should return
`insert_iterator<Container>'
/usr/include/g++/stl_iterator.h:404: warning: postfix
`insert_iterator<Container>::operator ++(int)' should return
`insert_iterator<Container>'
/usr/include/g++/stl_iterator.h:824: warning: postfix
`ostream_iterator<T>::operator ++(int)' should return
`ostream_iterator<T>'
/usr/include/g++/stl_iterator.h:824: warning: postfix
`ostream_iterator<T>::operator ++(int)' should return
`ostream_iterator<T>'
In file included from /usr/include/g++/vector:35,
from STL_egcs-1.1.2._Wefc++_TO_ASK.cpp:30:
/usr/include/g++/stl_bvector.h:65: warning: `struct __bit_reference' has
pointer data members
/usr/include/g++/stl_bvector.h:65: warning: but does not override
`__bit_reference(const __bit_reference&)'
/usr/include/g++/stl_bvector.h: In method `struct __bit_reference &
__bit_reference::operator =(const struct __bit_reference &)':
/usr/include/g++/stl_bvector.h:57: warning: `operator=' should return a
reference to `*this'
/usr/include/g++/stl_bvector.h: At top level:
/usr/include/g++/stl_bvector.h:150: warning: `struct __bit_iterator' has
pointer data members
/usr/include/g++/stl_bvector.h:150: warning: but does not override
`__bit_iterator(const __bit_iterator&)'
/usr/include/g++/stl_bvector.h:150: warning: or `operator=(const
__bit_iterator&)'
/usr/include/g++/stl_bvector.h:237: warning: `struct
__bit_const_iterator' has pointer data members
/usr/include/g++/stl_bvector.h:237: warning: but does not override
`__bit_const_iterator(const __bit_const_iterator&)'
/usr/include/g++/stl_bvector.h:237: warning: or `operator=(const
__bit_const_iterator&)'
as -V -Qy -o /tmp/ccniZDtx.o /tmp/ccEVeZ0q.s
GNU assembler version 2.9.1 (i486-linux), using BFD version 2.9.1.0.15
/usr/lib/gcc-lib/i586-pc-linux-gnu/egcs-2.91.66/collect2 -m elf_i386
-dynamic-linker /lib/ld-linux.so.2 /usr/lib/crt1.o /usr/lib/crti.o
/usr/lib/gcc-lib/i586-pc-linux-gnu/egcs-2.91.66/crtbegin.o
-L/usr/lib/gcc-lib/i586-pc-linux-gnu/egcs-2.91.66
-L/usr/i586-pc-linux-gnu/lib /tmp/ccniZDtx.o -lstdc++ -lm -lgcc -lc
-lgcc /usr/lib/gcc-lib/i586-pc-linux-gnu/egcs-2.91.66/crtend.o
/usr/lib/crtn.o
*/
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Q] Pragma directive to shut up the Wefc++ messages from STL?
1999-05-10 10:20 [Q] Pragma directive to shut up the Wefc++ messages from STL? Edwards, Phil
@ 1999-05-31 21:36 ` Edwards, Phil
0 siblings, 0 replies; 4+ messages in thread
From: Edwards, Phil @ 1999-05-31 21:36 UTC (permalink / raw)
To: 'egcs@egcs.cygnus.com'
Cc: 'm.cvjetko@rt.e-technik.uni-erlangen.de',
'egcs-bugs@egcs.cygnus.com'
Perhaps I should have trimmed egcs-bugs from the list of recipients.
+ Is there a pragma directive or something else to shut off the
+ messages produced with warning option -Wefc++.
Not at the moment. I haven't heard of any plans to implement such, but I'm
hardly an authoritative source. This falls into the category of, "if you
don't want the messages, don't add the warning option."
When I use -Weffc++, I often pipe the results through a grep or two in order
to remove those. It's not a problme during development, since I don't use
-Weffc++ during development for just this reason. I just fire it up at the
end to see what I may have missed.
+ Is there a plan to "correct" causes of these warnings in STL
+ in the future?
This is the only remaining empty stub in the initial libstdc++ FAQ... There
was a big discussion on the libstdc++-v3 list about Weff, but it occured
before the list was archived, and I don't recall much of it now.
I think the consensus was, "first we get the missing stuff working."
Phil
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Q] Pragma directive to shut up the Wefc++ messages from STL?
@ 1999-05-10 10:20 Edwards, Phil
1999-05-31 21:36 ` Edwards, Phil
0 siblings, 1 reply; 4+ messages in thread
From: Edwards, Phil @ 1999-05-10 10:20 UTC (permalink / raw)
To: 'egcs@egcs.cygnus.com'
Cc: 'm.cvjetko@rt.e-technik.uni-erlangen.de',
'egcs-bugs@egcs.cygnus.com'
Perhaps I should have trimmed egcs-bugs from the list of recipients.
+ Is there a pragma directive or something else to shut off the
+ messages produced with warning option -Wefc++.
Not at the moment. I haven't heard of any plans to implement such, but I'm
hardly an authoritative source. This falls into the category of, "if you
don't want the messages, don't add the warning option."
When I use -Weffc++, I often pipe the results through a grep or two in order
to remove those. It's not a problme during development, since I don't use
-Weffc++ during development for just this reason. I just fire it up at the
end to see what I may have missed.
+ Is there a plan to "correct" causes of these warnings in STL
+ in the future?
This is the only remaining empty stub in the initial libstdc++ FAQ... There
was a big discussion on the libstdc++-v3 list about Weff, but it occured
before the list was archived, and I don't recall much of it now.
I think the consensus was, "first we get the missing stuff working."
Phil
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~1999-05-31 21:36 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1999-05-10 9:43 [Q] Pragma directive to shut up the Wefc++ messages from STL?? gcl++ Library Development
1999-05-31 21:36 ` gcl++ Library Development
1999-05-10 10:20 [Q] Pragma directive to shut up the Wefc++ messages from STL? Edwards, Phil
1999-05-31 21:36 ` Edwards, Phil
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).