Revision as of 03:18, 25 July 2011 edit QuentinUK (talk \| contribs) Extended confirmed users 1,559 edits →Unlike C, whitespace in JavaScript source can directly impact semantics. ← Previous edit		Revision as of 03:27, 25 July 2011 edit undo QuentinUK (talk \| contribs) Extended confirmed users 1,559 edits →Some of the primitive data types also provide a set of named values that represent the extents of the type boundaries. These named values are described within the appropriate sections below. Next edit →
Line 353: :Number.MIN_VALUE and Number.MAX_VALUE come to mind: the global properties Infinity and NaN (same as Number.POSITIVE_INFINITY and Number.NaN, there's also Number.NEGATIVE_INFINITY) are a bit philosophical... they're ''special'' values with particular results specified for comparisons/casts/calculations. (I think true, false, and null are keywords as opposed global properties). I would definitely remove the generalization.—[[User talk:Machine Elf 1735\|<span style="text-shadow:#00FADE 0.05em 0.05em 0.07em;white-space: nowrap;font-family: Fraktur, Mathematica6, Georgia, sans-serif">Machine Elf <sup style="font-size:75%;font-family: Georgia, sans-serif">1735</sup></span>]] 01:22, 24 July 2011 (UTC) ::These are not mentioned so the initial statement is misleading. Also there is a range of numbers between Number.MAX_VALUE and Number.POSITIVE_INFINITY, "so boundaries" is also misleading. [[User:QuentinUK\|QuentinUK]] ([[User talk:QuentinUK\|talk]]) 03:27, 25 July 2011 (UTC) == Strings ==

Talk:JavaScript syntax: Difference between revisions