The way the BNF is organized in SV, Annex A contains only a general "function_subroutine_call", without detailing all the different kinds of functions, and then you have
function_subroutine_call ::= subroutine_call
subroutine_call ::=
tf_call // user-defined functions
| system_tf_call // built-in functions
...
and
system_tf_call ::=
system_tf_identifier [ ( list_of_arguments ) ]
| system_tf_identifier ( data_type [ , expression ] )
The actual detailed descriptions of different types of functions and their syntaxes is in other parts of the LRM, but not in Annex A.
So for example, Syntax 21-8 is
"file_positioning_functions ::=
$ftell ( fd )
| $fseek ( fd , offset , operation )
| $frewind ( fd )
Syntax 21-8-Syntax for file positioning system functions (not in Annex A)"
Regards,
Shalom
> -----Original Message-----
> From: owner-verilog-ams@eda.org [mailto:owner-verilog-ams@eda.org] On
> Behalf Of Geoffrey.Coram
> Sent: Wednesday, October 06, 2010 3:52 PM
> To: David Miller
> Cc: Verilog-AMS LRM Committee
> Subject: Re: Regarding ddx operator location in grammar
>
> > and make analog_partial_derivative_function_call part of
> analog_primary.
>
> Doesn't it need to be part of "primary" rather than "analog_primary"?
> Otherwise it's still subject to the same restrictions as
> analog_filter_function_call (which is part of analog_primary).
>
> -Geoffrey
---------------------------------------------------------------------
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.Received on Wed Oct 6 07:04:25 2010
This archive was generated by hypermail 2.1.8 : Wed Oct 06 2010 - 07:04:26 PDT