errata/608: mintypmax_expression usage

From: eric_mahurin@yahoo.com
Date: Thu Jul 29 2004 - 18:43:05 PDT

  • Next message: Eric Mahurin: "RE: errata/607: function returning signed integer/real/time/realtime"

    >Number: 608
    >Notify-List:
    >Category: errata
    >Originator: Eric Mahurin
    >Environment:
    >Description:

    Section 4.3 says this: "Values expressed in min:typ:max format can be used in expressions. The min:typ:max format can be used
    wherever expressions can appear."

    I think the intent is that these ONLY be used with expressions that are used for generating delays or times. I don't see where it says that.

    Secondly, the BNF is inconsistent in its use of mintypmax_expression and expression. As it is now, even an epression can have a mintypmax_expression in it with parenthesis.

    Personally, I think mintypmax_expression should unified expression and then in the text just describe when an expression or portion of it should allow the mintypmax ":" operators.

    But, if you don't do this, at least make all of the places that can have delay/time values use mintypmax_expression instead. Here are the ones I found:

    A.2.2.1: variable_type

    A.4.1: ordered_parameter_assignment (named parameters allow mintypmax, but ordered doesn't)

    A.6.5: wait statement

    A.7.5.2: timing_check_limit (found the issue here originally while parsing some example code with a $period statement and colons used direction in these timing_check_limit arguments)

    Again, I think expression and mintypmax_expression should be merged (along with constant_expression and module_path_expression) instead.

    This archive was generated by hypermail 2.1.4 : Thu Jul 29 2004 - 18:43:15 PDT and
    sponsored by Boyd Technology, Inc.