Is this how we deprecate now?
-
Yoy. At least they used camel casing ;)
static void AddEquipment(object dontUseThisWeHaveToDeleteThisMethod)
The parameter isn't used in the method...I think that the guy must've added the param to the method to make other code break (maybe using the compiler to find where it was called from) and then basically abandoned the code. Didn't comment anything or comment the code out or anything. I think I'm going to start using gems like this for NEW methods. Just sprinkle a couple of these across new APIs and let people wonder...
-
Yoy. At least they used camel casing ;)
static void AddEquipment(object dontUseThisWeHaveToDeleteThisMethod)
The parameter isn't used in the method...I think that the guy must've added the param to the method to make other code break (maybe using the compiler to find where it was called from) and then basically abandoned the code. Didn't comment anything or comment the code out or anything. I think I'm going to start using gems like this for NEW methods. Just sprinkle a couple of these across new APIs and let people wonder...
I like that! A former collegue of mine had a tendency to use very long and elaborate variable/function/method/property names. One day i invented an unused property called __AVeryLongAndLargelyUnusedProperty_PKA. PKA being his initials. Need i say that i forgot all about it. The thing went into production, until years later PKA one day yelled at me: What the shikes is this?
-
Yoy. At least they used camel casing ;)
static void AddEquipment(object dontUseThisWeHaveToDeleteThisMethod)
The parameter isn't used in the method...I think that the guy must've added the param to the method to make other code break (maybe using the compiler to find where it was called from) and then basically abandoned the code. Didn't comment anything or comment the code out or anything. I think I'm going to start using gems like this for NEW methods. Just sprinkle a couple of these across new APIs and let people wonder...
-
Yoy. At least they used camel casing ;)
static void AddEquipment(object dontUseThisWeHaveToDeleteThisMethod)
The parameter isn't used in the method...I think that the guy must've added the param to the method to make other code break (maybe using the compiler to find where it was called from) and then basically abandoned the code. Didn't comment anything or comment the code out or anything. I think I'm going to start using gems like this for NEW methods. Just sprinkle a couple of these across new APIs and let people wonder...
public int F ( int Reserved ) ...
-
Yoy. At least they used camel casing ;)
static void AddEquipment(object dontUseThisWeHaveToDeleteThisMethod)
The parameter isn't used in the method...I think that the guy must've added the param to the method to make other code break (maybe using the compiler to find where it was called from) and then basically abandoned the code. Didn't comment anything or comment the code out or anything. I think I'm going to start using gems like this for NEW methods. Just sprinkle a couple of these across new APIs and let people wonder...
Hmmm, let's improve it!
static void AddEquipment(object dontUseThisWeHaveToDeleteThisMethod)
{
if (dontUseThisWeHaveToDeleteThisMethod is bool && (bool)dontUseThisWeHaveToDeleteThisMethod) return;
}Seems better?