Hey Gary I have no experience writing language parsers so I could be way off the mark here, but with all due respect I think ECMA compliance is not just a matter of making something that exists "standard" or standards compliant.
"A conforming implementation of ECMAScript must provide and support all the types, values, objects, properties, functions, and program syntax and semantics described in this specification." My reading of this is that there is a heap of stuff in ECMAScript that does not exist in CF at all or directly conflicts with the way things are done in CF. The Null type, support for finally in try/catch blocks, date handling, arrays starting at 0, etc.. I'm all for cfscript getting ECMA style operators like ++, <, > and so on, but I think that this is worlds apart from ECMA compliance. -- Mark Stanton Gruden Pty Ltd http://www.gruden.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to cfaussie@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie -~----------~----~----~----~------~----~------~--~---
