Suggestion for a mixed camelCase & PascalCase notation

Jonathan M Davis jmdavisProg at gmx.com
Sat Jun 1 17:19:24 PDT 2013


On Sunday, June 02, 2013 02:08:15 Joseph Rushton Wakeling wrote:
> On Saturday, 1 June 2013 at 22:16:49 UTC, Jonathan M Davis wrote:
> > The sad thing is that we got hungarian notation due to a
> > misunderstanding. The
> > original idea was actually quite good. This article explains
> > what happened as
> > well as the original idea (which _is_ worth using):
> > 
> > http://www.joelonsoftware.com/articles/Wrong.html
> 
> Interesting read. A question: I'd assume that with modern
> languages it'd be possible to achieve much or all (or more) of
> the safety created by "Apps Hungarian" by using an appropriately
> crafted type system. E.g. to take one example from that article,
> create a SafeString type which is guaranteed to contain properly
> encoded text.

Sure, you could create wrapper types if you wanted to. That's a more 
heavyweight solution, since you have to create new types, but it's also safer, 
because the type system helps you out rather than just the names helping the 
programmer understand the code.

- Jonathan M Davis


More information about the Digitalmars-d mailing list