RE: [sv-bc] Mantis 1809

Stu,

The proposal we just passed today has all these corrections already
included - we revised it on the fly. But I'll add the note about the
fixed font, since it will be easy to miss when you cut and paste.

Dave



> -----Original Message-----
> From: Stuart Sutherland [mailto:stuart@sutherland-hdl.com]
> Sent: Monday, July 21, 2008 8:10 PM
> To: Vreugdenhil, Gordon; Rich, Dave
> Cc: sv-bc@eda.org
> Subject: RE: [sv-bc] Mantis 1809
> 
> I consider all of these to be editorial issues, which could be added
as a
> bug note for the editor (me) to take care when the proposal is added
to
> the
> LRM.
> 
> Stu
> ~~~~~~~~~~~~~~~~~~~~~~~~~
> Stuart Sutherland
> stuart@sutherland-hdl.com
> +1-503-692-0898
> www.sutherland-hdl.com
> 
> 
> 
> > -----Original Message-----
> > From: owner-sv-bc@eda.org [mailto:owner-sv-bc@eda.org] On Behalf Of
> > Gordon Vreugdenhil
> > Sent: Monday, July 21, 2008 7:41 AM
> > To: Dave Rich
> > Cc: sv-bc@eda.org
> > Subject: Re: [sv-bc] Mantis 1809
> >
> > Dave, thanks so much for making so much progress on this.
> >
> > Shalom caught a couple of things and I have a few additional things
> > that I think
> > we need to do.
> >
> >
> > 1)
> >
> > One of Stu's concerns was the use of "we" and similar.  The
following
> > paragraph still uses "we":
> >
> >    For the purpose of describing how identifiers resolve to wildcard
> > imported
> >    declarations we define what are a locally visible and potentially
> > locally
> >    visible identifiers.
> >
> > Since the paragraph is purely expository introduction and is
followed
> > by the definitions, I think we can just strike that paragraph.
> >
> >
> > 2)
> >
> > In the text following example 2:
> >      The declaration x from package p becomes
> > "x" and "p" should be in fixed font.
> >
> >
> > 3)
> >
> > In example 4, keywords aren't in bold.
> >
> > 4)
> >
> > Just after example 4:
> >      but only the wildcard import p::* that
> > the "p::*" should be in fixed font.
> >
> >
> > 5)
> >
> > In a couple of the examples, line breaks occur in the pdf in the
> > middle of a comment of SV code.  We should make sure that the
> > comments remain intact.  The examples following the
> > text "Other than for task and function names (see 22.7.1)" have
> > this problem as does the first example in 22.7.1
> >
> >
> >
> > Gord.
> >
> >
> >
> > Brad Pierce wrote:
> > > Proposal is attached for easier review.
> > >
> > >
> > >
> > > n  Brad
> > >
> > >
> > >
> > > *From:* owner-sv-bc@eda.org [mailto:owner-sv-bc@eda.org] *On
Behalf
> > Of
> > > *Rich, Dave
> > > *Sent:* Monday, July 21, 2008 4:56 PM
> > > *To:* sv-bc@eda.org
> > > *Subject:* [sv-bc] Mantis 1809
> > >
> > >
> > >
> > > New proposal uploaded and should be reviewed. It's very late.
> > >
> > >
> > >
> > > David Rich
> > > Verification Technologist
> > > Design Verification & Test Division
> > > Mentor Graphics Corporation
> > > dave_rich@mentor.com
> > > Office:   408 487-7206
> > > Cell:     510 589-2625
> > >
> > >
> > >
> > >
> > > --
> > > This message has been scanned for viruses and
> > > dangerous content by *MailScanner* <http://www.mailscanner.info/>,
> > and is
> > > believed to be clean.
> > >
> > >
> > > --
> > > This message has been scanned for viruses and
> > > dangerous content by *MailScanner* <http://www.mailscanner.info/>,
> > and is
> > > believed to be clean.
> >
> > --
> > --------------------------------------------------------------------
> > Gordon Vreugdenhil                                503-685-0808
> > Model Technology (Mentor Graphics)                gordonv@model.com
> >
> >
> > --
> > This message has been scanned for viruses and
> > dangerous content by MailScanner, and is
> > believed to be clean.
> 


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.