> > moreover it makes the code unreadable. > In what way is the code I cited below unreadable?
If the position was "it's an edge case and we've got better things to do so we're not implementing it", that'd be fine. And this would be a good reason. However applying subjective personal opinion like "ooh, I don't like that" or "I'd personally never use that" or "it's ugly" should have no part in the decision-making process of whether to implement something missing from OBD's CFML implementation. -- Adam > On Jul 9, 7:03 am, Adam Cameron <[email protected]> wrote: > > G'day > > Another OBD/CF incompat... > > > > I have this code: > > > <cfset bExpr1 = true> <cfset bExpr2 = true> <cfset bExpr3 = true> <cfif bExpr1 <!--- explanation of bExpr1 ---> AND bExpr2 <!--- explanation of bExpr2 ---> AND bExpr3 <!--- explanation of bExpr3 ---> > Foo </cfif> -- Open BlueDragon Public Mailing List http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon online manual: http://www.openbluedragon.org/manual/ mailing list - http://groups.google.com/group/openbd?hl=en
