blob: 07b71ebc072f9f6ec8c3e1d584d8071a7685eb29 [file] [log] [blame]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<link href="../book.css" rel="STYLESHEET" CHARSET="ISO-8859-1" TYPE="text/css">
<link rel="stylesheet" type="text/css" href="../content/PLUGINS_ROOT/PRODUCT_PLUGIN/book.css">
<meta content="Copyright (c) 2000, 2010 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v2.0 which accompanies this distribution, and is available at Contributors: IBM Corporation - initial API and implementation" name="copyright">
Most implementations of JavaScript are loosely based on a core script standard called ECMA. Beyond the
standard there is a common set of non-standard language constructs supported by most implementations and
other functions/constructs that are only supported by a subset of the JavaScript implementations.<br><br>
Quite a few public JavaScript toolkits as well as the general popular usage of JavaScript exploit many of these
non-standard language aspects making a pure modeling of the language difficult (if not impossible). Our solution
is a complex inference engine that analyzes your JavaScript to help build an accurate model. Unfortunately the
inference isn't always perfect. For these reasons some JavaScript class inferences may be imperfect and mark
fields/methods/types as an error that really aren't. Of course we are working on this and plan to work with
more edge cases as we progress.