Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!uakari.primate.wisc.edu!sdd.hp.com!news.cs.indiana.edu!arizona.edu!arizona!dave
From: dave@cs.arizona.edu (Dave P. Schaumann)
Newsgroups: comp.sys.amiga.hardware
Subject: Re: Standard for long hex numbers? (Was: Re: Amig
Message-ID: <873@caslon.cs.arizona.edu>
Date: 15 Feb 91 03:55:26 GMT
References: <2207@ria.ccs.uwo.ca> <18881@cbmvax.commodore.com> <887@cbmger.UUCP> <855@caslon.cs.arizona.edu> <18986@cbmvax.commodore.com>
Organization: U of Arizona CS Dept, Tucson
Lines: 19

In article <18986@cbmvax.commodore.com> daveh@cbmvax.commodore.com (Dave Haynie) writes:
|In article <855@caslon.cs.arizona.edu> dave@cs.arizona.edu (Dave P. Schaumann) writes:
|
||Prior art: virtually every hex memory dump I've ever looked at looked like:
||f000: 00 00 00 00 00 00
|
|Sounds like you're dealing with an 8 bit machine there.  On our 68030 emulator
|here lists with spaces depending on what you're listing.  If you asked for
|bytes, you'd get "07f00000: 00 01 02 03 04 05 06 07 ...", but for longwords
|it would be "07f00000: 00010203 04050607..."

Would it help if I said it was a C64/C128?  Really.


|Dave Haynie Commodore-Amiga (Amiga 3000) "The Crew That Never Rests"
-- 
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.