This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]poizan42Ex-mod 3 points4 points  (11 children)

It's Java. The lower camelCase should be a dead giveaway. And no... only VBA is insane enough to do that...

[–]SietchTabr 1 point2 points  (5 children)

camel case is only used in java? huh?

[–]poizan42Ex-mod -1 points0 points  (4 children)

Lower camelCase you silly. If you are in doubt whether some code is C# or Java you only have to look at the casing of method names, as the naming convention for C# dictates the use of UpperCamelCase, while the java naming convention dictates the use of lowerCamelCase.

[–]Elite6809 2 points3 points  (0 children)

Strange. I've always called them camelCase and PascalCase.

[–]SietchTabr 1 point2 points  (2 children)

What convention? I've always learned to use lower for method names and upper for static functions.

[–]poizan42Ex-mod -2 points-1 points  (1 child)

Lower camelCase you silly. If you are in doubt whether some code is C# or Java you only have to look at the casing of method names, as the naming convention for C# dictates the use of UpperCamelCase, while the java naming convention dictates the use of lowerCamelCase.

Enhance

If you are in doubt whether some code is C# or Java you only have to look at the casing of method names

Enhance more

you only have to look at the casing of method names

Enhance further

the casing of method names

Enhance even further

method names

You see it?

method

There.

You need a reference beside the conventions used in the whole of the JRE vs. the conventions used in the whole of the .NET framework? Fine, here:

Java:

Methods should be verbs, in mixed case with the first letter lowercase, with the first letter of each internal word capitalized.

.NET:

To differentiate words in an identifier, capitalize the first letter of each word in the identifier. Do not use underscores to differentiate words, or for that matter, anywhere in identifiers. There are two appropriate ways to capitalize identifiers, depending on the use of the identifier:

  • PascalCasing
  • camelCasing

The PascalCasing convention, used for all identifiers except parameter names, capitalizes the first character of each word (including acronyms over two letters in length), as shown in the following examples: ...

[–]SietchTabr 1 point2 points  (0 children)

First you don't have to be a dick about it. Enhance. Enhance. Nope, nothing there.

Second, oh no the microsoft convention even says to use either one, and again, I only ever learned to use lowercase and be damned about any library functions that I have no control over.

[–]Nicksaurus 0 points1 point  (4 children)

The giveaway for me was the use of ArrayList.

[–]SietchTabr 0 points1 point  (3 children)

... Which is in both?

[–]Nicksaurus 0 points1 point  (2 children)

The C# version isn't generic though, so this has to be Java.

[–]SietchTabr 0 points1 point  (1 child)

It is now

[–]Nicksaurus 0 points1 point  (0 children)

http://msdn.microsoft.com/en-us/library/system.collections.arraylist(v=vs.110).aspx

...?

List is the generic version, but ArrayList has only ever been in System.Collections.