Path: utzoo!utdoe!generic!pnet91!ericmcg
From: ericmcg@pnet91.cts.com (Eric Mcgillicuddy)
Newsgroups: comp.sys.apple2
Subject: Re: Hyper C and comp.sources.apple2, stand-along code, and whatever
Message-ID: <327@generic.UUCP>
Date: 31 Dec 90 23:50:03 GMT
Sender: root@generic.UUCP
Organization: People-Net [pnet91], Etobicoke, ON
Lines: 34

HyperC is standard K&R, if the source mentioned is ANSI it will not compile.
Since you mention that Aztec C compiled it I would guess that this is not the
problem. I will see about the source you mention, I suspect that more.c may be
shell dependent and may not work with the HyperC shell. There likely a few
system dependencies included.

I wrote scanf and do not appreciate it being called 'a patch'. :)
Adding anything to the library is a bit of a problem without the docs. Be sure
that you do not link the file before adding it to the library. Clone the 'cc'
file, but exclude the last to lines, this will then create unlinked .o files
that can be added to the 'libc' file. Try this command:

>lib /csys/libs/libc -rv /csys/scanf.o

That should add the scanf.o file to the end of the library and tell you what
it is doing while it is doing it (-r is replace and v is verbose). It takes
awhile.  Depending on the prefix that you have set and where the libc and
scanf.o files are located, you may not need full pathnames.

Some of the header files might work, but there should be quivalent HyperC ones
available. All I can say is try it.

To make stand alone programs you must include the opsys file as the first
system file on the floppy and call your program 'shell'. It can be either
native (created with ccn) 6502 code for speed or interpreted (made with cc)
p-code for size. Regardless the interpreter and run time libraries are in the
opsys file and it must be present between $800 and $2000 for any HyperC
generated code to run. 

Send me mail if you want more information on docs, or any other problems that
you may have.

UUCP: bkj386!pnet91!ericmcg
INET: ericmcg@pnet91.cts.com