--- In [email protected], "brucexs" <bswit...@...> wrote:
> I thought I posted a note this morning about an alternate approach: rather > than modifying class.c just call the plugin entry points like getobject or > definestruct directly with the arguments set up in szargs and process the > results. > > That way we don't have to keep retesting class.c and you don't have to depend > on me distributing a new version (or users of your plugins downloading a > special version of class.dll). > > Does that make sense? Yes, despite all my rewrites to class.c. But I use vec services all over the place, might well end up using class as well. Seems silly to keep pasting the same code in plugin after plugin. Maybe a glue.dll, whose only job is to translate C-friendly calls to vec, class, or any other of the Bruce-provided dlls, and do the stuff required to call your standard service entry points. Means users got to remember to download a support dll if e.g. they want to use vecs in e.g. database plugins, but that shouldn't be a big deal. Or: leave vec the way it is, with me occasionally asking you to make a modification. I seem to be able to put hooks into vec.dll without messing with your code much. Then have classglue.dll, specifically to bind to class plugin. ??
