On Thu, Apr 9, 2009 at 10:44 AM, Matthew Woodward <[email protected]> wrote: > We discussed at one point allowing people to disable specific functions but > that wouldn't happen any time soon--quickest fix for MXUnit I would think is > to do search/replace on assert and change it to doAssert or something along > those lines. I did the same thing for Reactor when I was testing Sava > (they've since moved off of Reactor) and it fixed the issue.
My suggestion - and one I'll try to push through the CFML Advisory Committee at some point - is for CFML engines to allow CFCs to contain methods that are named the same as built-in functions - but not allow UDFs (outside CFCs) to override built-ins. Unqualified calls to private methods in CFCs would need VARIABLES. to disambiguate them but calls to public methods would "just work" (because they are obj.method() already). This is the least impactful change. It allows CFC authors to protect their code from future addition of built-ins - as long as they always use variables.privateFunc() internally. Just an FYI in case the OpenBD team want to start thinking about that... -- Sean A Corfield -- (904) 302-SEAN An Architect's View -- http://corfield.org/ "If you're not annoying somebody, you're not really alive." -- Margaret Atwood --~--~---------~--~----~------------~-------~--~----~ Open BlueDragon Public Mailing List http://groups.google.com/group/openbd?hl=en official site @ http://www.openbluedragon.org/ !! save a network - trim replies before posting !! -~----------~----~----~----~------~----~------~--~---
