Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!unmvax!pprg.unm.edu!topgun!mustang!nntp-server.caltech.edu!toddpw
From: toddpw@nntp-server.caltech.edu (Todd P. Whitesel)
Newsgroups: comp.sys.apple2
Subject: Re: GS/OS Strings in Orca/C? How?
Message-ID: <1991Jan13.045015.25165@nntp-server.caltech.edu>
Date: 13 Jan 91 04:50:15 GMT
References: <1991Jan12.200743.24625@ee.ualberta.ca>
Organization: California Institute of Technology, Pasadena
Lines: 27

jpenne@ee.ualberta.ca (Jerry Penner) writes:

>Can anyone tell me how to properly put GS/OS class 1 strings into Orca/C
>programs?  I have the GS/OS Ref, which says next to nothing about using C
>with GS/OS, and the Orca/C manual says something to the effect that since
>C provides file access functions using the stdio.h library, it shouldn't be
>necessary to use GS/OS.  Hah.  Well I want to anyways.

So do I. I needed to device functions for DiskCopy. Print out the gsos.h file
and spend a little time looking at it. I'm mailing you some source code; it
should point you in the right direction.

>Also, when writing desktop programs in Orca/C, has anyone managed to get
>a simple desktop program running without using Orca's startdesk() and 
>enddesk() functions.  Mine just hangs.  Basically, all I do is start up

It hangs AFTER everything is finished? Are you using 1.1 or 1.0? With 1.0 (or
1.1 with stack repair off) passing an int to a function that needs a long
will create exactly that sort of behavior. When I still had 1.0 I gave up
on fread() and fwrite() because I thought they were screwed. Well they are
(they are declared as returning int and they should return size_t which is
long) but I had other problems because of the same effect.

If you are passing constants to functions make sure they have L's when needed.

Todd Whitesel
toddpw @ tybalt.caltech.edu