Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!haven!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn)
Newsgroups: comp.sys.apple2
Subject: Re: Q: Orca/C vs APW C include file parsing
Keywords: ORCA, APW, C
Message-ID: <13615@smoke.BRL.MIL>
Date: 19 Aug 90 02:13:53 GMT
References: <792@dg.dg.com>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 27

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.

>  And finally (ok 4 questions) can anyone tell me the differences between
>the APW C and Orca/C compilers (ie: APW C has string.h and Orca/C has
>strings.h)?

ORCA/C has <string.h>, which is the standard header associated with
the str*() functions.  <strings.h> is a Berkeleyism that originated
with a misunderstood description of the <string.h> header that AT&T
was providing; more recent releases of BSD have contained <string.h>
(also <strings.h>, just because some BSD-specific applications were
now committed to using it).

The main differences are
	(1) ORCA/C is supported; APW C is not.
	(2) ORCA/C attempts to conform to the C standard; APW C
	implements one interpretation of an old nonstandard UNIX
	flavor of C.
	(3) ORCA/C has a much better debugging environment.