Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cbmvax!bj
From: bj@cbmvax.commodore.com (Brian Jackson)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Aztec C and Enforcer
Message-ID: <16050@cbmvax.commodore.com>
Date: 25 Nov 90 02:04:03 GMT
References: <7127@sugar.hackercorp.com>
Reply-To: bj@cbmvax.commodore.com (Brian Jackson)
Organization: Commodore, West Chester, PA
Lines: 24

In article <7127@sugar.hackercorp.com> peter@sugar.hackercorp.com (Peter da Silva) writes:
>Enforcer tell me that programs compiled under Aztec C do lots of reads from
>location 8 with (READ-LONG) or 10 with (READ-WORD). I've looked through the
>runtime source and can't see where this is happening. Has anyone any ideas,
>or should I wait until I get the latest Aztec?
>
>(and what's the real official name? Manx or Aztec?)

Versions of Aztec ('Aztec C'is the name of the compiler while 'Manx
Software Systems' is the name of the company that brings it to you)
prior to v5.0d had quite a few Enforcer hits in them (both the
compiler and the code they generated). This seems to have been cured
in 5.0d. I use Aztec C quite a lot and the latest one has yet to cause
a hit (that I haven't created myself.)

bj

>Peter da Silva.   `-_-'

 -----------------------------------------------------------------------
 | Brian Jackson  Software Engineer, Commodore-Amiga Inc.  GEnie: B.J. |
 | bj@cbmvax.cbm.commodore.com    or  ...{uunet|rutgers}!cbmvax!bj     |
 | Simpson's Episodes are numbered in hex.                             |
 -----------------------------------------------------------------------