I ask because some vendors spend much, much more time on the OLE interface (they're targeting the VB market) than they ever do on the "native" C/C++ interface. In fact, sometimes the C/C++ interface is really just a wrapper to a bunch of OLE calls.
So ask yourself: how badly is this per-call efficiency needed? If it is needed badly enough, which interface really is faster, and is the faster interface sufficiently faster so as to make a difference?
That said, it's also the case that some vendors will have an OLE interface that's just slapped on hurredly because marketing wanted it, whereas their real market is people who've been using their C/C++ libraries for years.
So which interface would you rather work with, debug, and optimize code in? Win32::OLE plus the OLE interface to this package, or XS plus the C/C++ interface? The answer will depend on the package in question and what you're most comfortable programming in.
In reply to Re: OLE vs XS
by fizbin
in thread OLE vs XS
by Flame
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |