[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
|
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
868.0. "RECORD Data construct" by STAR::DUTKO (Nestor, VMS Engineering) Wed Apr 03 1991 13:48
If I define an attribute of type RECORD with three fields, I understand that
the fields are used as keywords when specifying their values.
Must I specify every keyword/value pair even if I don't need to?
Consider a VMS ACE. It is comprised of three fields, the Identifier, the Options
and Access. I don't need to specify Options on every ACE, just when I want to.
As a note, I'm currently envisioning the VMSace to be defined as:
TYPE VMSIdentifierAce = 1 RECORD
Identifier = 1 : Latin1String ;
Options = 2 : Latin1String ;
Access = 3 : Latin1String ;
END ;
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 868.1 | for now YES | TOOK::CALLANDER | | Wed Apr 03 1991 18:07 | 4 |
| For now you must specify EVERY keyword=value pair when entering a
record from both the FCL and the Iconic Map PMs. Maybe in the
future this will change, but for now we don't have a consistent
mechanism for encoding "it wasn't supplied" inside a record.
|