I used to think this kind of thing too.
Each language (or large-subset-of-language) has it's own conventions.
Examples:
gnu/posix C: lower_underscore_case
Microsoft C (eg the win32 api): UpperCamelCase
Java: lowerCamelCase
Javascript: lowerCamelCase
.NET: UpperCamelCase (except local variables which seem to be
lowerCamelCase)
ruby/python: lower_underscore_case
While none of the languages will stop you from using any conventions
you like, it's MUCH easier to learn to put your ego aside, and go with
the conventions.
The simple fact is, you're going to be reading loads of sourcecode
written by others in the form of examples and so forth, and if you get
annoyed every time you see stuff you 'hate' - well you're going to be
having a pretty unhappy time.
On 25/10/2008, at 2:11 PM, Ted Milker wrote:
On Fri, Oct 24, 2008 at 7:54 PM, Curt Hagenlocher
<[EMAIL PROTECTED]> wrote:
We're thinking now that we're going to go with the mangled version
of the
name instead of the originally cased-version. "Dispose" just
doesn't look
Rubyish enough. Any objections?
My opinion does not count for much but I love Ruby openness and hate
the naming conventions. I much prefer camel case and .NET guidelines
for naming than underscore and lowercase hell. I am just getting
started with Ruby and have no intention of following the naming
conventions if I can avoid it. IronRuby and .NET are my platform of
choice for the future, even in its immature state.
_______________________________________________
Ironruby-core mailing list
Ironruby-core@rubyforge.org
http://rubyforge.org/mailman/listinfo/ironruby-core
_______________________________________________
Ironruby-core mailing list
Ironruby-core@rubyforge.org
http://rubyforge.org/mailman/listinfo/ironruby-core
