But why change class.c? Just hide the messy calls directly to the class.dll plugin in your plugin.
You could probably even write an internal routine in your plugin that generated the requirement PowerPro plugin format call by packing and unpacking szargs. The remaining arguments are just copies of what is passed into you plugin. It would be called from other places. This way there is less chance of breaking anything and your changes become independent of me issuing a new class.dll. > > > > BTW, not sure what you are trying to do, but have you thought about > > avoiding making changes to the plugin and instead just calling call to > > createstruct entry point directly (by allocating your own *szargs etc ) > > I'm trying to make as simple an interface as possible from my client dll to > class dll. Since the operations required (create a struct template, create a > new instance of a struct, read/write a struct member) have simple arguments, > be nice to provide equally simple entry points into class.dll. > > I could do that by just cutting and pasting your code for equivalent existing > service. Trying to get a bit neater than that. >
