|
|
| (71 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
| |
|
| |
|
| 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.
| | Look out for me on Soylent IRC (#Soylent and #)<br> |
| Also looking for one for other languages used for Soylent: CSS, HTML, JS, SQL
| |
|
| |
|
| ==Slashcode==
| | http://soylentnews.org/~crutchy/ |
| 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.
| |
Latest revision as of 09:34, 20 February 2015
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.
Look out for me on Soylent IRC (#Soylent and #)
http://soylentnews.org/~crutchy/