errata/254: Table 30 should clarify that LHS can be array word/bit-select/part-select

From: Shalom.Bresticker@motorola.com
Date: Thu Jan 09 2003 - 12:54:54 PST

  • Next message: Shalom.Bresticker@motorola.com: "Re: errata/175: 13.2: file_path_spec syntax and related issues"

    Precedence: bulk

    >Number: 254
    >Category: errata
    >Originator: Shalom.Bresticker@motorola.com
    >Environment:
    >Description:

    This issue comes from the thread starting at

    http://www.boydtechinc.com/btf/archive/btf_2002/1809.html

    Table 30 says that LHS of assignments can be scalars, vectors, bit-selects, or
    part-selects (with some differences between continuous assignments and
    procedural assignments).

    It also says that LHS of procedural assignments can be "memory word".
    This goes back to 1364-1995, when arrays could only be 2-D, and only regs
    (not nets), and you could only access entire memory word, not bit-select or
    part-select.

    Table should clarify that LHS of continuous assignment can be array word (with
    constant select), or constant bit-select or constant part-select of array word
    with constant selects.

    Similarly, LHS of procedural assignments can be array word, or bit-select or
    part-select of array word, even with non-constant selects.

    This is relevant also to 2nd paragraph of 9.2, which again talks about a "memory
    word", a leftover from 1995 text.

    Also, the description of a "structural net expression", twice in 12.3.9.2
    also needs to be updated.

    All this is connected to issues #75 and 198 as well.

    Also, the 3rd paragraph in 4.2 also mentions a "memory word". Again, it should
    be an array word, bit-select, or part-select.

    Actually, I would like to see sections 3.10 and 4.2.2 clarify better that an
    array element is a vector/scalar (depending on its declaration) just like any
    other and can be used anywhere they can, with the same restrictions, unless
    otherwise stated.

    Finally, the entire standard should be searched to see whether there are any
    other archaic references to "memory" or "memories".

    This archive was generated by hypermail 2.1.4 : Thu Jan 09 2003 - 13:01:05 PST and
    sponsored by Boyd Technology, Inc.