T.R | Title | User | Personal Name | Date | Lines |
---|
1409.1 | | TOOK::SWIST | Jim Swist LKG2-2/T2 DTN 226-7102 | Wed Aug 28 1991 09:37 | 2 |
| Not to my knowledge.
|
1409.2 | not now, but yes | TOOK::KOHLS | Ruth Kohls | Wed Sep 04 1991 12:11 | 7 |
| > Is the mcc_b_dtype field of the MCC_T_Descriptor used?
Not currently, but I am planning to use it to distinguish between the
different hardware forms of real numbers for ILV and ASN.1 purposes, and
once that is done there will be other, similar, uses developed for it.
Ruth K.
|
1409.3 | the next best thing... | TENERE::SILVA | Carl Silva - Telecom Eng - DTN 828-5339 | Fri Sep 06 1991 06:00 | 12 |
| RE: .2,
>> Is the mcc_b_dtype field of the MCC_T_Descriptor used?
>
>Not currently, but I am planning to use it to distinguish between the
>different hardware forms of real numbers for ILV and ASN.1 purposes, and
>once that is done there will be other, similar, uses developed for it.
SO then the nbest thing to do is to use it now for future
compatibility?
Carl
|
1409.4 | | TOOK::SWIST | Jim Swist LKG2-2/T2 DTN 226-7102 | Fri Sep 06 1991 09:24 | 9 |
| That is unclear. The real function of this field is to represent
the operating system's view of the datatype (a superset of the
hardware's view of the datatype). On VMS, this matters
if and only if you pass the descriptor to an RTL routine like
lib$cvt_dxdx which needs to know the VMS datatype. On Ultrix, there's
no concept of descriptor-based data and hence the MCC descriptor means
nothing to the OS, but there are cases as Ruth mentioned where MCC
internally needs to know the hardware datatype, so it seems like
a consistent use of the field.
|
1409.5 | I do | TOOK::KOHLS | Ruth Kohls | Mon Sep 09 1991 11:31 | 11 |
| > SO then the nbest thing to do is to use it now for future
>compatibility?
It can't hurt. You can set it to DSC_K_DTYPE_Z (any) or
DSC_K_DTYPE_T (string, to match the declaration of a descriptor's pointer) on
mcc descriptor initialization, and alter it to fit specific cases
when necessary. Some of the necessary cases were pointed out by Jim--
VMS library routine calls. Another example is floating point arithmetic on VMS.
Ruth
|