I'm afraid I've missed this change quite much since it was so nicely
backwards compatible.
It doesn't make sense to have two classes in the Perl bindings when
there is really only one in the library - it's too confusing. That means
I'll need to remove the OGR Driver and DataSource classes comp
On 13.11.2015 16:37, Even Rouault wrote:
Not sure if it is a "swig" limitation, or something in the Perl
bindings. But the Python and Java bindings for sure can use the vector
part of GDALDatasetShadow.
Ok, I've missed all that. Sigh. Until now there's been a strict
difference between raste
Le vendredi 13 novembre 2015 15:17:40, Ari Jolma a écrit :
> On 13.11.2015 15:58, Even Rouault wrote:
> > Le vendredi 13 novembre 2015 14:48:02, Ari Jolma a écrit :
> >> OGR_Dr_Open became deprecated in 2.0 but it is still the main method to
> >> open vector datasets in the bindings.
> >>
> >> I j
On 13.11.2015 15:58, Even Rouault wrote:
Le vendredi 13 novembre 2015 14:48:02, Ari Jolma a écrit :
OGR_Dr_Open became deprecated in 2.0 but it is still the main method to
open vector datasets in the bindings.
I just realized that I would need one method to open all data sets.
OpenEx seems to
Le vendredi 13 novembre 2015 14:48:02, Ari Jolma a écrit :
> OGR_Dr_Open became deprecated in 2.0 but it is still the main method to
> open vector datasets in the bindings.
>
> I just realized that I would need one method to open all data sets.
> OpenEx seems to be it but I would still need to cas
OGR_Dr_Open became deprecated in 2.0 but it is still the main method to
open vector datasets in the bindings.
I just realized that I would need one method to open all data sets.
OpenEx seems to be it but I would still need to cast the object into a
Dataset or a DataSource. Maybe OpenEx should
