[Info-vax] Hex display order option for DUMP ?

[VAXman- at SendSpamHere.ORG]

In article <sdevtc$5to$1 at dont-email.me>, Simon Clubley <clubley at remove_me.eisner.decus.org-Earth.UFP> writes:
>On 2021-07-23, VAXman-  @SendSpamHere.ORG <VAXman- at SendSpamHere.ORG> wrote:
>> In article <sdet4l$k2p$2 at dont-email.me>, Simon Clubley <clubley at remove_me.eisner.decus.org-Earth.UFP> writes:
>>>
>>>Did everyone miss the part of my posting where I pointed out the
>>>current way has advantages for little endian data but also that
>>>it's a real pain for binary data ? :-)
>>>
>>>Binary data can be (for example) non-printable characters in data
>>>(which is what caused me to make this request).
>>
>> What is non-printable in:
>>
>>  BC00BC02 00730A02 00040000 000F00BB 00BB0200 6E6F6974 06050007 0000000F ........tion..>>.>>.........s..1/4.1/4 000000
>>  00BE00BE 02006562 03030005 0000000F 00BD00BD 02006F02 02000400 00000F00 .........o..1/2.1/2.........be..3/4.3/4. 000020
>>  00740902 00040000 000F00BF 00BF0200 65636E65 6373656C 0309000B 0000000F ........lescence..?.?.........t. 000040
>>  C2020066 04020004 0000000F 00C100C1 0200730A 02000400 00000F00 C000C002 .A.A.........s..A.A.........f..A 000060
>>  72696E03 06000800 00000F00 C300C302 00737568 70040500 07000000 0F00C200 .A.........phus..A.A.........nir 000080
>>  70030300 05000000 0F00C500 C5020073 05020004 0000000F 00C400C4 02006D61 am..A.A.........s..A.A.........p 0000A0
>>  69050400 06000000 0F00C700 C7020064 65050300 05000000 0F00C600 C6020074 t..AE.AE.........ed..C.C.........i 0000C0
>>  05020004 0000000F 00C900C9 02006E6F 06030005 0000000F 00C800C8 0200676E ng..E.E.........on..E.E......... 0000E0
>>  00070000 000F00CB 00CB0200 656C6261 72030600 08000000 0F00CA00 CA020073 s..E.E.........rable..E.E....... 000100
>>  04000000 0F00CD00 CD020065 04020004 0000000F 00CC00CC 02006E6F 69740505 ..tion..I.I.........e..I.I...... 000120
>>  02000400 00000F00 CF00CF02 00730502 00040000 000F00CE 00CE0200 64050200 ...d..I.I..(R).(R)....s..I.I 00012.. 000140
>>  05050007 0000000F 00D100D1 02006465 05030005 0000000F 00D000D0 02006E04 .n..TH.TH.........ed..N.N......... 000160
>>  06000800 00000F00 D300D302 00730502 00040000 000F00D2 00D20200 746E656D ment..O.O.........s..O.O........ 000180
>>  00000F00 D500D502 006E6169 03040006 0000000F 00D400D4 02006C61 6E657202 .renal..O.O.........ian..O.O.... 0001A0
>>  00D700D7 02006369 74050400 06000000 0F00D600 D6020065 6C706F06 05000700 .....ople..O.O.........tic..X.X. 0001C0
>>  D900D902 0074696F 03040006 0000000F 00D800D8 02007466 04030005 0000000F ........ft..O.O.........oit..U.U 0001E0
>>
>
>Huh ? Am I missing something ?
>
>In the above example, anything that doesn't render as a printable
>character, for example, anything less than 0x20 or the things that do
>render incorrectly in the above example as a printable character when
>they clearly are not (such as 0xc0, which renders as an uppercase A).
>
>I'm also assuming you are not showing a block mode display instead
>of a record mode display.

I don't care about the gobbledegook on the right and you were taking about the
display on the left.  How does printing the hexadecimal from left to right as
you asked for change IN ANY WAY what is in the representation on the right?

-- 
VAXman- A Bored Certified VMS Kernel Mode Hacker    VAXman(at)TMESIS(dot)ORG

I speak to machines with the voice of humanity.