Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!elroy.jpl.nasa.gov!ames!vsi1!zorch!xanthian From: xanthian@zorch.SF-Bay.ORG (Kent Paul Dolan) Newsgroups: comp.sys.amiga.hardware Subject: Re: Standard for long hex numbers? (Was: Re: Amiga and its memory map) Message-ID: <1991Feb14.063939.28350@zorch.SF-Bay.ORG> Date: 14 Feb 91 06:39:39 GMT References: <2207@ria.ccs.uwo.ca> <18881@cbmvax.commodore.com> <887@cbmger.UUCP> Organization: SF-Bay Public-Access Unix Lines: 61 daveh@cbmvax.commodore.com (Dave Haynie) writes: >Cheap-ass A3000 memory map: > >$ff010000-$ffffffff Reserved peterk@cbmger.UUCP (Peter Kittel GERMANY) writes: > 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 "'")? > We only would have to avoid the colon so that it couldn't be mixed up > with Intel-like segment addressing. > (And I myself would like to avoid comma and dot, because their use in > decimal numbers is already reverse in USA and Germany. That produces > big trouble enough, and I wouldn't like to cause such crap again with > hex numbers.) > Or is there already existing such a standard, only I don't know it and > nobody uses it? Yes, there does exist a very nice international standard for this purpose, and I suggest we adopt it posthaste! The ANSI/ISO standard for the Ada programming language defines numeric literals (in any base) to include underscore characters at arbitrary locations, which are only for human readability in source code, and are ignored by the compiler. Used every four hex characters, this makes Dave's table much more readable, and a lot easier to type from error free: Cheap-ass A3000 memory map: $_ff01_0000 - $_ffff_ffff Reserved $_ff00_0000 - $_ff00_ffff Zorro III autoconfig block $_8000_0000 - $_feff_ffff Reserved $_1000_0000 - $_7fff_ffff Zorro III board space $_0800_0000 - $_0fff_ffff Coprocessor slot board space $_0700_0000 - $_07ff_ffff A3000 Fast RAM $_0100_0000 - $_06ff_ffff Reserved (future motherboard space) $_00f8_0000 - $_00ff_ffff ROM $_00f0_0000 - $_00f7_ffff Production diagnostic ROM space $_00e9_0000 - $_00ef_ffff Zorro II I/O space $_00e8_0000 - $_00e8_ffff Zorro II autoconfig block $_00e0_0000 - $_00e7_ffff Reserved $_00b8_0000 - $_00df_ffff Motherboard I/O and reserved space $_00a0_0000 - $_00b7_ffff Zorro II I/O space $_0020_0000 - $_009f_ffff Zorro II memory space $_0000_0000 - $_001f_ffff Chip RAM Since the C compiler does not support this for input (or output, sort of), it can only be used for documentation, but it sure beats nothing, and doesn't conflict with either international usage mentioned above. Kent, the man from xanth.