On Thu, Apr 9, 2009 at 1:44 PM, Matthew Woodward <[email protected]>wrote:
> MXUnit--should have thought of this earlier--it won't work because they're > using a method called assert() and OpenBD has a built-in function assert(). We thought about it and decided we like assert and the engine should deal with it better than it does (this goes for all engines not just OpenBD) :) In general even though I am on the team for MXUnit we have not targeted OpenBD. To be frank about it, it is mostly do to the initial reaction from Alan and Andy about the web service support. Bill sort of got turned off by that :-/ > 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 I would bring this up in the CFML advisory commitee as it seems different engines are taking different routes here and I'd like to see the same solution across the board. Without getting into it too much I like the solution from Adobe at this point... Adam --~--~---------~--~----~------------~-------~--~----~ 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 !! -~----------~----~----~----~------~----~------~--~---
