[
Lists Home |
Date Index |
Thread Index
]
The API level is what's important not the language level in my book. For
example, what use would a Java standard be if the only thing standardized was
the language syntax and the java.lang package? So one could claim standards
compliance without even having an implementation of java.io or java.util. In
such situations, the language might as well not be a standard. This is what
happened with ECMAScript and to a lesser extent C++ (or is that a larger
extent?) .
--
THINGS TO DO IF I BECOME AN EVIL OVERLORD #44
I will only employ bounty hunters who work for money. Those who work for the
pleasure of the hunt tend to do dumb things like even the odds to give the
other guy a sporting chance.
----- Original Message -----
From: "Mike Champion" <mc@xegesis.org>
To: <xml-dev@lists.xml.org>
Sent: Friday, January 11, 2002 9:04 AM
Subject: Re: [xml-dev] ECMA Standardizes C#
> 1/11/2002 11:38:19 AM, Sean McGrath <sean.mcgrath@propylon.com> wrote:
>
>
> >Lets hope it is as successful as ECMA 262 at ridding the world of the
scourge
> >of vendor lock-in.
>
> I detect a certain tone of irony here <grin> but don't really know much
> about ECMA 262. Does it not provide a reasonable basis for interoperbility
> (at the language level, not API level) across browsers? Or is the fact
> that I stay as far away as possible from the dark corners of the language
> showing here?
>
>
>
> -----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
>
> The list archives are at http://lists.xml.org/archives/xml-dev/
>
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://lists.xml.org/ob/adm.pl>
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
|
