RE: [vhdl-200x] Implicit conversion, Overloading, & Strong Typing
Subject: RE: [vhdl-200x] Implicit conversion, Overloading, & Strong Typing
From: Scott Thibault (thibault@gmvhdl.com)
Date: Fri Dec 19 2003 - 08:49:04 PST
- Next message: Andy D Jones: "Re: [vhdl-200x] Corrections to Minutes for VHDL-200X-FT meeting, San Jose Dec 4, 2003"
- Previous message: Bailey, Stephen: "RE: [vhdl-200x] Corrections to Minutes for VHDL-200X-FT meeting,S an Jose Dec 4, 2003"
- In reply to: Gabe Moretti: "Re: [vhdl-200x] Implicit conversion, Overloading, & Strong Typing"
- Next in thread: Jay Lawrence: "RE: [vhdl-200x] Implicit conversion, Overloading, & Strong Typing"
- Reply: Scott Thibault: "RE: [vhdl-200x] Implicit conversion, Overloading, & Strong Typing"
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
> What Scott suggests is not a robust solution. In fact what would
> (if (we_n) then
I didn't suggest that. I was commenting on the current proposal, i.e.:
if (we) then
or
if (not we_n) then
My point is that the benefit of the above is not less typing, but avoiding
the countless compiler errors that result using the current standard when
the designer accidentally enters code like the above, which in my experience
occurs frequently.
--Scott
- Next message: Andy D Jones: "Re: [vhdl-200x] Corrections to Minutes for VHDL-200X-FT meeting, San Jose Dec 4, 2003"
- Previous message: Bailey, Stephen: "RE: [vhdl-200x] Corrections to Minutes for VHDL-200X-FT meeting,S an Jose Dec 4, 2003"
- In reply to: Gabe Moretti: "Re: [vhdl-200x] Implicit conversion, Overloading, & Strong Typing"
- Next in thread: Jay Lawrence: "RE: [vhdl-200x] Implicit conversion, Overloading, & Strong Typing"
- Reply: Scott Thibault: "RE: [vhdl-200x] Implicit conversion, Overloading, & Strong Typing"
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
This archive was generated by hypermail 2b28
: Fri Dec 19 2003 - 08:51:14 PST