From 1737942278589784555
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: f78e5,c491eb430f6ab75a
X-Google-Attributes: gidf78e5,public
From: Alexandre Oliva <oliva@dcc.unicamp.br>
Subject: Re: How about #depricate
Date: 1997/02/22
Message-ID: <orbu9e0wd0.fsf@dcc.unicamp.br>#1/1
X-Deja-AN: 220709952
References: <330B4E75.16FE@strata3d.com> <330CD371.2225@mds.rmit.edu.au>
X-Original-Date: 21 Feb 1997 16:53:15 -0300
Organization: IC - UNICAMP - Campinas, SP, Brazil
X-Auth: PGPMoose V1.1 PGP comp.std.c++
Mime-Version: 1.0 (generated by tm-edit 7.105)
Newsgroups: comp.std.c++
Originator: austern@isolde.mti.sgi.com


> 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.

Marcelo Cantos writes:

>   #define identifier !@$%

> Your compiler will then flag all the occurring instances as errors.
> An easier approach is to use grep.

I guess the intent of the poster is similar to the @deprecate comment
in Java.  the compiler should issue just a warning message, so that
code will still compile, but the user will be warned that this feature
may not be available in future releases of the compiler/language.

It should actually be a declaration or a pragma, visible by the
compiler, not only by the preprocessor, so that scope and overloading
can be addressed.

-- 
Alexandre Oliva
mailto:oliva@dcc.unicamp.br mailto:aoliva@acm.org
Universidade Estadual de Campinas, SP, Brasil
---
[ 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 
]



