> -----Original Message----- > From: Eric Lemings [mailto:[EMAIL PROTECTED] > Sent: Wednesday, April 16, 2008 9:39 AM > To: [email protected] > Subject: RE: New 27.basic.ios.cpp test migrated (LONG) > > > > > -----Original Message----- > > From: Martin Sebor [mailto:[EMAIL PROTECTED] On Behalf Of > Martin Sebor > > Sent: Tuesday, April 15, 2008 10:46 PM > > To: [email protected] > > Subject: Re: New 27.basic.ios.cpp test migrated (LONG) > > > > Martin Sebor wrote: > > [...] > > > Finally, every function is extern by default. There is no need > > > to explicitly declare it as such (I believe there are compilers > > > that warn about function definitions with the extern keyword). > > > > FYI, here's an example of the diagnostic (issued by HP aCC 6) > > from our nightly builds I was referring to above: > > > > "$(TOPDIR)/src/ti_num_get.cpp", line 51: remark #4244-D: > > extern storage > > class used with a function definition > > _RWSTD_DEFINE_FACET_FACTORY (extern _RWSTD_EXPORT, > > num_get, TARGS_C, > > num_get); > > ^ > > Another "useful" compiler warning? I'm not surprised. HP aCC 6 has > about as many real warnings as MSVC 8 and 9. You just can't put much > stock in compiler warnings these days. > > I wonder what the rationale for the warning is? The syntax and > semantics > of C and C++ clearly allows extern specifiers in function definitions. > I'll have to look it up in HP's aCC docs.
Yeah, here's the "rationale" for the warning: http://www.docs.hp.com/en/11925/Diagnostics_Documentation/Diagnostics_in dex.htm#4244 In short, there is no reason for the warning; it's just more nonsensical verbage. Brad.
