3 ms·
Unless your ReadByte function does something different than what the function you call assumes it does. For example, it might have different behaviour in edge
by Someone 13y ago
Unless your ReadByte function does something different than what the function you call assumes it does.
For example, it might have different behaviour in edge cases (end of file, I/O exception). One could call that bad architecture, but one could not even be aware of the existence of the broader interface that has a ReadByte member function, or one could (IMO rightfully) think the difference does not matter of you call a method taking an argument of interface type that does not include ReadByte.
In the absolutely worst case, it does something completely unrelated to what Read does. Unlikely? Yes, but it might be part of a badly factored class that also has code for reading from an A/D converter.