Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!dg!dg-rtp.dg.com!bkahn
From: bkahn@dg-rtp.dg.com (Bruce Kahn)
Newsgroups: comp.sys.apple2
Subject: Re: Q: Orca/C vs APW C include file parsing
Keywords: ORCA, APW, C
Message-ID: <807@dg.dg.com>
Date: 20 Aug 90 15:37:24 GMT
References: <792@dg.dg.com> <13615@smoke.BRL.MIL>
Sender: root@dg.dg.com
Reply-To: bkahn@dg-rtp.dg.com (Bruce Kahn)
Organization: Data General Corporation, Research Triangle Park, NC
Lines: 27

In article <13615@smoke.BRL.MIL>, gwyn@smoke.BRL.MIL (Doug Gwyn) writes:
|> In article <792@dg.dg.com> bkahn@archive.rtp.dg.com (Bruce Kahn) writes:
|> >  Under the same token (no pun intended), will APW C allow you to, in an
|> >include file, declare a variable as 'extern int Flag_A' and then within 
|> >the source code redeclare it as 'int Flag_A' w/o choking??  Is this 'legal'
|> >by ANSI C definitions?
|> 
|> Certainly, as I understand what you're describing, it is allowed.
|> The only objects that cannot be declared multiple times are those
|> having no linkage.  You're describing objects with external linkage.
|> 

  Finally got ahold of Mike and he told me that 1.1b9 does NOT do this
and that this bug has been fixed in the final release.  The 'final release' is
being 'bundled now' but he didnt give a shipping date for when they will
be sent out to users.  Sure hope it comes soon as I dont plan on hacking my
code to work just because of this...
  
  I think my problem using stdlib.h was due to the fact that I overwrote my 
Orca/C include file with my APW Tools & APW C include files.  Time to sort out
my include trees...

--
                                            Bruce (bkahn@archive.rtp.dg.com or
                                                   kahn@adam.dg.com)
  
  Standard disclaimers apply, except where prohibited by law...