Re: Question about record rep spec placement

[schwarza@gdls.com (Art Schwarz)]

> The way we intend a clients to read this is: You can
> assume that a Message has components Priority, Port, and
> Data, with the types shown. However, there are no guarantees
> as to the size of a Message, the placement of components
> within that message, the number of bits each component will
> use, etc. being stable from release to release. (In some
> cases, of course, you can use attributes to determine the
> current values, but it's up to the client to protect himself
> from changes in those attribute values.)

Why not supply procedures (methods) for setting and retrieving
values of interest within the record? One advantage (of procedures)
is it allows explicit front-end validity checks. Another advantage
may be to allow the type to be private.

art
schwarza@gdls.com