Here's a list of coding convetions to follow: http://mindprod.com/unmain.html . Especially important to follow them in this economy. ;)
The only naming convention i know that "fusebox" recommends is the dsp_, act_, etc stuff, but even that isn't laid out in stone. Naming conventions and general coding conventions are left to the individual/team. Personally i don't like hungarian notation and won't use it unless that's the standard for that particular team. I've found it's nice when the code is all pristine, but after a few cycles of maintenance and such it becomes much more of a hindrance. Again, personal preference/style, just like where to put the opening curly brace. I'll take a nice clean design over naming conventions any day (within reason of course. hehe). Bob >>> [EMAIL PROTECTED] 06/14/02 01:10AM >>> What are the recommended naming conventions for fusebox code, if any? I see people write variables in all caps, mixed case, lower case, etc. Is it xfa.something or XFA.something? Personally, I tend to use Hungarian notation for everything. I find it makes the code look nice and consistent. (And not just because I'm Hungarian...) I prefer xfa.variableName, fusebox.targetCircuit, query.fieldName, etc. I use the same notation whether it's CF, html, or SQL code. All lower case with the first letter of each word after the first one capitalized. I think giving the code a nice consistent look over all is a very good idea. It makes it easier for others to read it and makes it easier to make heads or tails of it at a later time even for the original author. Not to mention the case sensitivity issues on Unix platforms. Any thoughts? Balazs ==^================================================================ This email was sent to: [email protected] EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^================================================================
