I don't see chaining the setFirstName() and setLastName() methods as making
the operation more atomic. If you want atomic, write a new method, called
setName(), which takes two parameters.
You can't do that if you don't own the object! That's my point: if you get an API that has lots of setter/getter methods but you want to program as if the API was less granular, then method chaining is appropriate (of course, that presupposes that whoever wrote the API actually returns this anyway!).
Right or wrong, it's valid, and therefore perfectly acceptable to me, as
long as you don't work on the same project as I do. ; )
Yeah, coz' if you worked on my projects, you'd have to follow my coding guidelines (and I *always* get to set coding guidelines on any projects I'm involved with).
Sean A Corfield -- http://www.corfield.org/blog/
"If you're not annoying somebody, you're not really alive." -- Margaret Atwood
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
