Hi Tristan, in reference to this thread: https://mail.gna.org/public/ghdl-discuss/2006-01/msg00001.html Why not turning this error into a simple warning ? When I reuse code by others not written with GHDL I often have this error. I know you want GHDL to follow the Standard but a warning is sufficient to say that the code is not standard compliant.
on 2009-02-24 16:52
on 2009-02-25 00:11
On Tuesday 24 February 2009 08:50:57 Sylvere Teissier wrote: > in reference to this thread: > https://mail.gna.org/public/ghdl-discuss/2006-01/msg00001.html > > Why not turning this error into a simple warning ? > > When I reuse code by others not written with GHDL I often have this > error. > > I know you want GHDL to follow the Standard but a warning is sufficient > to say that the code is not standard compliant. One note: the new VHDL 2008 standard has relaxed certain rules like these. But I haven't used it enough to know if it covers this case or not.
on 2009-02-26 09:46
Quoting Sylvere Teissier <st@invia.fr>: > Hi Tristan, > > in reference to this thread: > https://mail.gna.org/public/ghdl-discuss/2006-01/msg00001.html > > Why not turning this error into a simple warning ? I will see what I can do. I think it would be simpler if this error doesn't occur with --std=93c. > When I reuse code by others not written with GHDL I often have this > error. Sure, I understand this point. Tristan.
Enable email notification
Enable multi-page view