On Apr 7, 2008, at 10:36 AM, Mike Schrag wrote:
I'd expect the instanceof check will be much more efficient than
catching an exception.
By far ...
From an OO design point of view, I'd add a billsOfMaterial() method
to the Part class that simply returns NSArray.emptyArray.
ManufacturedPart will then override this to return the correct
result for a ManufacturedPart.
Ew gross ...
By far one of my favorite technical arguments.
If it's not an attribute of all Parts, then from an OO design
standpoint it shouldn't be on Part. I agree if your argument is
based on "the convenience of being able to call billsOfMaterial on
the entire array," though.
Yeah, I'm getting the impression that there's no really "ungross" OO
way to do this. I think this and instanceOf are equally "gross"
because if I add other classes that have a billsOfMaterial()
relationship, then I'd have to remember to come here and add it to the
list of things instanceOf checks.
I think I'll go with adding the billsOfMaterial() method to Part
because then I can use this same logic in more places without having
to write the instanceOf check every time.
Still seems not right, but it's easier. =:-0
Dave
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
