Typographical Issues in IEEE Std 1076-2008

This is a collection of typographical issues in the LRM that are not captured by their own pages.

Section 6.5.2 Interface object declarations

The sentence

If no mode is explicitly given in an interface declaration other than an interface file declaration, mode in is assumed.

should read

If no mode is explicitly given in an interface object declaration other than an interface file declaration, mode in is assumed.

Rationale: This section, while subordinate to 6.5 Interface declarations, includes text specific to interface object declarations. If the intent of the sentence were to apply to all interface declarations, it would be in the wrong place. Moreover, modes only apply to interface object declarations, not to interface declarations in general.

ErnstChristen -- 2016-05-04

Section 6.5.7.3 Port map aspects

The text

The purpose of a port aspect is as follows:

should read

The purpose of a port map aspect is as follows:

Rationale: There is no concept called "port aspect" in 1076-2008, and the section is about port map aspects.

ErnstChristen -- 2016-05-04

Section 24.1.1 General

This is the clause about standard tool directives.

In the example at the end of this section, the original protect directive and the equivalent sequence of protect directives should use the same font size.

ErnstChristen -- 2016-05-11

Comments