Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: [xml-dev] a useful naming convention

From: "Michael Kay" <mike@--------.--->
To: "'Bryan Rasmussen'" <bry@------.--->,<jim.fuller@--------.--.-->
Date: 8/2/2005 11:48:00 AM
> "In Simonyi's version of 
> Hungarian notation, every
> variable was prefixed with a lower case tag that indicated 
> the kind of thing
> that the variable contained. "

I have always regarded that with horror, but it's a matter of personal
taste.

Names are there to identify objects, not to contain all the properties of
the object. Don't try to pack them with bit-significant meaning; apart from
anything else, you don't want to change the name of something when its
properties change.

The main debate about naming is the scope of uniqueness of a name. Should
the title of a chapter have the same element name as the title of a section?


As far as the internal syntax of a name is concerned, the only important
thing is to try and be consistent: use hyphens or underscores or camelCase,
but not all three interchangeably.

Michael Kay
http://www.saxonica.com/


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent