Re: Probably too late for this, but...

[Michael Kirkham <mikek@muonics.com>]

On Fri, 11 May 2001, Michael Kirkham wrote:

>        typedef RowStatus {
>            type        Enumeration (active(1), notInService(2),
>                            notReady(3), createAndGo(4),
>                            createAndWait(5), destroy(6));
>            read-type   Enumeration (active(1), notInService(2),
>                            notReady(3));
>            write-type  Enumeration (active(1), notInService(2),
>                            createAndGo(4),
>                            createAndWait(5), destroy(6));
>            
>            ...
>        }

Actually it might be slightly less redundant to do...

        typedef RowStatus {
            type        Enumeration (active(1), notInService(2));
            read-type   Enumeration (notReady(3));
            write-type  Enumeration (createAndGo(4),
                            createAndWait(5), destroy(6));

            ...
        }

...and say 'type' == values that can be read and written, 'read-type' ==
values that can only be read, 'write-type == values that can only be
written.  That would still be compatible with the current 'type'
semantics, I believe.