Hi Marq, I have filed Mantis 2836 for this one. I will file mantis for the other one. Regards Surya -------- Original Message -------- Subject: Re:No BNF support for .module_output_variable_identifier From: Marq Kole <marq.kole@nxp.com> To: Surya Pratik Saha <spsaha@cal.interrasystems.com>, verilog-ams@server.eda.org <verilog-ams@eda.org> Date: Monday, August 03, 2009 2:33:39 PM > Hi Surya, > > This looks like an oversight: an alternative should be added to the third rule in BNF A.9.1 to handle the procedural assignment of a paramset_output_variable_expression. This paramset_output_variable_expression would have to be defined such that it may use the ".module_output_variable_identifier" as primitive. > > This issue as well as the one you mentioned on the access function should be made into a Mantis item. If you want I can do that... > > Cheers, > Marq > > > -----Original Message----- > From: owner-verilog-ams@server.eda.org [mailto:owner-verilog-ams@server.eda.org] On Behalf Of Surya Pratik Saha > Sent: Monday 3 August 2009 9:56 > To: verilog-ams@server.eda.org > Subject: No BNF support for .module_output_variable_identifier > > Hi, > In Verilog AMS 2.3.1, section 6.4.3 Paramset output variables, there is > an example of ".module_output_variable_identifier". But I could not see > this in the BNF of paramset. Is it intentional or a oversight of LRM? > > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Mon Aug 3 12:27:23 2009
This archive was generated by hypermail 2.1.8 : Mon Aug 03 2009 - 12:27:39 PDT