Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!apple!vsi1!zorch!xanthian From: xanthian@zorch.SF-Bay.ORG (Kent Paul Dolan) Newsgroups: comp.sys.amiga.programmer Subject: Re: Modula-2, where are you? Message-ID: <1991Feb15.061916.28212@zorch.SF-Bay.ORG> Date: 15 Feb 91 06:19:16 GMT References: <4702@mindlink.UUCP> <1991Feb13.004919.21783@zorch.SF-Bay.ORG> <1991Feb14.164633.8014@bony1.bony.com> Organization: SF-Bay Public-Access Unix Lines: 32 xanthian@zorch.SF-Bay.ORG (Kent Paul Dolan) writes: > Well, someone told me about four months ago that the functionality of > direct access to absolute machine addresses in the Modula-2 standard > was not implemented in Benchmark, for example. stevef@bony1.bony.COM (Steve Faiwiszewski) writes: > Could you please explain further? Benchmark can certainly directly > access absolute machine addresses. Please note carefully the "someone told me" above; I make no claim that I have checked this for myself. What I was told was that the following declaration, copied from page 229 of Edward J. Joyces 1985 _Modula-2, A Seafarer's Manual and Shipyard Guide_, either would not compile or would not do what was expected (I think the former) under BENCHMARK Modula-2, where the intent is to declare a variable whose data is stored at an absolute machine address: VAR PortStat[0FFFH]: BITSET; (* Port status at address hexadecimal 0FFF *) Which, I did check the Wirth 4th Edition Modula-2 manual, is indeed legal Modula-2. I'd love to be told I'm wrong, but not nearly as much as I'd love to be told the braindead 64K data element size was fixed in an upgrade to BENCHMARK. Kent, the man from xanth.