From: mdruiter AT cs DOT vu DOT nl Newsgroups: comp.os.msdos.djgpp Subject: Re: __attribute__((unused)), gcc get's confused...? Date: Mon, 2 Aug 1999 12:06:41 GMT Organization: Fac. Wiskunde & Informatica, VU, Amsterdam Lines: 18 Message-ID: <7o41kh$2la@cs.vu.nl> References: <379CDE99 DOT 3E957B4 AT unb DOT ca> <7nkach$sak AT cs DOT vu DOT nl> NNTP-Posting-Host: galjas.cs.vu.nl X-Sender: mdruiter AT cs DOT vu DOT nl User-Agent: tin/pre-1.4-19990413 ("Endemoniada") (UNIX) (SunOS/5.5.1 (sun4u)) X-Poster-Key: sha1:AOdE55R0kE/A86bs+6NeMXA5KXk= Cancel-Lock: sha1:6lu136Ae3CSA8yYCgbXwV/C8LeQ= To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com T.E.Dickey wrote: > `unused' > This attribute, attached to a function, means that the function is > meant to be possibly unused. GNU CC will not produce a warning > for this function. GNU C++ does not currently support this > attribute as definitions without parameters are valid in C++. Well, this is for *functions* where we were looking for a way to ignore a *parameter* of a function. I don't understand "as definitions without parameters are valid in C++", I think. Does that apply here? Thanks for digging in the docs. -- Groeten, *Michel* _http://www.cs.vu.nl/~mdruiter_ ____________ \ /====\ / "You know, Beavis, you need things that suck, \/ \/ to have things that are cool", Butt-Head.