> With partial casing, who give a f*** about the library author's casing style? > Just follow the style guide, no matter what.
-> IntelliSense / Code completion: Will follow the original authors there casing. In other words you are then forced to use code completion & edit the code structure for each function call. Great idea for production coding. ;) -> People following guides. Good luck on that. I can guarantee that unless you work for a dictatorship team, different styles will flow out. Its extreme hard to change people there previous build up experience / training. :( -> External developers. Good luck again on getting them to perfectly follow the casing guide. In general they work on different projects for different departments or clients. So different styles will show up. Or simply laziness with code completion. Its nice in theory, in practice things always turn out different. * * * * identifier_comparison_ignore_underscore * identifier_comparison_ignore_case_first_letter * identifier_comparison_ignore_case_rest_letters Sounds perfect to me. It will add a large amount of flexibility. And if that integrates with code completion, there is no reason why styles differ ( if the IDE's ). And if people are bothered with the "free" casing style, it can now be reported that you can have free or fixed styling. More options, more fun :) cjxgm: Want to put it forward to the Nim committee for a vote? :)
