On 8/2/05, Ash <[EMAIL PROTECTED]> wrote: > > If I have a superclass defined in one file, what's the preferred way to > make its definition available in another file at compile-time? I can > (include ...) the file, but I'm not sure that makes sense. What if I > need the superclass definition in several files? > > On a related note, I have a library that contains several superclasses, > defined in several different files. If I build this library as a shared > object, I can use (require-for-syntax ...) to pull in the superclass > definitions to any file that subclasses them in a program that uses > the library. If I build the library statically, I can't do this. Is > there any way to make superclass definitions from a static library > available? >
The canonical way is to include a seprate file with class-definitions that use the "protoype:" option, see the Meroon Postscript manual. It's not perfect, since it requires duplicatiing the defs for your class hierarchy. cheers, felix _______________________________________________ Chicken-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/chicken-users
