|
|
| (66 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| | I'm just a regular pleb from Australia. I'm not a member of the Soylent staff. |
| | |
| PHP/SQL/HTML/CSS and Delphi (Object Pascal) are my preferred languages.<br> | | PHP/SQL/HTML/CSS and Delphi (Object Pascal) are my preferred languages.<br> |
| I'm pedantic about code etiquette (indents, spaces, etc).<br>
| |
|
| |
| New to Perl but interested in learning. I have a basic perl virtual host set up on my dev machine.<br>
| |
|
| |
| Look out for me on #Soylent IRC.<br>
| |
|
| |
| Watch pages:<br>
| |
| [[Style]]<br>
| |
| [[CssWork|CSS Work]]<br>
| |
|
| |
| ==Code style==
| |
| Perl programming style guide:<br>
| |
| http://perldoc.perl.org/perlstyle.html
| |
|
| |
| Just to start the ball rolling ("borrowed" from perl.org):
| |
| * closing curly bracket of a multi-line BLOCK should line up with the keyword that started the construct
| |
| * 4-column indent (slashcode uses tab indents, but in gedit you can set tab width or raplace tabs - tab may be better anyway?)
| |
| * Opening curly on same line as keyword, if possible, otherwise line up
| |
| * Space before the opening curly of a multi-line BLOCK
| |
| * One-line BLOCK may be put on one line, including curlies
| |
| * No space before the semicolon
| |
| * Semicolon omitted in "short" one-line BLOCK
| |
| * Space around most operators
| |
| * Space around a "complex" subscript (inside brackets)
| |
| * Blank lines between chunks that do different things
| |
| * Uncuddled elses
| |
| * No space between function name and its opening parenthesis
| |
| * Space after each comma
| |
| * Long lines broken after an operator (except and and or )
| |
| * Space after last parenthesis matching on current line
| |
| * Line up corresponding items vertically
| |
| * Omit redundant punctuation as long as clarity doesn't suffer
| |
| If anyone has any others or wants to change any, feel free to do so. Maybe add a reason/background in change summary just so others know where you're coming from.
| |
|
| |
| We should maybe make a wiki page for coding style and develop it so that all our code is readable and consistent regardless of author.<br>
| |
| Also looking for one for other languages used for Soylent: CSS, HTML, JS, SQL
| |
|
| |
| Goes without saying, but HTML and CSS should be W3C compliant.
| |
|
| |
| ==Slashcode==
| |
| IHMO there are way too many folders nested in the slashcode source tree. There may be good reasons but I generally prefer a flat filesystem (as much as possible anyway) for code accessibility. Also helps to reduce likelihood of duplicate filenames.
| |
| What do other devs think of prefixing function names with source filename?<br>
| |
| For example, main() function in article.pl becomes article__main()<br>
| |
| Not suggesting that it all be changed to suit this convention right away, but might be handy for new functions to make it easier to figure out where things are declared.
| |
|
| |
| gedit identifies a syntax error in shtml.pl getFileText function (line 74).
| |
|
| |
|
| ===slashcode files of interest===
| | Look out for me on Soylent IRC (#Soylent and #)<br> |
| https://github.com/SoylentNews/slashcode/blob/master/themes/slashcode/htdocs/article.pl
| |
|
| |
|
| https://github.com/SoylentNews/slashcode/blob/master/themes/slashcode/htdocs/comments.pl
| | http://soylentnews.org/~crutchy/ |