On Nov 28, 7:07 pm, "Mislav Marohnić" <[EMAIL PROTECTED]>
wrote:
> On Nov 28, 2007 4:54 PM, Viktor Kojouharov <[EMAIL PROTECTED]> wrote:
>
>
>
> > If a function can take an argument, and you'd expect to get a boolean in
> > some cases, but an object in others, what would you do?
>
> In my opinion, a function that returns booleans in some cases and objects in
> others is a poor designed function.
>
> I must agree with Andrew on both his points.
Backwards compatibility. And yes, that in itself means it's poorly
designed, but what you gonna do. And usually the problem is what it
takes, rather than what it returns.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Prototype: Core" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/prototype-core?hl=en
-~----------~----~----~----~------~----~------~--~---
