Re: [gdal-dev] Doxygen Arguments

2024-05-09 Thread Andrew Bell via gdal-dev
Thanks to all who looked at this and Even for resolution. On Thu, May 9, 2024 at 12:11 PM Even Rouault wrote: > Andrew, > > this is now fixed per > https://github.com/OSGeo/gdal/commit/393eee77b40ae16751e4d2c0ad3e53386b22d025 > . Doxygen apparently takes the function/method at declaration time,

Re: [gdal-dev] Doxygen Arguments

2024-05-09 Thread Even Rouault via gdal-dev
Andrew, this is now fixed per https://github.com/OSGeo/gdal/commit/393eee77b40ae16751e4d2c0ad3e53386b22d025 . Doxygen apparently takes the function/method at declaration time, and not definition time, and we had a number of unnamed parameters in declarations. (I also struggled with weird

Re: [gdal-dev] Doxygen Arguments

2024-05-09 Thread Daniel Baston via gdal-dev
It looks like Doxygen is using argument names from the function prototype instead of the implementation: https://github.com/OSGeo/gdal/blob/master/gcore/gdal_priv.h#L753 I did some searching but didn't come across a way to change this behavior. It looks like many other functions include the

[gdal-dev] Doxygen Arguments

2024-05-09 Thread Andrew Bell via gdal-dev
Hi, I'm looking at the documentation for GDALRasterBand::RasterIO and it's surprising that the names of the arguments aren't included in the function prototype despite them being in the doxygen function definition. The arguments are described well below the function prototype, making it hard to