Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!ncar!noao!arizona!dave
From: dave@cs.arizona.edu (Dave P. Schaumann)
Newsgroups: comp.sys.amiga.hardware
Subject: Re: Standard for long hex numbers? (Was: Re: Amiga and its memory map)
Message-ID: <855@caslon.cs.arizona.edu>
Date: 14 Feb 91 04:25:19 GMT
References: <2207@ria.ccs.uwo.ca> <18881@cbmvax.commodore.com> <887@cbmger.UUCP>
Organization: U of Arizona CS Dept, Tucson
Lines: 28

In article <887@cbmger.UUCP> peterk@cbmger.UUCP (Peter Kittel GERMANY) writes:
>In article <18881@cbmvax.commodore.com> daveh@cbmvax.commodore.com (Dave Haynie) writes:
>>
>>Cheap-ass A3000 memory map:
>>
>>$ff010000-$ffffffff	Reserved
>
>I always have big difficulties reading such big hex numbers. Couldn't
>there be developed a standard to insert delimiters as in long decimal
>numbers (there all 3 digits) all 4 digits?
>
>How about $ff01'0000 (or comma or hyphen instead of "'")?

Why not just use a space?  $ff01 0000

Prior art: virtually every hex memory dump I've ever looked at looked like:
f000: 00 00 00 00 00 00

I suppose using a space might be ambiguous in some cirucumstances.  I don't
like the quote or hyphen, but the comma could work (as it works in decimal
numbers).

I do agree that *some* seperator needs to be used.  My eyes get lost after
more than 5 digit in a row, especially in hexidecimal numbers.
-- 
Dave Schaumann      | DANGER: Access holes may tear easily.  Use of the access
		    | holes for lifting or carrying may result in damage to the
dave@cs.arizona.edu | carton and subsequent injury to the user.