Webmaster Forum / HTML, CSS, Scripts / JavaScript / February 2007

jackchang1@gmail.com said the following on 2/27/2007 9:24 PM:

Because Javascript isn't AI. How would it know whether you meant
function or functiom(); or were trying to create a variable followed by
a function call? If you want syntax checking, try JSLint:

<URL: http://www.jslint.com/lint.html>

On Feb 28, 2:24 am, "jackcha...@gmail.com" wrote:

Javascript did tell you directly, it just told you about its problem
not yours. Its problem is that - functiom - is a valid (but pointless)
Expression, and so a valid ExpressionStatement, and - method1() - is
also a valid Expression (a Call Expression, and so a valid
ExpressionStatement) and so also a valid expression statement, but if
you omit the optional semicolon form the end of the first
ExpressionStatement then javascript can only automatically insert it
for you if you put a line terminator before then following
ExpressionStatement. As there is no line terminator javascript is
expecting to see that semicolon, and when it is not seen it tells you
that it was expecting it, which seems reasonable.

If you want to avoid not noticing mis-typed keywords you should try
being smarter yourself and get yourself a syntax-highlighting editor
that colors javascript keywords distinctly differently from
Identifiers.

Richard.

In comp.lang.javascript message <1172629489.606763.214350@a75g2000cwd.go
oglegroups.com>, Tue, 27 Feb 2007 18:24:49, "jackchang1@gmail.com"
<jackchang1@gmail.com> posted:

Already explained.  If there are some typoes that you make frequently
and/or find hard to see, you can process your pages with a suitable
search/ask/replace tool.

I have a batch file (try.bat; "try" is easy to type) which does various
checks (including with W3's TIDY) on any *.htm file changed since it was
last run.  Part of it offers the following left-to-right word
substitutions : anf = and, ar = at, hoe = how, 8061 = 8601, wnen = when.
Of course, one then must avoid using those "words".

It's a good idea to read the newsgroup and its FAQ.  See below.