From: Michael DeHaan <michael.dehaan@...>
Date: 2004-10-22T06:17:47+09:00
Subject: Re: CamelCase issues

> > Some more examples:
> >
> >   render_content_on <-> renderContentOn
> >   render_table_header_on <-> renderTableHeaderOn
> >

To add more confusion to this thread ...

A user of this API might have a question.   Does render_content_on
change a value or return the current one, based on whether it has
parameters?  It's hard to tell.

To clean this up, I'd be apt to use attr_reader and attr_writer, while
overriding the render_content= function.

Trivial accessor and mutator methods are not something I'm a fan of,
I'd like to keep field syntax when things are simple.  I mean, we
could write a render_content? kind of query function, but what would
be the point?

Let me know if that's totally evil, I'm new here :)

--MPD