Interesting that you picked only that argument. :-)
That example is more than just semi-colons, and is a very small sampling of
how and why cfscript in Railo beats the hell out of cfscript in ACF. You
know it as well as I do, although I can appreciate your reasoning for
needing to defend ACF. :-)
<cfscript>
foo = myService[ myMethod ]( argumentCollection: arguments )
</cfscript>
There's another perfect example of how cfscript in ACF blows. Something
that should have (and could have) been supported for years, but Adobe
intentionally chose not to support it.
Again, I appreciate your need to defend ACF. And your right to do so. I,
too, was once a staunch supporter of ACF. Things change. :-)
On Mon, Aug 20, 2012 at 8:41 AM, Raymond Camden <[email protected]>wrote:
>
> On Mon, Aug 20, 2012 at 8:23 AM, Matt Quackenbush <[email protected]>
> wrote:
> > Railo's cfscript implementation beats the hell out of ACF's, and has for
> > years.
> >
> > Go run this on ACF. Then install Railo and give it a whirl. :-)
> >
> > <cfscript>
> > foo = {
> > x:'yay!',
> > y:'hooray!',
> > z:'rock on, Railo!'
> > }
> > writeDump( foo )
> > </cfscript>
>
> Um - it works fine in ColdFusion if you add semicolons. Are you
> seriously arguing Railo beats the "hell" out of ColdFusion because you
> can leave off semicolons?
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Order the Adobe Coldfusion Anthology now!
http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion
Archive:
http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:352220
Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
