Inconsistency between Writeable and Writable in CVB

Programming Questions
, , ,
1

Hello,

while looking through the current CVB installation, I noticed an inconsistency in the naming around Writeable vs Writable.

For example:

  • cvb/genapi/_decl/decl_node.hpp exposes IsWriteable()

  • cvb/gevserver/_decl/decl_node.hpp exposes IsWritable()

From what I can see, this does not seem to be limited to the C++ headers only. The same difference appears to show up in other exposed surfaces as well, for example in Python stubs and in .NET XML documentation.

This is not a functional issue by itself, but it does make the terminology less consistent across APIs, wrappers, documentation, and downstream integrations.

Is this difference intentional?

If not, would it be possible to standardize on one spelling in a future release, preferably Writable?

And if a full cleanup is not practical in the short term, would it be possible to support both names for a transition period, so existing code keeps working while a preferred spelling is defined going forward?

Thanks.