Bruyn, Bill-p6141c wrote:
Yeah, that's about what I'd come up with too (unless I'm
misunderstanding you, this sounds like my option 1.)
That'll work I guess, but I was hoping not to have to muck up all my
method names (e.g., getWhatwouldordinarilybeacamelcasename(),
getWHATWOULDORDINARILYBEACAMELCASENAME()) if there's another way.
Thanks,
Bill
Yes, I suppose it just your option one. I was thinking you could adopt
a convention to convert field names to camel-case property names (eg. an
underscore in a field name converts to a new word in a camelcase
property name), but that's a horrible hack. On second thought I'd
reluctantly use your option 2.
Actually, I'd argue against the requirement unless it's needed to
interface to a legacy application.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
