Preferred naming?

[howa]

Which one you like?

1.

<CompanyReport>


2.

<companyReport>

3.

<company_report>

4.

<company-report>

 

[Peter Flynn]

Which one you like?

1. <CompanyReport>

2. <companyReport>

3. <company_report>

4. <company-report>

Unless there are significant differences in structure between this kind
of report and all the others, <report type="company">

///Peter

 

[howa]

Well, this is just an example, what I concern is the naming is a word
is combined of two another words.

 

[Peter Flynn]

Well, this is just an example, what I concern is the naming is a word
is combined of two another words.

Yes, but what you ought to be concerned with is the meaning and the
implications, rather than whether it looks prettier as lowercase,
camelCase, or something else.

lowercase is for documentheads, webheads, and unixheads
TitleCase is for documentheads and older programmers
camelCase is for C++ and Java programmers
under_score is for documentheads and SGML hackers
hyphens are for old mainframe heads and modern webheads



///Peter

 

[burkley]

Yes, but what you ought to be concerned with is the meaning and the
implications, rather than whether it looks prettier as lowercase,
camelCase, or something else.

lowercase is for documentheads, webheads, and unixheads
TitleCase is for documentheads and older programmers
camelCase is for C++ and Java programmers
under_score is for documentheads and SGML hackers

Don't forget under_score for old school C programmers

 

[Joe Kesselman]

Which one you like?

The most important thing is that the naming convention be consistent
with other names in the same documents so people working with those
documents know what to expect.