RE: [sv-ec]E-mail Vote (part 1) 1371

I have uploaded a new proposal based on Neil's wording suggestions and
have changed initial block to initial construct. Block was in the
original text. If someone wants to use procedure, they can submit
another mantis issue for a global clean-up.

I moved the sentence about terminating the simulation when all initial
blocks end up to section 16.2 because that functionality is independent
of $exit. $exit is just one mechanism to end a set of initial blocks in
a program.

Dave


> -----Original Message-----
> From: owner-sv-ec@server.eda.org [mailto:owner-sv-ec@server.eda.org]
On
> Behalf Of Bresticker, Shalom
> Sent: Wednesday, April 25, 2007 12:49 AM
> To: Brad Pierce; sv-ec@server.eda.org
> Subject: RE: [sv-ec]E-mail Vote (part 1) 1371
> 
> Well, if you are going to quote 1364, let's go all the way:
> 
> 9.9.1 and 9.9.2 are called "Initial construct" and "Always construct".
> respectively.
> 
> 1364 uses "construct" for 'initial' and 'always' much more than other
> terms, and also in the BNF.
> 
> Stu has proposed using 'procedure' instead, but the committees have
not
> voted on that. Even if so, Stu still has a lot of work as even his
Draft
> 2 still uses other terms in many places.
> 
> We could also explicitly say that 'always' and 'initial' are called
> 'procedures' and 'constructs' interchangeably.
> 
> I do think it is best to avoid 'block' as that term is used for
> Sequential and Parallel blocks (begin...end, fork...join), including
the
> familiar term 'named block'. On the other hand, 'always block' and
> 'initial block' are terms frequently used by users and by most of us,
> even if for no other reason than that 'block' is only one syllable.
> 
> Shalom
> 
> 
> > -----Original Message-----
> > From: owner-sv-ec@server.eda.org [mailto:owner-sv-ec@server.eda.org]
> > On Behalf Of Brad Pierce
> > Sent: Sunday, April 22, 2007 8:46 AM
> > To: sv-ec@server.eda.org
> > Subject: Re: [sv-ec]E-mail Vote (part 1) 1371
> >
> > In the 1364 standard, 'always' and 'initial' are described in
> > Subclause
> > 9.9, called
> >
> >       "Structured procedures"
> >
> > Subclause 6.2 says
> >
> >      "Procedural assignments occur within procedures such as always,
> > initial [...],
> >       task, and function [...]"
> >
> > Stu's consistent use of the phrases "always procedure" and "initial
> > procedure"
> > is accurate and sensible.
> >
> > -- Brad
> 
> --
> 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.