🚀 go-pugleaf

Sender: 
Reply-To: jnh@ece-csc.UUCP (Joseph Nathan Hall)
Followup-To: 
Distribution: 
Organization: North Carolina State University, Raleigh, NC
Keywords: 

Two questions ...

1)  I'd like to be able to compile several CODE resources with similar
    interface routines, and then load and call them on-the-fly.  How can
    I make calls into a CODE resource ... ?  (I'd like to have something
    that works sort of like a UN*X dynamic link.)

2)  (Easier question)  What do I do to get my application to start up and
    load a document when I double-click that document in the Finder?  (I've
    already got the ICN#, FREF, BNDL resources set up correctly; I just don't
    know how to tell what file I should load once the application's running.)

Thanks lots ...

My previous invective concerning the THINK C editor still stands, despite
Mr. Siegel's suggestion that I ought to go out and find a different
programming environment if the one I have doesn't suit.  Well, it actually
suits me pretty well, thanks, and I have no complaints about compilation
speed, efficiency, or the environment in general.  But I think the editor
has some pretty chintzy features (or lack thereof).  At the least you ought
to be able to move around easily without using the mouse and/or too many
control-shift-option-command-key combinations.  In addition, an option for
a "preferred alternate editor," to be invoked in lieu of the THINK C editor
(in MultiFinder), would be nice.

Oh, and correct support for draft-ANSI-style function declarations would
be nice, too ... what about lint, while you're at it ... gee whiz, a VAX/11
cross-compile mode would be nice, too ...

:-)

-- 
v   v sssss|| joseph hall                      || 201-1D Hampton Lee Court
 v v s   s || jnh@ece-csc.ncsu.edu (Internet)  || Cary, NC  27511
  v   sss  || the opinions expressed herein are not necessarily those of my
-----------|| employer, north carolina state university . . . . . . . . . . .