Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!uunet!overload!dillon From: dillon@overload.Berkeley.CA.US (Matthew Dillon) Newsgroups: comp.sys.amiga.programmer Subject: Re: Intuition Image structure rendering utilities Message-ID: Date: 27 Mar 91 17:36:55 GMT References: <1214@muleshoe.cs.utexas.edu> <1991Mar27.080423.22023@agate.berkeley.edu> Organization: Not an Organization Lines: 30 In article <1991Mar27.080423.22023@agate.berkeley.edu> pete@violet.berkeley.edu (Pete Goodeve) writes: >In article <1214@muleshoe.cs.utexas.edu> Jonathan Abbey says: >>.. Probably the best way to implement this sort of stuff is through dynamically linked object modules. That is, a running program makes a library call to dynamically link in an arbitrary object module. I have written a library to do this, although it is still somewhat primitive (and likes to run under 2.0). The concept is simple -- you simply link your main program with symbols and the dynamic loader finds the executable and picks out the symbols, then dynamically links in the requested object module, providing pointers to requested symbolic functions as a result. Thus, one simply defines the interface calls and support routines required (since the dynamically linked object module can link to any of the program's symbols, such as Move(), Draw(), printf(),...). Any third party can write object modules using the interface spec for a particular job (like converting or displaying images in one format or another). -Matt -- Matthew Dillon dillon@Overload.Berkeley.CA.US 891 Regal Rd. uunet.uu.net!overload!dillon Berkeley, Ca. 94708 USA