Or ActionScript. Surely it is good business sense to ensure that when you include a "script" option in a product that it is compliant with current standards. This ensures a larger base of users can adapt quickly to your product.
I am fully aware, Sean, that you are not a fan of <cfscript> - but that doesn't mean that there aren't a lot of us out there that aren't extensive users of it. I am not a Macromedia shareholder - so I dont care too much for the Business Case side of it (i.e. how can we make money from this) - but "standards" are a good thing. If <cfscript> were ECMA compliance then ONE standard for ActionScript, Javascript and <cfscript> could be maintained by an organisation. That has to impact the MM bottom-line somehow - hopefully in increased sales because of a "compliance" stamp against <cfscript>. Regards, Gary Menzel On Mon, 6 Dec 2004 13:57:23 +1100, Darryl Lyons <[EMAIL PROTECTED]> wrote: > I guess the best point I can make about this is consistency.. > ActionScript, apparently (I'm not a big ActionScript person), is ECMA > compliant. Why shouldn't CFSCRIPT be compliant? > > I can't count how many times I've typed: > > for (i=1; i <= arraylen()... ) > > When switching between JavaScript and CFSCRIPT. > > Darryl > > > > --- > You are currently subscribed to cfaussie as: [EMAIL PROTECTED] > To unsubscribe send a blank email to [EMAIL PROTECTED] > Aussie Macromedia Developers: http://lists.daemon.com.au/ > --- You are currently subscribed to cfaussie as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
