Re: Javascript 1.3
On Fri, 16 Apr 2004 13:07:38 -0500, "Matt Kruse"
<newsgroups@mat tkruse.com> wrote:
[color=blue]
>Same think with try/catch, or any other keyword additions and language
>changes in different versions.
>If you're developing for an internet audience, you can't use any of these
>new features, because there is no way (that I've found) to degrade nicely,
>without relying on language="Javas cript1.3", etc.[/color]
but that's never been a reliable solution anyway, it was ignored by
too many of the old browsers - the ones we need to protect.
[color=blue]
>Causing a syntax error while determining whether or not an operator is
>supported (as another poster suggested) isn't really a good solution, IMO.[/color]
Absolutely, that's definately unacceptable, I wouldn't use ===, it's
one of things I disagree with jslint on.
Jim.
--
comp.lang.javas cript FAQ - http://jibbering.com/faq/
On Fri, 16 Apr 2004 13:07:38 -0500, "Matt Kruse"
<newsgroups@mat tkruse.com> wrote:
[color=blue]
>Same think with try/catch, or any other keyword additions and language
>changes in different versions.
>If you're developing for an internet audience, you can't use any of these
>new features, because there is no way (that I've found) to degrade nicely,
>without relying on language="Javas cript1.3", etc.[/color]
but that's never been a reliable solution anyway, it was ignored by
too many of the old browsers - the ones we need to protect.
[color=blue]
>Causing a syntax error while determining whether or not an operator is
>supported (as another poster suggested) isn't really a good solution, IMO.[/color]
Absolutely, that's definately unacceptable, I wouldn't use ===, it's
one of things I disagree with jslint on.
Jim.
--
comp.lang.javas cript FAQ - http://jibbering.com/faq/
Comment