Changes between Version 3 and Version 4 of rfc51_rasterio_resampling_progress


Ignore:
Timestamp:
Dec 1, 2014, 10:42:50 AM (6 years ago)
Author:
Even Rouault
Comment:

RFC 51: Make GDALRasterIOExtraArg* psExtraArg argument of RasterIO() optional for out-of-tree code

Legend:

Unmodified
Added
Removed
Modified
  • rfc51_rasterio_resampling_progress

    v3 v4  
    122122GDALDataset and GDALRasterBand (non virtual) RasterIO() and (virtual)
    123123IRasterIO() methods have a new final argument psExtraArg of type GDALRasterIOExtraArg*.
     124This extra argument defaults to NULL for code using GDAL, but is required for
     125all in-tree code, so as to avoid that in-tree code forgets to forwards psExtraArg
     126it might have returned from a caller.
    124127
    125128GDALDataset::RasterIO() and GDALRasterBand::RasterIO() can accept a NULL pointer
     
    197200
    198201  * C++ users of the GDALRasterBand::RasterIO() and
    199     GDALDataset::RasterIO() API must add the new GDALRasterIOExtraArg* psExtraArg
    200     argument (potentially to NULL). It would have been possible to declare it as
    201     optional, but it would have then been more error prone to forget forwarding
    202     psExtraArg. This was especially true in the conversion phase, but now it is
    203     done, it isn't perhaps needed any more.
     202    GDALDataset::RasterIO() API do not need to change their code, since the new
     203    GDALRasterIOExtraArg* psExtraArg argument is optional for out-of-tree code.
    204204
    205205  * Out-of-tree drivers that implement IRasterIO() must be changed to accept the new