From: Stephen W. <st...@ic...> - 2010-04-22 00:20:15
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 We may may give the warning a touch of sophistication by having it only warn for a very small set of known functions that are commonly and reasonably used like tasks ($fscanf, for example) but generate errors for anything else. Then if -g2009 is enabled, turn the errors to warnings. Is that a practical compromise? Cary R. wrote: > --- On Wed, 4/21/10, Jared Casper <jar...@gm...> wrote: > >> "Calling a nonvoid function as if it has no return value >> shall be >> legal, but shall issue a warning. The function can be used >> as a statement and >> the return value discarded without a warning by casting the >> function call to the void type. >> >> void'(some_function());" >> >> 1800-2005 has similar wording in a section 12.3.2 >> Discarding function >> return values. >> >> So maybe this should be behind -g2009? > > It sounds like it certainly belongs there. Given that it will > generate a warning it may be safe to allow in normal Verilog. > I personally think it is poor coding practice to do this, but > since SV allows it I think we need to add it. - -- Steve Williams "The woods are lovely, dark and deep. steve at icarus.com But I have promises to keep, http://www.icarus.com and lines to code before I sleep, http://www.picturel.com And lines to code before I sleep." -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFLz5XIrPt1Sc2b3ikRAjdgAKCoBBGTELgMWa1VfXZDLMtsoqu51gCgt2em iA4pdPQflDk5R7s66JgjitU= =l2WU -----END PGP SIGNATURE----- |