[sv-bc] RE: [sv-ec] Proposed merged LRM Table of Contents

Stu,

I looked this over a little.

I don't think Clause 3, which is the first with real content, should
already start with detailed descriptions of modules, packages, programs,
and interfaces, before the more basic subjects, starting with but not
ending with, lexical conventions and data types, for example, have been
described. The detailed descriptions of modules, etc., are not
understandable without understanding first the pieces of which they are
made. Besides, it is of enormous size. It does make sense to devote a
separate clause to each of them. (I would favor giving packages their
own separate clause as well.)

I can see putting overview descriptions of them, with only a little
detail, at the beginning, with detailed descriptions later on.

Regards,
Shalom


> -----Original Message-----
> From: owner-sv-ec@server.eda.org [mailto:owner-sv-ec@server.eda.org]
On
> Behalf Of Stuart Sutherland
> Sent: Tuesday, February 20, 2007 8:26 AM
> To: sv-bc@server.eda.org; sv-ec@server.eda.org; sv-ac@server.eda.org;
> sv-cc@server.eda.org; 'IEEE P1800 Working Group'
> Subject: [sv-ec] Proposed merged LRM Table of Contents
> 
> All,
> 
> In the P1800 working group meeting on 2/20/2007, I will go over the
> editing
> status on the merged 1800 and 1364 LRMs.  For your reference, I have
> attached is the Table of Contents of the merged LRM, as it stands
today.
> 
> During the editing process, the new Clause titles will list old 1364
and
> 1800 clause numbers that were merged into the new clause.  I will keep
> that
> information there for convenience until we are ready to generate a
> ballot
> draft.  Note that this summary of old clause numbers will not be 100%
> exact,
> or sometimes the list might span several lines.  I hope, though, that
it
> will help everyone to know where major portions of the old LRMs ended
up
> in
> the merged LRM.
> 
> Stu
> ~~~~~~~~~~~~~~~~~~~~~~~~~
> Stuart Sutherland
> Sutherland HDL, Inc.
> stuart@sutherland-hdl.com
> 503-692-0898
> 
> --
> 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.