Add const keyword to Get methods on class interfaces

MichaelSzaszy — Mon, 25 Apr 2011 18:41:53 GMT

Without the const keyword attached to get methods you cannot create any const references to fGDB types. Example:

void func(const Geodatabase *pGdb)
{
pGdb->GetDatasetTypes(...); // Error
}

void func2(const Geodatabase &gdb)
{
gdb.GetDatasetTypes(...); // Error
}

This prevents us from writing more robust code that is self documenting (const indicating that we will not mutate the state of the object within the code).

Were these attributes omitted because the internal implementation of the fGDB classes do mutate state from the invocation of such methods? If so does applying mutable to the offending fields resolve any of these internal issues?

Thanks,

Mike

Re: Add const keyword to Get methods on class interfaces

LanceShipman — Mon, 15 Aug 2011 15:22:24 GMT

We have added the const keyword to most Get functions in the 1.1 version of the API. This should allow the writing of more robust code.

topic Re: Add const keyword to Get methods on class interfaces in File Geodatabase API Questions

Add const keyword to Get methods on class interfaces

Re: Add const keyword to Get methods on class interfaces