User:Crutchy: Difference between revisions
No edit summary |
|||
Line 16: | Line 16: | ||
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. | 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. | ||
Also looking for one for other languages used for Soylent: CSS, HTML, JS, SQL | Also looking for one for other languages used for Soylent: CSS, HTML, JS, SQL | ||
==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. |
Revision as of 11:02, 23 February 2014
PHP/SQL/HTML/CSS and Delphi (Object Pascal) are my preferred languages.
I'm pedantic about code etiquette (indents, spaces, etc).
New to Perl but interested in learning. I have a basic perl virtual host set up on my dev machine.
Look out for me on #Soylent IRC.
Code style
Perl programming style guide:
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. Also looking for one for other languages used for Soylent: CSS, HTML, JS, SQL
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.