On 2004-06-07 13:10, Goodleaf, John [EMAIL PROTECTED] wrote:
It's a hard problem. How do you provide conventions that don't annoy
the hell out of programmers, but which ensure that legibile,
maintainable code is left?
First of all, I should note this: As long as there is a way to
Hello,
I'm abusing the mailing list because many of you are sickeningly
clever and have long experience in IT. I'm working to establish a
document (yep) providing guidance for our company's
small-but-growing IT group with regard to coding standards and
practices. It seems rife
On Monday 07 June 2004 20:10, Goodleaf, John wrote:
Hello,
I'm abusing the mailing list because many of you are sickeningly
clever and have long experience in IT. I'm working to establish a
document (yep) providing guidance for our company's
small-but-growing IT group with
On Mon, 7 Jun 2004, Goodleaf, John wrote:
the hell out of programmers, but which ensure that legibile,
maintainable code is left?
style(9) comes to mind there...
HTH
Olaf
--
Olaf Hoyer[EMAIL PROTECTED]
Fuerchterliche Erlebniss geben zu raten,
ob der, welcher sie erlebt, nicht
On Mon, Jun 07, 2004 at 09:55:10PM +, Daniela wrote:
I would have no problems with coding standards that allow you to clean up
_after_ a session, because I lose half of my good ideas while bothering with
coding standards. Good would be some convention where you can just modify
your code
On Mon, 7 Jun 2004 13:10:06 -0700
Goodleaf, John [EMAIL PROTECTED] wrote:
Hello,
I'm abusing the mailing list because many of you are sickeningly
clever and have long experience in IT. I'm working to establish a
document (yep) providing guidance for our company's
On Monday 07 June 2004 02:55 pm, Daniela wrote:
On Monday 07 June 2004 20:10, Goodleaf, John wrote:
Hello,
I'm abusing the mailing list because many of you are sickeningly
clever and have long experience in IT. I'm working to establish
a document (yep) providing guidance for our
