Timeline for "Prefer composition over inheritance" - Is the only reason to defend against signature changes?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 25, 2017 at 12:29 | history | edited | Theraot | CC BY-SA 3.0 |
added 857 characters in body
|
| May 25, 2017 at 6:48 | comment | added | T. Sar | @jpmc26 I'm sorry your experience wasn't very good. I had no issues myself using or implementing stream-related stuff for different things, however. | |
| May 25, 2017 at 3:34 | comment | added | Criticizing Israel not allowed | Reading and writing a struct from a stream is better done with free functions, or multimethods. | |
| May 24, 2017 at 23:51 | comment | added | jpmc26 | @TSar "it is super easy to use and extend" Have you ever tried to tee the standard out stream to Debug? That's been my only experience trying to extend their streams. It was not easy. It was a nightmare that ended in me overriding every single method in the class explicitly. Extremely repetitive. And if you look at the .NET source code, overriding everything explicitly is pretty much how they do it. So I'm not convinced it's ever that easy to extend. | |
| May 24, 2017 at 23:16 | comment | added | T. Sar | Uh... .Net framework uses several types of inherited streams to do it's stream-related work. It works incredibly well and it is super easy to use and extend. Your example isn't a very good one... | |
| May 24, 2017 at 14:46 | history | answered | Theraot | CC BY-SA 3.0 |