Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uunet!dg!archive!bkahn
From: bkahn@archive.rtp.dg.com (Bruce Kahn)
Newsgroups: comp.sys.apple2
Subject: Q: Orca/C vs APW C include file parsing
Keywords: ORCA, APW, C
Message-ID: <792@dg.dg.com>
Date: 17 Aug 90 16:31:04 GMT
Sender: root@dg.dg.com
Reply-To: bkahn@archive.rtp.dg.com (Bruce Kahn)
Organization: Data General Corporation, Research Triangle Park, NC
Lines: 25


  Ok, Im back w/another C question.  I have Orca/C 1.1b9 (the upgrade is 'in
the mail') and want to compile C written (and compiled) under APW C.  If
I #include the file stdlib.h with Orca/C I get the error:

39:  void *bsearch(void *key, void *base, size_t count, size_t size, 
        int (*compar) (const void *p1, const void *p2));
                      ^ ) expected

  Im assuming that since this is a standard include file that the routines
SHOULD be parsable by the compiler (silly me I know).  Has anyone else ever
used stdlib.h with Orca/C and NOT had this problem??
  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?
  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)?


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