[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
RE: [xml-dev] Convention versus standard
- From: Len Bullard <len.bullard@uai.com>
- To: Michael Kay <mike@saxonica.com>, 'bryan rasmussen' <rasmussen.bryan@gmail.com>, 'Fraser Goffin' <goffinf@googlemail.com>
- Date: Mon, 21 Jul 2008 08:08:08 -0500
And again if the difference is authority vs/or general consent, without a
metric for general consent, it is simply a convention which does not imply
good or bad.
Fun discussion but we are skirting the essential issue: the means of
explicit documentation for agreement. A set of conventions in no way
implies authoritative agreement. A best practice implies someone or some
group deemed it 'best'. So in that respect, until one has the metric, there
is no useful discrimination of best practice and convention.
len
From: Michael Kay [mailto:mike@saxonica.com]
> It is common practice for programmers to name variables in
> numerous non-helpful ways, it is best practice to have a well
> thought out naming scheme that allows those who maintain code
> to know what a variable is to be used for, hopefully
> achievable by following the coding styles for their languages
> and organizations
My experience is that an intelligent programmer using their own common sense
will usually produce much more helpful variable names than a programmer who
is blindly following rules defined by some corporate style police.
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]