Re: why leading underscores removed ?

> I adopted the leading underscores style a long time ago, when using
> Eclipse.  It helped with completion (Eclipse was very slow at this,
> back in the day).
>
> However, seeing that in code has "scared" people, since its unusual.
>
> Next: Hibernate is not as flexible as Tapestry, and leading
> underscores confuse it (when you apply annotations directly to
> fields).  I don't want some of my code following one convention, some
> following another.
>
> Further, I'm using some some Groovy now, maybe some Scala in the
> future.  And often, I'm using final variables from inner classes. The
> underscores become increasingly chancy there.
>
> So I don't want underscores in the tutorials and examples, and I want
> to be consistent.
>
> Its not a big deal, lots of meaningless changes ... to
> implementations. No backwards compatibility issues. Underscores will
> continue to be allowed (and stripped out as necessary).  I'll leave a
> number of underscored fields in the integration test suite.
>
>
>
>
>
>
> On Wed, May 7, 2008 at 10:32 AM, Sven Homburg <homburgs@...>
> wrote:
> > hi howard,
> >
> >  what is the reason removing the variables leading underscores?
> >
> >
> >  --
> >  with regards
> >  Sven Homburg
> >  http://tapestry5-components.googlecode.com
> >
>
>
>
> --
> Howard M. Lewis Ship
>
> Creator Apache Tapestry and Apache HiveMind
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>