Fwd: ETF fell swoop #1

From: Karen Pieper (Karen.Pieper@synopsys.com)
Date: Thu Jan 02 2003 - 16:50:56 PST

  • Next message: Shalom.Bresticker@motorola.com: "Re: Fwd: ETF fell swoop #1"

    Precedence: bulk

    I'll second that we do a mail vote on these issues.

    If you have any objections to any of these items please speak up now. Any
    item that has not had
    an issue raised with it will pass on Friday 1/10/03 at 12:00 PST so that we
    do not have to spend meeting
    time on 1/13 discussing them. We've done a great job in the last few
    days, and there are now 72
    proposals. Not discussing 15 of them should make things go a little faster.

    Karen

    >X-Authentication-Warning: max.boyd.com: majordomo set sender to
    >owner-etf@boyd.com using -f
    >Reply-To: <Brad.Pierce@synopsys.COM>
    >From: "Brad Pierce" <Brad.Pierce@synopsys.COM>
    >To: <etf@boyd.com>
    >Subject: ETF fell swoop #1
    >Date: Thu, 26 Dec 2002 09:03:37 -0800
    >X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
    >Importance: Normal
    >Sender: owner-etf@boyd.com
    >
    >Precedence: bulk
    >
    >I propose that the following 15 ETF issues be grouped together
    >and that their proposals be voted on as a single item.
    >(If there are any proposals among these for which there is
    >not a consensus, I suggest we excise those particular issues
    >and consider only the remainder.)
    >
    > http://www.boyd.com/1364_btf/report/full_pr/56.html
    > http://www.boyd.com/1364_btf/report/full_pr/60.html
    > http://www.boyd.com/1364_btf/report/full_pr/77.html
    > http://www.boyd.com/1364_btf/report/full_pr/94.html
    > http://www.boyd.com/1364_btf/report/full_pr/97.html
    > http://www.boyd.com/1364_btf/report/full_pr/104.html
    > http://www.boyd.com/1364_btf/report/full_pr/124.html
    > http://www.boyd.com/1364_btf/report/full_pr/130.html
    > http://www.boyd.com/1364_btf/report/full_pr/131.html
    > http://www.boyd.com/1364_btf/report/full_pr/143.html
    > http://www.boyd.com/1364_btf/report/full_pr/152.html
    > http://www.boyd.com/1364_btf/report/full_pr/180.html
    > http://www.boyd.com/1364_btf/report/full_pr/195.html
    > http://www.boyd.com/1364_btf/report/full_pr/207.html
    > http://www.boyd.com/1364_btf/report/full_pr/223.html
    >
    >
    >------ ISSUE 56 ---------------------------------------
    >
    > In 12.3.11, in the first sentence, in "the signed keyword
    > must be used", the word "signed" should be bold.
    >
    > In 12.4, in the 2nd paragraph, in the penultimate sentence,
    > in "declared using the automatic keyword", the word
    > "automatic" should be bold.
    >
    >------ ISSUE 60 ---------------------------------------
    >
    > Change "1364-2000" to "1364-2001" in 17.9.3 code header.
    >
    >------ ISSUE 77 ---------------------------------------
    >
    > In Table 30 (Clause 6), in last line in last cell of table,
    >
    > REPLACE
    >
    > "Concatenation of regs;bit or part selects of regs"
    >
    > WITH
    >
    > "Concatenation of regs, bit-selects and part-selects of regs"
    >
    >
    > Also widen table cell so that no list items wrap around to
    > a second line.
    >
    >------ ISSUE 94 ---------------------------------------
    >
    > Add tri1 to the list in Syntax 19-1.
    >
    >------ ISSUE 97 ---------------------------------------
    >
    > In 12.1, in the 2nd paragraph, in the fifth sentence,
    > change "used used" to "used".
    >
    > In 12,1, in the 2nd paragraph, in the last sentence,
    > change the semicolon (;) to a comma (,).
    >
    >------ ISSUE 104 --------------------------------------
    >
    > In the 'NOTE' of section 3.2.2, change
    >
    > "types; but that the term"
    >
    > to
    >
    > "types, but that term"
    >
    >------ ISSUE 124 --------------------------------------
    >
    >Change the following:
    >
    > m Returns the current hierarchical path as a string. Does not
    > read data from the input file or str argument. If an invalid
    > conversion character follows the %, the results of the
    >operation
    > are implementation dependent.
    >
    > to
    >
    >
    > m Returns the current hierarchical path as a string. Does not
    > read data from the input file or str argument.
    >
    > If an invalid conversion character follows the %, the results of
    > the operation are implementation dependent.
    >
    >------ ISSUE 130 --------------------------------------
    >
    > Close this issue as a duplicate of part of issue 93.
    >
    >------ ISSUE 131 --------------------------------------
    >
    >
    > In the 2nd paragraph of Introduction,
    > in the first sentence, the superscript
    > on the first occurrence of the word
    > 'Verilog' should be the "Registered" symbol,
    > that is, an "R" in a circle.
    >
    >------ ISSUE 143 --------------------------------------
    >
    > All cross-references to "Section n", for
    > example, "Section 6" should be changed to
    > "Clause n", for example, "Clause 6".
    >
    > And references to subclauses should be without the
    > word "clause" at all. See, for example, third column in
    > third row in Table 117.
    >
    >------ ISSUE 152 --------------------------------------
    >
    >
    > In 12.2.1, last sentence, change "it s" to "its".
    >
    > In 12.2.2.2, first sentence, change "it's" to "its".
    >
    >------ ISSUE 180 --------------------------------------
    >
    >
    > In 14.3.2, 2nd para., items (a) and (b), before Table 48,
    > change
    >
    > "s ' x"
    > to
    > "s -> x"
    >
    > and change
    >
    > "x ' s"
    > to
    > "x -> s"
    >
    >------ ISSUE 195 --------------------------------------
    >
    > In the final example of 3.11.3, change
    >
    > module RAM16GEN (DOUT, DIN, ADR, WE, CE)
    >
    > to
    >
    > module RAM16GEN (output DOUT, input DIN, ADR, WE, CE) ;
    >
    >------ ISSUE 207 --------------------------------------
    >
    >
    > "1364-2000" appears a number of times.
    > It should be "1364-2001".
    >
    > Places:
    > 17.9.3 code header
    > Annex E header
    > Annex F header
    > Annex G header and many places in code
    > 26.6.9 footnote
    >
    >------ ISSUE 223 --------------------------------------
    >
    > 9.5: In Note, CHANGE "is same" to "is the same".
    >
    > 17.10: At end of para. 1: CHANGE "the starting" to "their
    >starting".
    >
    >--------------------------------------------------------

    This archive was generated by hypermail 2.1.4 : Thu Jan 02 2003 - 16:52:05 PST and
    sponsored by Boyd Technology, Inc.