Off the top of my head - the only case I could make is for the ease of transition between other languages and CF, which I don't think is a small thing.
Almost every programmer I know is comfortable with ECMAScript on SOME level - and I would tend to believe is a 'assumed' standard whenever seeing the word 'script' in a language. I know it came as a surprise to me when I found that cfscript wasn't a ECMAScript. Oh yeah - and it would mean we could write code like: foo = (x++ == (row = y * 2)) ? --y + 4 : (x *= 4 == row ? --row : row++ )); Just for fun ;o) Mark On Sun, 5 Dec 2004 18:52:45 -0800, Sean Corfield <[EMAIL PROTECTED]> wrote: > On Mon, 6 Dec 2004 12:26:45 +1000, Gary Menzel <[EMAIL PROTECTED]> wrote: > > ECMA compliance sounds like a good idea. > > I'd be interested to hear a commercial business argument in favor of > getting Macromedia to spend lots of time and effort on bringing > CFSCRIPT up to ECMAScript compliance as opposed to spending that time > and effort on adding new functionality to ColdFusion. That's a serious > question... > -- > Sean A Corfield -- http://www.corfield.org/ > Team Fusebox -- http://www.fusebox.org/ > Breeze Me! -- http://www.corfield.org/breezeme > > "If you're not annoying somebody, you're not really alive." > -- Margaret Atwood > -- E: [EMAIL PROTECTED] W: www.compoundtheory.com ICQ: 3094740 --- 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/
