🚀 go-pugleaf

"David Clegg" wrote
>
> I use one based on the MS guidelines, but which deviates in areas where
> I thought it made sense to do so in order to provide better
> interoperability with languages such as Delphi.

What you remark on in your blog all generally falls into an area where MS's
guidance doesn't seem to be carrying the day: the lack of scope marking on
private fields. Or what might be termed an RPN of scope. Seems to me that m,
_, or m_ are doing pretty well in the general press.

"Do not expose a property with the same name as its underlying type."

Rock and a hard place on this one. Delphi is easy because TFont --> property
Font, but there being no type marker in C# except the casing, the
declaration of a property (arguably a public instance reference) should
really be the type name in camel case--except that that's probably what the
internal field is. in the translation from class/type (PascalCase) to
property to field (camelCase), the middle term has no where to go.

bobD