Messages in this thread |  | | Subject | Re: Compilation problems with 2.1.20, incorrectly globalized symbols | Date | Wed, 15 Jan 1997 23:37:39 -0500 | From | Buddha Buck <> |
| |
> Well, as they say in TQM class, the question is not how to eliminate > these instances of the problem, but how to ensure that future > instances never occur again. Off the top of my head, it seems like > the situation is for the gatekeeper (i.e., Linus) to enforce that > people don't abuse the global symbol namespace, in the same way he > enforces sane coding style.
Linux enforces sane coding style? Since when?
As far as I know, Linux has refused to dictate coding style -- the Documentation/CodingStyle file is a suggestion, not a requirement. To quote from that file, "Coding style is very personal, and won't _force_ my views on anybody...".
Yes, keeping this from happening again would require work from Linus. But I doubt that that is going to happen. As Alan Cox stated, most of the people working on this project consider working drivers more important than clean drivers, and that is what sets their priorities.
> There is also the additional problem that when I muck around in code > that someone else is writing and maintaining (possibly at this very > moment), I won't necessarily fix the problem right...
This is a major issue, and why these problems are best solved by the maintainers of the particular sections.
-- Buddha Buck bmbuck@acsu.buffalo.edu "Just as the strength of the Internet is chaos, so the strength of our liberty depends upon the chaos and cacaphony of the unfettered speech the First Amendment protects." -- A.L.A. v. U.S. Dept. of Justice
|  |