Do-more designer and real data

[Henryp]

The Do-more designer doesn't seem to have the ability in a data view window to show DLV memory as a real number.

[b_carlton]

The Do-More is highly typed compared to the DL products. Ech type has its own memory area. The 'V' memory is for unsigned 16 bit words. 'Real' memory values are stored in the 'R' memory area.

[BobO]

The Do-more designer doesn't seem to have the ability in a data view window to show DLV memory as a real number.

Implied via casting. Needs to be DWORD aligned, which is also the only way it can be used as real in an instruction. To view DLV0-1 as real enter DLV0:R.

[franji1]

The PUBLISH/SUBSCRIBE instructions' primary purpose is for moving numeric data from type-less Guest Protocol memory (like DLV) into the strongly-typed Do-more Data Blocks (like D, R, N, V or user-defined strongly-typed data-blocks).

Key functionality built-in to these instructions are
1. support for BCD conversion (to/from)
2. support for mis-aligned data (e.g. reals that cross on odd-word boundaries like DLV1/DLV2 as a REAL, which is not supported using Casting mechanism of Do-more).

[BobO]

The PUBLISH/SUBSCRIBE instructions' primary purpose is for moving numeric data from type-less Guest Protocol memory (like DLV) into the strongly-typed Do-more Data Blocks (like D, R, N, V or user-defined strongly-typed data-blocks).

Key functionality built-in to these instructions are
1. support for BCD conversion (to/from)
2. support for mis-aligned data (e.g. reals that cross on odd-word boundaries like DLV1/DLV2 as a REAL, which is not supported using Casting mechanism of Do-more).

...and this too.