This LCS does not show where the attribute is used.

-- Peter Flake - 2017-03-16

@PF: Use is shown in the new examples block.

Version 2

• Attribute mode description updated for subviews.
• Examples of use added.

-- Brent Hayhoe - 2017-03-19

The list of possible kinds must be edited (16.2.1).

Why are aliases excluded from the prefix?

Why is M'converse'converse not allowed?

Why uses the example 9-bit for e.g. RdData?

Why uses BusSlaveView such a heavy construct instead of an alias? alias BusSlaveView is BusMasterView'CONVERSE.

-- Patrick Lehmann - 2017-03-20

@PL2: Likewise. For an example, see array attributes or LCS 018

@PL5: Likewise. Example seems to be inconsistent with syntax. If 'CONVERSE is a record view, then it should be stand-alone or used with an alias and not inside of a view declaration.

-- Jim Lewis - 2017-03-20

@PL1: Added modifications to include mode view entity class kind.

@PL2 &
@JL1: Added missing alias reference in attribute prefix.

@PL3: Why is it disallowed?

@PL4: Why not? This is example code. Have you not heard of parity?

@PL5: The examples are there to indicate how one can define views and not necessarily in the most efficient manner. I have added an alias based declaration example.

@JL2: 'CONVERSE returns a mode view. Mode view declarations may contain mode views of composite elements within that declaration.

Version 3

• Added modifications to section 16.2.1
• Added alias to attribute prefix section 16.2.6
• Added extra example illustrating use of alias to declare a mode view

-- Brent Hayhoe - 2017-03-20

@BH WRT 'CONVERSE the example I object to is:

view BusSlaveView of BusRecordType is
   BusMasterView'CONVERSE
end view BusSlaveView;

I think this example should be done with an alias as follows

alias BusSlaveView is  BusMasterView'CONVERSE ;

-- Jim Lewis - 2017-03-20

In 16.2.1, why did you change "named entities" to "named entity classes". The LRM uses "named entity" and "named entities" to mean any named object in numerous places. OTOH, "named entity classes" is probably not defined anywhere.

-- Jim Lewis - 2017-03-20

I'm with Jim there, I think that you can have

type HoldTheBus is record
  busstop : BusRecordType
end record HoldTheBus;

view BusSlaveView of HoldTheBus is
   busstop : view BusMasterView'CONVERSE
end view BusSlaveView;

but don't see how you can legally have

view BusSlaveView of BusRecordType is
   BusMasterView'CONVERSE
end view BusSlaveView;

-- Rob Gaddi - 2017-03-23

@RG & @JL WRT BusMasterView'CONVERSE

Point taken. I've been thinking about it this way for so long that it seemed natural.

I think alias is the correct way to make this converse declaration.

We now do not need the second example.

@JL WRT 16.2.1 "entity classes"

The BNF in the attribute defines what an entity class is. We seem to have a lot of confusion over entities and the entity class entity in the text. i thought that this may clarify the text.

OTOH, we also talk about objects a lot when we mean object class. I'm not sure how we should go with this one and am happy to leave it as entities. There is a technical grammar here to be followed. I'm not the one to specify that.

Version 4

• Removed "entity classes" reference.
• Changed 'CONVERSE mode view declaration to be alias based.
• Removed second example.

-- Brent Hayhoe - 2017-03-21

Do we really need such a big example in the LRM? I suggest a smaller FIFO/Streaming bus example (Data, Valid, Ack).

The Result row in the attribute description should mention that the modes are in the same order. I somehow dislike the <...> notation.

The wording element mode does not apply to slices.

-- Patrick Lehmann - 2017-03-25

Version 5