| |||||||||||||
Getting the right kind of contributionsGetting the right kind of contributionsPosted May 30, 2008 1:23 UTC (Fri) by pr1268 (subscriber, #24648)In reply to: Getting the right kind of contributions by roc Parent article: Getting the right kind of contributions
We obviously need a programming language in which there is only one valid way to write a given sequence of tokens, and all other inputs generate compiler errors. Such a language already exists: RPG. Just don't expect to see much Linux kernel development in it anytime soon! <sarcasm> Here's yet another (audacious) proposal: Let's get rid of whitespace altogether (except, of course, those spaces required by the C language, i.e., after type declarations, or those in string literals). This would mean one unified coding standard which would not be subject to debate. Pray that the whitespace-free code works right, because debugging and modifying it would be a real nightmare! </sarcasm>
(Log in to post comments)
Getting the right kind of contributions Posted May 31, 2008 23:59 UTC (Sat) by csawtell (subscriber, #986) [Link] Although you have marked it "sarcasm" this is the most sensible suggestion I have seen during this whole debate about source code formatting. C code expressed in white-space free format could be used as the Standard C Code Interchange and 'Difference & Patch' Format for the Linux Kernel. Programs to convert between the unformatted - Interchange - format and the many formats desired by the Kernel contributers could be created as required. The Wikipedia pretty print and code beautifier has some examples.
|
|||||||||||||