This is the kid of thing that makes me wish that new tags and functions 
introduced by competing engines were namespaced or prefixed. I've been 
working with OpenBD for a few years and migrated all of our ACF (v5-7) 
sites over without too much trouble. But now with engine-specific 
enhancements, I've got vendor lock if I make use of those enhancements. 
Worse is when two engines have a similar function with different names and 
slightly different functionality (e.g. OpenBD writeDump vs Railo dump). So 
if I find that I have a need for using another engine (e.g. Framework 
compatibility reasons) then I have to stop thinking about it just as CFML. 

On Sunday, April 1, 2012 6:42:17 AM UTC-4, Alex Skinner wrote:
>
> No the issue is that OpenBluedragon has a built in function called 
> render() that the other two engines don't have.
>
> when you're calling render() its calling the built in function which takes 
> one argument the string you want to runtime execute.
>
> but the fix is correct :)
>
> Alex
>  

-- 
online documentation: http://openbd.org/manual/
   google+ hints/tips: https://plus.google.com/115990347459711259462
     http://groups.google.com/group/openbd?hl=en

Reply via email to