From 569292216575085728 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f78e5,c491eb430f6ab75a X-Google-Attributes: gidf78e5,public From: Marcelo Cantos Subject: Re: How about #depricate Date: 1997/02/21 Message-ID: <330CD371.2225@mds.rmit.edu.au>#1/1 X-Deja-AN: 220498080 References: <330B4E75.16FE@strata3d.com> X-Original-Date: Fri, 21 Feb 1997 09:42:57 +1100 Organization: MDS Group, RMIT X-Auth: PGPMoose V1.1 PGP comp.std.c++ Newsgroups: comp.std.c++ Originator: austern@isolde.mti.sgi.com X-Mailer: Mozilla 3.01Gold (X11; I; SunOS 5.5.1 sun4u) Bret Pehrson wrote: > > Since C++ is (and always will be) a growing language, and since that > growth causes the deprication of various elements, how about some help > from the language in the form of a deprication notification, something > of the form of: > > #depricate identifier > > which would issue a compiler diagnostic along the lines of: > > warning: 'identifier' is marked as depricated. Deprecate, not depricate. I assume the purpose of #deprecate is to get the compiler to tell the programmer where all the instances of this keyword are located. This could easily be addressed by going: #define identifier !@$% Your compiler will then flag all the occurring instances as errors. An easier approach is to use grep. In reality I don't think many identifiers are deprecated and the compiler vendors usually issue warnings of this nature anyway. -- ___________________________________________________________________ Marcelo Cantos, Research Assistant marcelo@mds.rmit.edu.au Multimedia Database Systems Group __/_ _ Tel 61-3-9282-2497 723 Swanston St, Carlton VIC 3053, Aus/ralia ><_>Fax 61-3-9282-2490 / --- [ comp.std.c++ is moderated. To submit articles: Try just posting with your newsreader. If that fails, use mailto:std-c++@ncar.ucar.edu comp.std.c++ FAQ: http://reality.sgi.com/austern/std-c++/faq.html Moderation policy: http://reality.sgi.com/austern/std-c++/policy.html Comments? mailto:std-c++-request@ncar.ucar.edu ]