Re: No BNF support for .module_output_variable_identifier

Hi Sri,
I have permission to file Mantis in http://www.eda.org/svdb. If you 
refer to file ticket there, I can also do that. Please let me know.

Regards
Surya



-------- Original Message  --------
Subject: Re:No BNF support for .module_output_variable_identifier
From: Sri Chandra <sri.chandra@freescale.com>
To: Surya Pratik Saha <spsaha@cal.interrasystems.com>
Cc: verilog-ams@eda.org
Date: Monday, August 03, 2009 2:10:19 PM
> Dear Surya,
>
> At first glance it looks like an oversight. The 
> analog_function_statement (which is included in the paramset statement 
> syntax) should allow syntax of the following nature (as described in 
> the example of 6.4.3)
>
> ft = .gm/(‘M_TWO_PI*(.cpi + .cmu));
>
> where gm, cpi and cmu are references to the module level variables.
>
> the grammar for analog_procedural_assignment currently doesn't specify 
> the above syntax from my quick look of Annex A. Hopefully i haven't 
> missed something here. We need to be careful adding it to the 
> analog_primary since these kind of reference to module level variables 
> are done only within the paramset and no where else.
>
> I will raise a ticket for this and this can be discussed in one of the 
> meetings.
>
> Regards,
> Sri
>
>
>
> Surya Pratik Saha wrote:
>> 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.