Messages in this thread |  | | Date | Fri, 30 Nov 2001 10:20:43 -0800 | From | "Paul G. Allen" <> | Subject | Re: Coding style - a non-issue |
| |
antirez wrote: > > On Fri, Nov 30, 2001 at 11:47:28AM -0500, Jeff Garzik wrote: > > The security community has shown us time and again that public shaming > > is often the only way to motivate vendors into fixing security > > problems. Yes, even BSD security guys do this :) > > It's a bit different. Usually the security community uses it > when there isn't a way to fix the code (i.e. non-free code) > or when the maintaner of the code refused to fix the issue. > Also to "expose" the security problem isn't the same as > to flame. > > While not a good idea, something like a long name > for a local var isn't a big problem like a completly > broken software with huge security holes used by milions of people > every day. >
A variable/function name should ALWAYS be descriptive of the variable/function purpose. If it takes a long name, so be it. At least the next guy looking at it will know what it is for.
PGA -- Paul G. Allen UNIX Admin II ('til Dec. 3)/FlUnKy At LaRgE (forever!) Akamai Technologies, Inc. www.akamai.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |