Le dimanche 31 août 2014 22:44:00, Robert Coup a écrit :
> Excellent :)
>
> There's obviously no nice run-time solution using the C++ API,
Yes, that could be possible if the C++ public API had redirection to driver
implementation methods. In GDAL, we have that with some methods like
RasterIO()
Excellent :)
There's obviously no nice run-time solution using the C++ API, though I
guess callgrind/linux-perf can do it - do you have any experience worth
sharing there?
Rob.
On Mon, Sep 1, 2014 at 7:14 AM, Even Rouault
wrote:
> Le dimanche 31 août 2014 20:50:41, Robert Coup a écrit :
> > T
Le dimanche 31 août 2014 20:50:41, Robert Coup a écrit :
> That's cool :) Is there any particular performance penalty to compiling
> *with* OGRAPISPY_ENABLED and then running *without*
> OGR_API_SPY_FILE/OGR_API_SPY_SNAPSHOT_PATH
> set?
Hi Robert,
Hopefully no, see for example :
OGRFeatureH OGR_
That's cool :) Is there any particular performance penalty to compiling
*with* OGRAPISPY_ENABLED and then running *without*
OGR_API_SPY_FILE/OGR_API_SPY_SNAPSHOT_PATH
set?
Rob :)
On Sun, Aug 31, 2014 at 11:34 PM, Even Rouault
wrote:
> Hi,
>
> This will not be of interest for the crowds, but ma
Hi,
This will not be of interest for the crowds, but mainly for OGR driver
developers (and potentially also to get precise bug reports from users). I'm
currently adding update capabilities to the MITAB driver, and while playing
with QGIS, there are sometimes sequences of OGR calls that trigger
