--- In [email protected], "brucexs" <bswit...@...> wrote: > > > 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. class: Yes, fine. I'll either make a glueclass.dll to do the job (to avoid replicating code in many plugins, if I ever go that way), or stuff it in plugin in question. vec: simple change, included in ClassAndVec.zip, modifies none of your code, adds a dll-to-dll service not available any other way (return number of columns: basically, is vec 1d or 2d). Okay incorporating those changes in next version pp?
