1364-2001 bnf changes

From: Shalom Bresticker (Shalom.Bresticker@motorola.com)
Date: Wed Nov 13 2002 - 07:22:21 PST

  • Next message: Shalom Bresticker: "Re: errata/189: 12.1, macromodule needs clarification"

    Precedence: bulk

    I have two concerns about the many bnf change proposals we have:

    1. When developers look at the bnf changes, in many changes they will
    probably not understand the type of change or its implications. For
    example, whether the change is functionally equivalent to the old bnf or
    not.

    The meaning of changes in the text of the standard are clearer, so the
    problem is not so great.

    2. I worry about coordination of bnf changes with the SystemVerilog
    committee. As you have seen, they do not want to wait for us and are
    doing changes without us, at least from Dan Jacobi's review. That is not
    so bad, because we also have that review and we can track what they are
    doing.

    The reverse, however, is not true. We have many change proposals that
    they do not know of and are not tracking.
    As a result, we will make changes which will not be reflected there.

    We could say, "Well, that is their problem, not ours," but do we want
    to? 

    --
Shalom Bresticker                           Shalom.Bresticker@motorola.com
Design & Reuse Methodology                             Tel: +972 9 9522268
Motorola Semiconductor Israel, Ltd.                    Fax: +972 9 9522890
POB 2208, Herzlia 46120, ISRAEL                       Cell: +972 50 441478

    "The devil is in the details."

    This archive was generated by hypermail 2.1.4 : Wed Nov 13 2002 - 07:24:42 PST and
    sponsored by Boyd Technology, Inc.