| 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 |
Hi,
Yet another MSL question : how do you model an attribute whose ASN.1
datatype is defined as CHOICE ?
The only solution I've found is to use RECORD , with variants, but this
assumes that the datatype is structured with a fixed field. What if I have
a simple attribute which may take different datatypes? (That is, assuming
my intepretation of the ASN.1 CHOICE datatype is correct...)
Thanks, regards,
Philippe.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2441.1 | You have no CHOICE | BLUMON::SYLOR | Architect = Buzzword Generator | Tue Mar 10 1992 00:35 | 6 |
In a word, you can't. I figure I'll add all the ASN.1 type constructors to the Entity Model someday. But when I don't know. Mark | |||||
| 2441.2 | TOOK::STRUTT | Management - the one word oxymoron | Tue Mar 10 1992 19:37 | 9 | |
Philippe,
I'd be interested in hearing more about this "attribute" that is
defined as a CHOICE. What exactly *is* this attribute? Why is it
potentially more than one actual datatype?
It is possible that there is a solution to your problem (in addition
to, or an alternative to) VARIANT RECORD
Colin
| |||||