The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
APL programmers: a confusion
C or C++ programmers: a corruption
C# or Java programmers: a delegation
FORTRAN programmers: a computation
COBOL programmers: a company
BASIC programmers: an asylum
LISP programmers: a list (of course)
Pascal programmers: a school
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
The responses are very funny unfortunately someone might take this seriously so we need to let identity stay in the political area of our society and not let it enter our profession.
Such a sad state but it is what it is for now
How about a Byte? Each one in a group is a Bit. If there are more than 8 in the group, it's a Word of Software Engineers, more than 16 is a DoubleWord (or DWord), more than 32 is a QuadWord (or QWord), etc.
Sure, except that you can inherit multiple interfaces and you still can't instantiate one without an implementation.
Depending on how it is defined, it is possible to inherit an abstract class. Two cases in point are List<T> and Dictionary<object,object>. After all, generics are, for all practical purposes, abstract classes.
Architecturally, they still have highly different uses.
About that, I agree, so why muddy the waters with this new construct that is half interface and half virtual method?
David A. Gray
Delivering Solutions for the Ages, One Problem at a Time
Interpreting the Fundamental Principle of Tabular Reporting
After all, generics are, for all practical purposes, abstract classes.
I really don't agree with that.
I think in general the purpose of really surface-level default implementations give you options for interacting with those implementations or to give a default error. That's mostly it, or at least that's all I'd use it for. I don't see that as muddying.
I think it will result in much more composable code, and that's a valid purpose.
"Never attribute to malice that which can be explained by stupidity."
- Hanlon's Razor
Last Visit: 22-Nov-19 2:15 Last Update: 22-Nov-19 2:15