From: James A. Markevitch (jam@magic.com)
Date: Wed Oct 11 2000 - 22:24:23 PDT
Here are my notes on the "homework" assigned to me from the last BTF
telecon. I will be travelling on Friday, 10/13, and will not be able to
attend the telecon. I am not religious about any of my determinations,
so if there is any discussion about them, feel free to change them.
James Markevitch
<p> Notes on review comments AnneH-EC-33 through AnneH-EC-52
10/11/2000
In reviewing these comments, I marked each with a code to indicate the
level of necessity. The codes are:
NO CHANGE
No change should be made.
SENSIBLE
Indicates that the change is a sensible one. However, it is not
strictly necessary, so if we are trying to minimize the number of
edits in this draft, we may choose to ignore it.
CLARIFICATION
A change which clarifies the standard and which should be implemented.
FIXTYPO
A change which is typographical or layout-like in nature. These
should be implemented.
UNSURE
I am not sure of the correct disposition.
<p><p>> AnneH-EC-33) On page 342, in item d), it would be clearer if "identifier"
> were replaced with "reference identifier".
SENSIBLE: This probably adds to the clarity.
<p><p>> AnneH-EC-34) On page 361, in bullet 8, it should be stated that the `else
> clause is only evaluated if none of the preceding `ifdef or `elsif
> conditions are defined.
NO CHANGE: Bullet 8 is consistent with the flow of the bullets in this
section; that is, the first 8 bullets map out the flow of how the whole
ifdef-elsif-else structure. If we were to choose to make a change here,
we would also want to update the description of 'elsif. Furthermore,
because the second bullet item clearly indicates that the 'elsif and 'else
are ignored, there doesn't appear to be any likelihood of confusion.
The whole set of bullet-items could probably have been done in a better
manner, but that's probably beyond the scope of what we want to change
at this point.
<p><p>> AnneH-EC-35) On page 361, bullet 9 should not be a bulleted item, since
> unlike the rest, it doesn't describe the decision flow of the `ifdef,
> `else, `endif group of directives.
FIXTYPO: This should be made, since this bullet item should not be a bullet
item.
<p><p><p><p>> AnneH-EC-36) On page 362, in bullet 4, it should be stated that the `else
> clause is only evaluated if the preceding `ifndef condition is defined and
> none of the preceding `elsif conditions are defined.
NO CHANGE: No change for the same reason as given for AnneH-EC-34.
<p><p>> AnneH-EC-37) On page 362, bullet 5 should not be a bulleted item, since
> unlike the rest, it doesn't describe the decision flow of the `ifndef,
> `else, `endif group of directives.
FIXTYPO: This should be changed for the same reason as given for AnneH-EC-35.
<p><p>> AnneH-EC-38) On page 366, in line 2, there should be a space in
> "timespecified" so that it is "time specified".
FIXTYPO: This should be fixed.
<p><p><p><p>> AnneH-EC-39) On page 462, in Table 23-23, there is an entry for "regs or
> variables" and another for "integer, time and real variables". The first
> entry should just be "regs" instead of "regs or variables".
UNSURE: I believe this change should be made, but will defer to the PLI
task force for a determination.
<p><p>> AnneH-EC-40) On page 520, retitle Figure 23-60 as "Using
> acc_handle_tchkarg1(), acc_handle_tchkarg2(), and acc_handle_notifier"
> since this figure is referenced also in section 23.47 on acc_handle_notifier.
<p>UNSURE: Given the emboldened contents of the figure, this seems to make
sense. Will defer to the PTF.
<p>> AnneH-EC-41) On page 597, in the first paragraph, change "function However"
> to include a period ("function. However").
FIXTYPO: This should be fixed.
<p><p><p><p>> AnneH-EC-42) On page 662, "The text message generated by this example is
> split off the io_printf() calls" would be clearer as "The text message
> generated by this example is split between the two io_printf() calls".
CLARIFICATION: Instead of the proposed text, change the sentence to read
"The text message generate by this example is split into two separate
io_printf() calls."
<p><p>> AnneH-EC-43) On page 675, in section 26.3.3 in the first line, "which is"
> should be "which are".
FIXTYPO: This should be fixed.
<p><p>> AnneH-EC-44) On page 676, in paragraph two of section 26.3.4, an extra
> comma is needed before the word 'and':
> >"The routines, C structures, and some examples".
SENSIBLE: Although the existing text is typographically correct, so is the
proposed change. The change, however, is more consistent with the style
in this section (see, for example, the first sentence in 26.3.4).
<p><p><p><p>> AnneH-EC-45) On page 721, at the end of the first paragraph, a possessive
> is needed: "An application can get the path to the simulation's
> save/restart location".
FIXTYPO: Basically, just insert an apostrophe into the word "simulations"
so that it becomes "simulation's".
<p><p>> AnneH-EC-46) On page 745, there is an extra comma. Change "file, opened,
> using" to "file, opened using".
FIXTYPO: This should be fixed.
<p><p><p><p>> AnneH-EC-47) On page 799, there is a missing square bracket. Change "[C.6"
> to "[C.6]".
FIXTYPO: This should be fixed.
<p><p>> AnneH-EC-48) On page 803, in item 1), change "in either initial and always
> blocks" to "in either initial or always blocks".
FIXTYPO: This should be fixed.
<p><p><p><p>> AnneH-EC-49) On page 803, in the next to last paragraph of section C.7, the
> wording is very awkward: "The reset_value argument is an integer that
> specifies whose value is returned..." ???
UNSURE: I believe that the sentence should be changed. However, someone
familiar with this section should double check. The new sentence should
read "The reset_value argument is an integer that specifies the value which
will be returned by the $reset_value system function after the tool is
reset."
<p><p>> AnneH-EC-50) On page 807, section D.1, change "The `default_decay_time
> compiler directives" to the singular "The `default_decay_time compiler
> directive".
FIXTYPO: This should be fixed.
<p><p>> AnneH-EC-51) On page 807, place a white-space character between the
> directive and the value:
> >`default_decay_time integer_constant
> >`default_decay_time 100
> >`default_decay_time infinite
FIXTYPO: All three of these should be fixed.
<p><p><p><p>> AnneH-EC-52) On page 808, place a white-space character between the
> directive and the value:
> >`default_trireg_strength integer_constant
FIXTYPO: This should be fixed.
This archive was generated by hypermail 2.1.4
: Mon Jul 08 2002 - 12:54:14 PDT
and
sponsored by Boyd Technology, Inc.