That's exactly my point. ifdef's of this kind never get disabled for the
so called *stable* kernels... :-(. This is just obvious lazzyness which
may contribute to the quite widespread oppinnion that linux leaks
proffesionality.
There's no speed measurable speed hit from the serial debugging code,
and 1800 bytes in the grand scheme of things is really not all that big.
Some schools of thought believe that it's important to leave such
debugging code in, so that if there is a problem in the field, you can
figure out what's going on and fix the problem that much quicker.
If people think that aesthetically this is ugly, they are of course
entitled to their own opinion. However, it's clear those people who
think that this sort of thing is important have looked at commercial
"professional" software.
I tend to be more impressed by technical arguments about the quality of
an OS than "aesthetic issues". Of course, if there are people who only
understand how to judge an OS based on such aesthetic qualities, I don't
mind catering to their little obsessions if it doesn't take much
effort. In this particular case the code has gone through enough
testing that I'm reasonably certain it won't cause a problem, which is
why I submitted a bug to Linus to disable it by default.
- Ted
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu