"that's like saying that the manufacturer of a rivet gun should determine airworthiness standards for aircraft assembled with their products."
Fair call but the manufacturer of a rivet gun should give the user of said rivet gun guidelines on how best to use the rivet gun true? Adobe being the manufacturer should be providing guidelines as to the best practise way to use the product and use the language. In the end it is up to the developer to decide what to write and how to structure their code so having a standard of sorts seems kind of useless to me as for one the language and environments are changing so quickly that the so called standard would keep being changed to adapt to the new environments. Adobe should be saying things like (this is an example so don't flame me about it's ) : "When looping over an array the preference is <cfloop array="arr".. over <cfloop from="1" to="#arrayLen(arr)#" because bla bla bla...." and so on. I see this as a standard. The so called "coding standards" documents are more "coding convention" documents that outline an organisations preferred coding style and in my view is not and should not be referred to a general industry coding standard as I see it often referenced as but poorly as an organisational based standard, and even then it isn't a coding standard, it is a coding convention guide. I see the two as very different things. The only reason I am even bring it up is that it was asked by Sean to update it and make it current which I don't really think is his responsibility to do. Sure if you want to use it as a base for developing your own guideline within your own organisation then sure go right a head, but it shouldn't be taken as gospel as each organisations requirements are different and should be treated as such. As for what Toby has mentioned such as "release processes, merging and conflict management procedures etc" these are procedure based things and should not be anywhere near coding standards....imo anyway -----Original Message----- From: Robin Hilliard [mailto:ro...@rocketboots.com.au] Sent: Wednesday, 4 August 2010 2:33 PM To: cfaussie@googlegroups.com Subject: Re: [cfaussie] Re: Coding Standards > If a coding standard for writing ColdFusion should be developed it should be > developed by Adobe, maintained distributed by them also. After all they are > the ones distributing the platform. That argument doesn't work for me Steve - that's like saying that the manufacturer of a rivet gun should determine airworthiness standards for aircraft assembled with their products. Almost all code is written for two audiences - (1) the parser attached to the compiler/interpreter and (2) other developers. Adobe is responsible for the standard of (1) by definition, because they write the parser. Any other standards exist solely to aid comprehension for other developers reading the code. Every coding standard starts as a "how I write code" document. It turns into a standard when a second person takes it up. There can be as many coding standards as there are groups of co-operating developers, and as long as they aid each group in understanding the intent of each-other's code, they're worth having. They're also worth sharing with other groups so that good ideas can spread, and optimal (for purpose) coding standards can evolve to fill their own ecological niche in the standardosphere. Cheers, Robin PS: See you at the Melbourne Flex UG tomorrow night. ROBIN HILLIARD Chief Technology Officer ro...@rocketboots.com.au RocketBoots Pty Ltd Level 11 189 Kent Street Sydney NSW 2001 Australia Phone +61 2 9323 2507 Facsimile +61 2 9323 2501 Mobile +61 418 414 341 www.rocketboots.com.au -- You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to cfaus...@googlegroups.com. To unsubscribe from this group, send email to cfaussie+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en. -- You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to cfaus...@googlegroups.com. To unsubscribe from this group, send email to cfaussie+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en.
