On 2017-02-16 12:52, Gene Wirchenko wrote:
but this use of the Scope Resolution operator allowed me to jump 2 levels in the OOP hierarchy, Gene. DODEFAULT(x,y) would have ran the method 1 above, and that's not what I needed. Like I said, at first, it didn't seem very OOP to me, but revisiting it, I suppose it is.

     It is not very OOP.  I do not know enough about your case to
judge whether I would do that, too, but I rather doubt it.  It has the
smell of a kludge, but sometimes, kludges are necessary.



That's EXACTLY what I thought when I saw it over a decade ago. Looks very non-OOP and kludgey. But you're right about sometimes it's necessary, and I can honestly say this implementation I just made saved a lot of coding, and it wasn't too obfuscated.

_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Reply via email to