Login | Register
My pages Projects Community openCollabNet

Discussions > dev > Re: [propel-dev] roadmap > Reply to message

propel
Reply to message

* = Required fields
* Subject
* Body
Attachments
Send reply to
Topic
Author (directly in email)
Please type the letters in the image above.

Original message

Author =?ISO-8859-1?Q?David_Z=FClke?= <dz@bitxtender.com>
Full name =?ISO-8859-1?Q?David_Z=FClke?= <dz@bitxtender.com>
Date 2006-03-28 16:07:17 PST
Message > Good questions -- and that's why this is a discussion rather than a
> decision. I personally do think that if it is added at all it
> should be
> toggle-able, yes. API docs is a good argument for keeping more
> traditional methods. Bear in mind, though, that the getter/setter
> methods are all doing almost the exact same thing, so I think from a
> readability perspective consolidating that would help. Also, if I
> understand the proposals, you could still always override the
> methods in
> the stub methods, so for the important stuff the API docs would still
> work as expected.

true

> -- I haven't looked over these proposals yet, but I guess in my mind I
> see __call() as a replacement for the _standard_ get*()/set*()
> methods &
> not for the other methods of the class. Others may have other ideas.

agreed