re: generate proposal

From: Jason Woolf (jasonw@cadence.com)
Date: Mon Feb 02 2004 - 11:49:08 PST

  • Next message: Steven Sharp: "re: generate proposal"

    > That is not a description that a code writer can use to determine whether
    > it is ok to use a defparam or not.

    The point of that section is to allow the reader to determine the legality of a
    defparam with a particular hierarchical parameter name. It explains the reason
    for the restriction and defines it precisely. Are you saying that it is too
    complicated, or that a code developer shouldn't have to understand elaboration
    in order to write a model? I would have to disagree with you if that is the
    case. True, it wasn't necessary before, but it's a different world with
    generates.

    > Further, it means that its legality is not determined until elaboration time.

    The legality of any hierarchical name is not determined until elaboration time.
    The rules for defparams that contain hierarchical names can only be enforced
    at elaboration time.

    This goes back to your position that defparams are a bad idea. I completely
    agree. But we're stuck with them, so we're stuck explaining the complicated
    restrictions needed to prevent irrational design descriptions.

    Do you have any suggestions on how to improve this aspect of the proposal?

    -Jason

    This archive was generated by hypermail 2.1.4 : Mon Feb 02 2004 - 11:35:51 PST and
    sponsored by Boyd Technology, Inc.