Newsgroups: comp.sys.next
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usenet
From: Garance_Drosehn@mts.rpi.edu
Subject: Re: C Programming questions
Message-ID: <qq=gsrf@rpi.edu>
Nntp-Posting-Host: gilead.its.rpi.edu
Organization: Rensselaer Polytechnic Institute
References: <h4+gjkn@rpi.edu>
Date: 6 Apr 91 22:47:23 GMT
Lines: 35

In article <h4+gjkn@rpi.edu> 
           Garance_Drosehn@mts.rpi.edu (that's me...) writes:
>Time for a few programming questions!

And now I'll summarize all the answers I got.

>1) Is there some manual or set of manuals for programming the Next, or should
>   I just look thru all the digital-library documents?

The answer here seems to be "b", just look thru all the online documentation.

>2) What I'm working on includes a library of subroutines.  I can compile them
>   OK, but what commands do I need to turn them into a subroutine library?

check "ar" and "ranlib" in the man pages.

>3) I tried to come up with the magic parameters to the "ld" command to load
>   all my C object files into a runnable application. (...skipping along...)
>   I then took (what I consider) the sleazy way out and used:
>          cc -o my.app ${OBJECTS}

The unanimous answer here was that using "cc" was the correct way to do what I
wanted.  My experience from some other (non-Unix) systems was simply leading me
down the wrong path.

>4) Once I got past the loader, the program basically works.  One odd thing
>   (compared to what I've seen on other platforms) is that the fprintf
>   subroutine seems to always return a value of zero. (...etc...)

The concensus was that I'd be smarter not to use the return value from fprintf
anyway, because fprintf returns different things on different systems.  While I
have nothing but thanks for the other three answers, I'd like to quibble about
this answer a bit.  I'll do that in a separate thread though.

Garance_Drosehn@mts.rpi.edu   or  gad@eclipse.its.rpi.edu
