RE: [sv-bc] Defparam -- mixed message from IEEE standards

People don't seem understand the difference between deprecation and
removal. 

You can't remove a feature from an existing standard. 

You can remove a feature from a new revision of a standard, but then you
can't claim backwards compatibility with the previous version. Even if
you don't have backwards compatibility in the LRM, implementers can't
ignore the fact that the feature was in existence.

Deprecation is the terminology used to make a feature 'fade away' and
gives implementers the option to remove support for it as warranted by
user demand.

Dave


> -----Original Message-----
> From: Paul Graham [mailto:pgraham@cadence.com]
> Sent: Thursday, June 15, 2006 9:16 AM
> To: mcnamara@cadence.com
> Cc: Rich, Dave; sv-bc@verilog.org
> Subject: Re: [sv-bc] Defparam -- mixed message from IEEE standards
> 
> > And, last time I checked, ANSI C, FORTRAN, et cetera, still has the
goto
> > statement, despite Edsger's best efforts, now 38 years in progress
[Ref:
> 
> Even Ada has the goto statement!  Some language features are
> just so useful that no amount of complaining will make them
> go away.
> 
> Paul