Archived
This forum has been archived. Please start a new discussion on GitHub.
Code convention for .Net Ice libraries
It seems that .Net libraries of Ice are following the Java naming conventions (no capital for method names for example).
It would nicer if the .Net naming conventions where followed by the Ice assemblies. Although not critical, it's the kind of things that makes you feel at home while using Ice.
It would nicer if the .Net naming conventions where followed by the Ice assemblies. Although not critical, it's the kind of things that makes you feel at home while using Ice.
0
Comments
-
Most of the Ice APIs are generated from Slice definitions, so the same single set of Slice files is used for all implementation languages. If we were to change the definitions to match the .NET naming convention, we would break every piece of existing Ice source code ever written.
But, even assuming we could do that, we'd still not be able to please everyone because, after the renaming exercise, the convention would now be wrong for Java.
Personally, I think that .NET is the odd one out here: it's unusual for a convention to use an initial upper-case letter for methods and properties.
Cheers,
Michi.0 -
Ok, thanks for the answer. I was not aware that such a change would impact all the other languages as well.
Joannes0
