Really? I'm sure that I usually get an error. Or at least I certainly do if I return the wrong type for a returntype.
Going to have to test that now.... On 4 July 2011 13:18, Andy Wu <[email protected]> wrote: > I changed the behaviour recently to match ACF due to MXUnit code where > there was a cfreturn despite the return type being void. > > > Matthew Woodward wrote: > >> Personally I would think that if the returntype is void, and the function >> contains cfreturn, it should throw an error. Alan and Andy will have to >> chime in, and I don't know what the behavior is in ACF off the top of my >> head, but it makes logical sense to me that if you declare returntype="void" >> and the function returns something, or even contains a cfreturn tag or >> return statement, an error should be thrown. That way you don't have >> unexpected behavior due to the fact that it's returning an empty string, >> which is what we're seeing here. >> > -- Stephen Moretti Blog : http://nil.checksite.co.uk/ Twitter : http://twitter.com/mr_nil More Twitter : http://twitter.com/CFOverflow -- official tag/function reference: http://openbd.org/manual/ mailing list - http://groups.google.com/group/openbd?hl=en
