RE: [sv-bc] Referencing non LRM constructs such as `uselib in LRM

Shalom is correct. Configurations are a much better solution to the 
problem that was poorly addressed by the `uselib directive.

`uselib was a poor attempt to plug the hole that occurs when one 
tries to instantiate two modules with the same name from two 
different files. The problem is that you are now modifying the source 
code with hard-coded file locations to control configurations. I 
seriously discourage the use of the non-standard `uselib. The syntax 
of the `uselib is also goofy and must be turned off with an empty 
`uselib to get the -y and -v command line switches to work again.

Looking over Mantis 1850, the proposed improvement is good but I 
would more enthusiastically support removal of all discussion of the 
`uselib from the paragraph, or modify the paragraph with more 
editorial content, such as:
... This can occur in the presence of configuration library mapping 
or nonstandard functionality such as provided by the ILL-CONCEIVED 
`uselib directive. ...

Regards - Cliff

At 02:49 AM 1/22/2009, Bresticker, Shalom wrote:
>Hi,
>
>Configurations were intended to replace `uselib, so standardizing 
>`uselib would contradict a decision previously made. I have not 
>heard a significant number of calls to standardize it, either.
>
>The reference in 23.11 does call it a non-standard functionality. By 
>the way, there is a proposal in Mantis 1850 to change that paragraph.
>
>Shalom
>
>
> > `uselib is a non LRM construct, though most of the standard
> > simulators and tools support it as Verilog-XL does. Is there
> > any chance to make it standardized and integrated in SV LRM.
> >
> > Also, I saw in LRM section "23.11 Binding auxiliary code to
> > scopes or instances"  there is a reference of `uselib. If
> > there is no plan  to make `uselib standardized then a non-LRM
> > construct should not be referred in LRM.
>---------------------------------------------------------------------
>Intel Israel (74) Limited
>
>This e-mail and any attachments may contain confidential material for
>the sole use of the intended recipient(s). Any review or distribution
>by others is strictly prohibited. If you are not the intended
>recipient, please contact the sender and delete all copies.
>
>
>--
>This message has been scanned for viruses and
>dangerous content by MailScanner, and is
>believed to be clean.

----------------------------------------------------
Cliff Cummings - Sunburst Design, Inc.
14314 SW Allen Blvd., PMB 501, Beaverton, OR 97005
Phone: 503-641-8446 / FAX: 503-641-8486
cliffc@sunburst-design.com / www.sunburst-design.com
Expert Verilog, SystemVerilog, Synthesis and Verification Training


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.