> Or you could just use cfmodule. ;-) > ...and accept the performance hit (20ms or so :) ?
Seriously though, there is use for direct calling of other fuseactions. And current <cfmodule> technique is a bit cumbersome (and there IS a slight performance hit). But we still should address the protection of local scope. Oh, wait... I remember reading that variables scope in CF MX is now also implemented as a structure (it wasn't in previous releases). Since Lee's core already requires CF MX because of <cffunction> then protecting local variables is pretty much a non-issue. We just need to Duplicate() the variables scope to internal stack in FB_ struct, then StructClear() variables scope, run the specified fuseaction, again StructClear() the variables scope and Duplicate() it back from the stack in FB_ struct. This way we can automagically protect the variables scope when calling fuseactions with RunAction(). Lee, please-oh-please shoot me your core file, I wanna play with it :) .erki ==^================================================================ This email was sent to: [email protected] EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^================================================================
