Am Samstag, 3. Juni 2006 02:29 schrieb Mattias Gaertner:
> On Fri, 2 Jun 2006 20:21:01 -0400
>
> "Alexandre Leclerc" <[EMAIL PROTECTED]> wrote:
> > 2006/6/2, Burkhard Carstens <[EMAIL PROTECTED]>:
> > > [..]
> > >
> > > > > CORRECT
> > > > > FMyString: string;
> > > > >
> > > > > INCORRECT
> > > > > lpstrMyString: string;
> > > > >
> > > > > The exception to the Hungarian notation rule is in enumerated
> > > > > types.
> > > >
> > > > If other developers agree, we should add this to the wiki page.
> > > > If not, then deviation from this standard should be mentioned.
> > >
> > > For variables this is ok, but for components, I also use the
> > > "btnWhatever" notation. Especially on bigger projects, this helps
> > > a lot.
> > >
> > > Just my 2 cent ..
> >
> > Well, I've the same opinion on this. I agree with the documents and
> > naming convention presented in these documents (especially the
> > Borland one, which I do follow since many years as best as I can).
> > But the addition which is in the old document I posted ([2..4]
> > letters prefix for components) is very usefull for code clearness -
> > it's all about code readability and clarity. When you can actually
> > 'read' the code and need no comments and searching here and there
> > about the nature of the control, this is a good thing.
>
> Why is btnOk more clear/readable than OkButton?
sure,it doesn't matter on a form with two buttons and one label, but I
have some forms containg some dozend control. Now if I want to change a
property of that one button, who's name i cant remenber exactly, but I
now it is a button and it is related to settingn a minimum range for
something, I just enter "btnMin" Ctrl-Space and code-tools let me
choose ..
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
