|
Personally, I agree with the convention team. Having a name that is too long is just as hard to read (within the code) as a name that is too short. The problem I have with longer names is that I often will run out of space in the extended factor 2 or other specifications where they are used. I think a good meaningful name can be created within the 15 char limit. Your example of wwASUFM is one that is too short. (7 Chars) Mike rpg400-l-bounces@xxxxxxxxxxxx wrote on 12/28/2004 05:24:52 AM: > > Hi group, > > I'm having an argument with the team that choose our shop's coding > style conventions. I'd like to have your opinion on the subject. > > The heart of the matter lies in this kind of constant declaration: > > DwwAppStateUpdFailMsg... > D C '...' > > The convention team says this name is too long. They want everybody > to keep their names within the 15-character limit -- indeed, 13 > meaningful characters after you add the two-character prefix. > > I think this name is already on the short side. Using so many abbreviations won't make newcomers' work any easier. > Still, isn't it more readable than wwASUFM for instance?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.