Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!sdd.hp.com!wuarchive!uunet!cbmvax!cbmehq!cbmger!peterk From: peterk@cbmger.UUCP (Peter Kittel GERMANY) Newsgroups: comp.sys.amiga.hardware Subject: Re: Standard for long hex numbers? (Was: Re: Amiga and its memory map) Message-ID: <919@cbmger.UUCP> Date: 21 Feb 91 14:18:36 GMT References: <2207@ria.ccs.uwo.ca> <18881@cbmvax.commodore.com> <887@cbmger.UUCP> <1991Feb14.063939.28350@zorch.SF-Bay.ORG> Reply-To: peterk@cbmger.UUCP (Peter Kittel GERMANY) Organization: Commodore Bueromaschinen GmbH, West Germany Lines: 53 In article david@starsoft.hou.tx.us (Dave Lowrey) writes: >In article <1991Feb14.063939.28350@zorch.SF-Bay.ORG> xanthian@zorch.SF-Bay.ORG (Kent Paul Dolan) writes: >> >> 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 >> >> > 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.) >> >> Yes, there does exist a very nice international standard for this >> purpose, and I suggest we adopt it posthaste! >> >> Cheap-ass A3000 memory map: >> >> $_ff01_0000 - $_ffff_ffff Reserved > >Yuck! > >Why not use spaces? Many debuggers and such allow them. >I understand that underscores are easier to parse, but it looks awfull. > >ff01 0000 ff ab cc e1 ..... NOOOOOO! PLEASE, no spaces! See, for me (plus many people here) a space is a separator, we expect that something really different follows (you know, we write nouns together, like "Computerliteratur"). And here we must strongly separate one hex number from the other. It happens very often that you have two numbers directly following each other, just separated by a space as a normal word. (Also mixed with decimal numbers that are not preced by a $.) It would generate much confusion, if there also were spaces inside one of these numbers. So, for me the underscore doesn't look really nice, but it is functional. And if it is already standardized, why not join such a standard. -- Best regards, Dr. Peter Kittel // E-Mail to \\ Only my personal opinions... Commodore Frankfurt, Germany \X/ {uunet|pyramid|rutgers}!cbmvax!cbmger!peterk