Re:Conceptual Debt Is Worse Than Technical Debt
by HillaryBriss on Wednesday December 30, 2015 @11:35PM
(#10816138)
(I wanted to add this to my other reply, but it's too late for that.)
Is there a method naming convention in Objective-C where the phrase "withExceptionXYZ" in the method declaration means "this method may throw an instance of ExceptionXYZ"?
This is from https://android.googlesource.com/platform/frameworks/base/+/... :
public static void readExceptionWithOperationApplicationExceptionFromParcel(
Parcel reply) throws OperationApplicationException {
int code = reply.readExceptionCode();
if (code == 0) return;
String msg = reply.readString();
if (code == 10) {
throw new OperationApplicationException(msg);
} else {
DatabaseUtils.readExceptionFromParcel(reply, msg, code);
}
}
I don't know Objective-C at all. Would this method name truly feel correct in that language?Thanks.
Re:Conceptual Debt Is Worse Than Technical Debt
by geofft on Friday January 01, 2016 @08:58PM
(#10824581)
I parsed saurik's comment as a joke based on Objective-C enjoying long names containing the word "with". Objective-C is relatively unique among programming languages in continuing the method name when specifying parameters, and "with" is a usual way of specifying them. For instance, one of the constructors for NSString is named "stringWithContentsOfFile:encoding:error:", and the way you'd call that method is something like [NSString stringWithContentsOfFile:@"file.txt" encoding:NSUTF8StringEncoding error:NULL].
However, in this context it's not used that way, because you're not taking an OperationApplicationException. Instead, yes, this appears to be a variant of readExceptionFromParcel that instead sometimes throws an OperationApplicationException. That use of the word "with" would not feel correct in Objective-C -- nor would the use of an exception, probably, since they are rarely used in Objective-C.
Re:Conceptual Debt Is Worse Than Technical Debt
by HillaryBriss on Saturday January 02, 2016 @05:40PM
(#10828347)
Ah. I just wasn't able to understand saurik's joke. Thank you for clarifying these things. Good stuff.
Re:Conceptual Debt Is Worse Than Technical Debt
by HillaryBriss on Wednesday December 30, 2015 @10:21AM
(#10812366)
Aha. Android SDK names aren't as bad as I thought!
Nice comment.
2) NUL is a character, while NULL is a pointer. These APIs are using the correct name for each scenario.
3) Checking if the user is a monkey (or now a goat) is a running gag. I don't think that is a naming mistake.
4) The usage of "exception" in that name is clearly different each time, though maybe it requires knowing Objective-C for that to feel "correct" (as the developer who named that function clearly is writing Objective-Java there ;P).
The spelling mistakes and inconsistencies are "awesome", though :(.