From: Michael Neumann Date: 2004-10-22T06:34:32+09:00 Subject: Re: CamelCase issues On Fri, Oct 22, 2004 at 06:17:47AM +0900, Michael DeHaan wrote: > > > 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. def render_content_on(renderer) renderer << "..." end It renders content on a "canvas" (in GUI-speak if you like). It always takes one parameter. > 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 :) I don't really understand your last sentences... Regards, Michael