Duth, Deprecating a feature normally means (at least): 1) new constructs may not have defined behavior in conjunction with the deprecated feature 2) future versions of the LRM may not define the construct (i.e. strictly speaking it would become illegal) or may not require support for compliance to the standard. In reality, tool implementors don't arbitrarily cease to support features, even when deprecated, due to backwards compatibility concerns. That being said, as a user, one might think twice about designing *new* systems using a deprecated feature as one's risk of having future problems definitely goes up. Gord. Brad Pierce wrote: > -----Non-member submission from <premduth.vidyanandan@xilinx.com>----- > > Date: Fri, 13 Jan 2006 17:30:45 -0700 > Message-ID: > <28CF4EE84FBF61419DFF495222DB13DB0244D3A6@XCO-EXCHVS1.xlnx.xilinx.com> > From: "Premduth Vidyanandan" <premduth.vidyanandan@xilinx.com> > > As long as deprecating a feature will not mean that the tool stops > supporting it that answers my concerns. > > Thanks > > Duth > > ---------------------------------------------------------------------- > > -- -------------------------------------------------------------------- Gordon Vreugdenhil 503-685-0808 Model Technology (Mentor Graphics) gordonv@model.comReceived on Mon Jan 16 07:03:23 2006
This archive was generated by hypermail 2.1.8 : Mon Jan 16 2006 - 07:03:53 PST