Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!src.honeywell.com!msi.umn.edu!cs.umn.edu!kksys!orbit!pnet51!chucks
From: chucks@pnet51.orb.mn.org (Erik Funkenbusch)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Is it me or Manx C 5.0c (the -MR option)
Message-ID: <4267@orbit.cts.com>
Date: 3 Mar 91 11:45:01 GMT
Sender: news@orbit.cts.com
Organization: People-Net [pnet51], Minneapolis, MN.
Lines: 23

Ata@system-m.phx.bull.com (John G. Ata) writes:
>Manx knows about this bug but chose not to fix it.  You can get around
>this problem by optimizing (-so).  It still exists in 5.0d, but haven't
>tried 5.0e yet.
>
>                              John


funny, the 5.0e release is just a cc replacement, and it still says 5.0d when
you run it.  wonders will be wonders.

speaking of Aztec 5.0.  I'm trying to write some pure code.  i understand not
to reference any globabl variables such as stdin, stdout, errno, etc.  the old
aztec had a resident startup code, this is missing now, however going through
the supplied startup code i notice many things that are allocated dynamically.
 is this startup code also re-entrant?  i see a problem with the global device
table.  even though the space is allocated dynamically, the reference is still
global.  does this mean i can't use any manx dos routines if i want re-entrant
code?  anyone with some experience, help would be appreciated.

UUCP: {amdahl!tcnet, crash}!orbit!pnet51!chucks
ARPA: crash!orbit!pnet51!chucks@nosc.mil
INET: chucks@pnet51.orb.mn.org