Hi Arpad, I think i understand the problem a bit more. I also checked the input_declaration BNF syntax and the syntax for this is specified in one of the sections (7.4.2.2) but not in the BNF/Annex A input_declaration := input [range] list_of_port_identifiers; Also the BNF for list_of_port_identifiers is not specified in BNF syntax. This needs to be fixed as part of the next revision. I will raise a mantis item for this if its not already there. Anyway i would expect this to be resolved as part of moving to 1364-2005. cheers, Sri Sri Chandra wrote: > Hi Arpad, > > Not sure why you think LRM doesnt support arrays. According to BNF > (LRM 2.2): > > function_item_declaration ::= > input_declaration > | inout_declaration > | output_declaration > | block_item_declaration > > block_item_declaration ::= > parameter_declaration > | integer_declaration > | real_declaration > > And if you look at integer_declaration and real_declaration > > integer_declaration ::= integer list_of_identifiers ; > > real_declaration ::= real list_of_identifiers ; > > list_of_identifiers ::= var_name { , var_name } > var_name ::= variable_identifier > | array_identifier array_range > > (The above is also detailed in section 3.1) > > cheers, > Sri > > Muranyi, Arpad wrote: > >> I am just noticing (with disbelief) that analog functions >> cannot take arrays as inputs (since I don't see any mention >> of it in LRM v2.2). Is this observation/conclusion correct? >> >> analog function real maxValue; >> input n1, n2 ; >> real n1, n2 ; >> begin >> // code to compare potential of two signal >> maxValue = (n1 > n2) ? n1 : n2 ; >> end >> endfunction >> >> Is there a way to make "n1" and/or "n2" an array? >> >> Thanks, >> >> Arpad >> =========================================================== >> >> >> > -- Srikanth Chandrasekaran Design Technology (Adelaide) Freescale Semiconductor Ph: +61-(0)8-8168 3592 Fax: x3201Received on Thu Sep 15 16:47:45 2005
This archive was generated by hypermail 2.1.8 : Thu Sep 15 2005 - 16:48:02 PDT