It depends on the project. The worst approach, IMO, is deciding what your style will be without taking what kind of project it is into account. For smaller projects, or small teams of developers who are all good in the various languages used, it might be that separating things adds more complexity then is necessary.
Personally, I find separation on functionality far more important than separation on language. It shouldn't be needed to reshuffle files around if you rewrite part of your program in C. I do agree though that there shouldn't be SQL mixed with Perl (C, Java, Python, whatever). All SQL code should live in the database - and all the code is allowed to do is to call stored procedures. And the code calling the stored procedures should be in a layer itself as well. Hence, I wouldn't use MySQL, as that doesn't have stored procedures. (Or triggers. Or subselects.)
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||