What are examples for opposing implementations / miswording within the .net / java framework?
In Java, java.lang.System.arraycopy
- notice the lowercase c.
Also NullPointerException
Java is better than NullReferenceException
.NET.
AppDomain
violates a convention that usually does not use abbreviations.
Control.ID
breaks the explicit pascal cover id convention with "Id" and Camel wraps around its "id".
EDIT: Due to popular demand, there are a couple more ... although they are more simply named than conditionals.
SortedList
in .NET - this explains what an implementation is, but doesn't give a good idea of what a dictionary API is.
Type.MakeGenericType
- it creates a constructed type. Too MethodInfo.MakeGenericMethod
.
source to share
- IPEndPoint splits the compound caps guideline (which, oddly enough, specifically calls the endpoint as an example).
- All Interop links are verboten because they are an abbreviation for interop. Luckily, they left them as Interop, though.
I swear there by an attribute or something completely wrong, but I can't remember it from my head. But there is always a funny case of HTTP_REFERER .
source to share
java.util.Hashtable
If it is a HashSet and a HashMap, then it must be a HashTable.
Not breaking the rules, but I've always hated: UndoableEdit
My mind seems to parse this as an Un (doable) edit, that is, an edit that cannot be done, rather than a correct interpretation of an UnDo-able Edit, which means an edit that can be undone.
source to share