Talk:JavaScript syntax - Revision history

Z. Patterson at 23:27, 20 April 2025

2025-04-20T23:27:57Z

← Previous revision		Revision as of 23:27, 20 April 2025
Line 4:		Line 4:
	{{WikiProject JavaScript\|importance=Top}}		{{WikiProject JavaScript\|importance=Top}}
	}}		}}
			{{American English}}
	{{Backwardscopy		{{Backwardscopy
	\|author = Miller, F. P., Vandome, A. F., & McBrewster, J.		\|author = Miller, F. P., Vandome, A. F., & McBrewster, J.

Cewbot: Reminder of an inactive anchor: backquote

2024-02-21T21:31:23Z

Reminder of an inactive anchor: backquote

← Previous revision		Revision as of 21:31, 21 February 2024
Line 11:		Line 11:
	\|comments = {{OCLC\|721316846}}, {{ISBN\|9786130097844}}.		\|comments = {{OCLC\|721316846}}, {{ISBN\|9786130097844}}.
	\|bot=LivingBot		\|bot=LivingBot
			}}
			{{Broken anchors\|links=
			* <nowiki>[[Grave accent#Use in programming\|backquote]]</nowiki> The anchor (Use in programming) [[Special:Diff/1083439356\|has been deleted]]. <!-- {"title":"Use in programming","appear":null,"disappear":{"revid":1083439356,"parentid":1081031463,"timestamp":"2022-04-18T20:37:32Z","removed_section_titles":["As surrogate of apostrophe or (opening) single quote","CITEREFKuhn2001","CITEREF2019","CITEREFEggert2012","Technical notes","ASCII grave","Games","Use in programming","CITEREFOdersky2011"],"added_section_titles":["Unicode"]}} -->
	}}		}}

Cewbot: Maintain {{WPBS}} and vital articles: 2 WikiProject templates. Create {{WPBS}}. Keep majority rating "C" in {{WPBS}}. Remove 2 same ratings as {{WPBS}} in {{WikiProject Computing}}, {{WikiProject JavaScript}}.

2024-02-04T04:28:04Z

Maintain {{WPBS}} and vital articles: 2 WikiProject templates. Create {{WPBS}}. Keep majority rating "C" in {{WPBS}}. Remove 2 same ratings as {{WPBS}} in {{WikiProject Computing}}, {{WikiProject JavaScript}}.

← Previous revision		Revision as of 04:28, 4 February 2024
Line 1:		Line 1:
		⚫	{{Talk header}}
⚫	{{WikiProject Computing \|importance=Mid ~~\|class=C~~ \|software=y \|software-importance=Mid}}
	{{WikiProject ~~JavaScript~~\|class=C\|~~importance=Top}}~~		{{WikiProject banner shell\|class=C\|
		⚫	{{WikiProject Computing \|importance=Mid \|software=y \|software-importance=Mid}}
⚫	{{Talk header}}~~{{Backwardscopy~~
			{{WikiProject JavaScript\|importance=Top}}
			}}
			{{Backwardscopy
	\|author = Miller, F. P., Vandome, A. F., & McBrewster, J.		\|author = Miller, F. P., Vandome, A. F., & McBrewster, J.
	\|year = 2010		\|year = 2010

Harryboyles: removing redundant parameters in {{WikiProject JavaScript}}

2023-06-04T05:33:23Z

removing redundant parameters in {{WikiProject JavaScript}}

← Previous revision		Revision as of 05:33, 4 June 2023
Line 1:		Line 1:
	{{WikiProject Computing \|importance=Mid \|class=C \|software=y \|software-importance=Mid}}		{{WikiProject Computing \|importance=Mid \|class=C \|software=y \|software-importance=Mid}}
	{{WikiProject JavaScript\|class=C\|importance=Top~~\|imortance=~~}}		{{WikiProject JavaScript\|class=C\|importance=Top}}
	{{Talk header}}{{Backwardscopy		{{Talk header}}{{Backwardscopy
	\|author = Miller, F. P., Vandome, A. F., & McBrewster, J.		\|author = Miller, F. P., Vandome, A. F., & McBrewster, J.

87.191.37.170: /* Inaccuracy (needs citation) */ Reply

2022-12-09T07:26:27Z

Inaccuracy (needs citation): Reply

← Previous revision		Revision as of 07:26, 9 December 2022
Line 12:		Line 12:
	== Inaccuracy (needs citation) ==		== Inaccuracy (needs citation) ==
	The following statement: "'''else statements must be cuddled (i.e. "} else {" , all on the same line), or else some browsers may not parse them correctly.'''" found in section 5.1 is incorrect. I have been programming in javascript for 4 years, and have never used that programming style. I have yet to notice any browser incompatibilities. If this statement is true, please provide a citation. - [[User:Kickboy\|Kickboy]] 04:07, 24 August 2006 (UTC)		The following statement: "'''else statements must be cuddled (i.e. "} else {" , all on the same line), or else some browsers may not parse them correctly.'''" found in section 5.1 is incorrect. I have been programming in javascript for 4 years, and have never used that programming style. I have yet to notice any browser incompatibilities. If this statement is true, please provide a citation. - [[User:Kickboy\|Kickboy]] 04:07, 24 August 2006 (UTC)

			:The statement is not present anymore.
			:Can we delete this block from 2006? [[Special:Contributions/87.191.37.170\|87.191.37.170]] ([[User talk:87.191.37.170\|talk]]) 07:26, 9 December 2022 (UTC)

	== Inheritance without prototyping, etc. ==		== Inheritance without prototyping, etc. ==

Qwerfjkl: /* Module syntax */ edit opening comment (CD)

2021-08-05T12:38:30Z

Module syntax: edit opening comment (CD)

← Previous revision		Revision as of 12:38, 5 August 2021
Line 496:		Line 496:

	== Module syntax ==		== Module syntax ==
	Module syntax which is the most basic thing of every JS interpreter is missing. I suggest to make section on how module system works per different implementations like browser/server(e.g. Google Chrome/Node.js). I suggest to avoid making it bloated as to address issue pointed out by {{re\|Elias}}. <span style="font-size: small" >[[User:Alexander_Davronov\|<span style='color:#a8a8a8'>AXO</span><span style="color:#000">NOV</span>]] [[User talk:Alexander_Davronov\|(talk)]] [[Special:Contributions/Alexander_Davronov\|⚑]]</span> 08:35, 13 October 2020 (UTC)		Module syntax which is the most basic thing of every JS interpreter is missing. I suggest to make section on how module system works per different implementations like browser/server(e.g. Google Chrome/Node.js). I suggest to avoid making it bloated as to address issue pointed out by {{u\|Elias}}. <span style="font-size: small" >[[User:Alexander_Davronov\|<span style='color:#a8a8a8'>AXO</span><span style="color:#000">NOV</span>]] [[User talk:Alexander_Davronov\|(talk)]] [[Special:Contributions/Alexander_Davronov\|⚑]]</span> 08:35, 13 October 2020 (UTC)

Qwerfjkl: Assessment (C): JavaScript (Top) (Rater)

2021-08-05T11:23:51Z

Assessment (C): JavaScript (Top) (Rater)

← Previous revision		Revision as of 11:23, 5 August 2021
Line 1:		Line 1:
	{{WikiProject Computing \|importance=Mid \|class=C \|software=y \|software-importance=Mid}}		{{WikiProject Computing \|importance=Mid \|class=C \|software=y \|software-importance=Mid}}
		⚫	{{WikiProject JavaScript\|class=C\|importance=Top\|imortance=}}
	{{Talk header}}		{{Talk header}}{{Backwardscopy
⚫	{{WikiProject JavaScript\|class=\|imortance=}}
	{{Backwardscopy
	\|author = Miller, F. P., Vandome, A. F., & McBrewster, J.		\|author = Miller, F. P., Vandome, A. F., & McBrewster, J.
	\|year = 2010		\|year = 2010

Alexander Davronov: /* This is not the JavaScript syntax is a very long description of the language */

2020-10-13T08:35:35Z

This is not the JavaScript syntax is a very long description of the language

← Previous revision		Revision as of 08:35, 13 October 2020
Line 493:		Line 493:
	The source of information can be the standard manual of the language if it exist, please so don't expect hundreds of references.		The source of information can be the standard manual of the language if it exist, please so don't expect hundreds of references.
	Just a list of manuals describing the evolution of the language, because some constructs appeared from the first version, others in later versions. It would be ridiculous to tag such article urging for more references. It is a simple task for an experienced JavaScript programmer with some formal education in IT. [[User:Elias\|Elias]] ([[User talk:Elias\|talk]]) 06:56, 25 December 2019 (UTC)		Just a list of manuals describing the evolution of the language, because some constructs appeared from the first version, others in later versions. It would be ridiculous to tag such article urging for more references. It is a simple task for an experienced JavaScript programmer with some formal education in IT. [[User:Elias\|Elias]] ([[User talk:Elias\|talk]]) 06:56, 25 December 2019 (UTC)
			: {{re\|Elias}}. Thumbing up. I agree the article must be shortened. I also suggest to move examples to a separate one.
			: {{tq\|i=1\|[...] The article may also include a semantic description [..] }} It would be disastrous to the article as specs contain a lot (I mean A LOT) of elaborated [[Interface description language\|IDL]] definitions for very simple language constructs. I stand for providing simple examples avoiding making article overly academic/specific. <span style="font-size: small" >[[User:Alexander_Davronov\|<span style='color:#a8a8a8'>AXO</span><span style="color:#000">NOV</span>]] [[User talk:Alexander_Davronov\|(talk)]] [[Special:Contributions/Alexander_Davronov\|⚑]]</span> 08:35, 13 October 2020 (UTC)

			== Module syntax ==
			Module syntax which is the most basic thing of every JS interpreter is missing. I suggest to make section on how module system works per different implementations like browser/server(e.g. Google Chrome/Node.js). I suggest to avoid making it bloated as to address issue pointed out by {{re\|Elias}}. <span style="font-size: small" >[[User:Alexander_Davronov\|<span style='color:#a8a8a8'>AXO</span><span style="color:#000">NOV</span>]] [[User talk:Alexander_Davronov\|(talk)]] [[Special:Contributions/Alexander_Davronov\|⚑]]</span> 08:35, 13 October 2020 (UTC)

DannyS712 bot: Task 70: Update syntaxhighlight tags - remove use of deprecated tags

2020-05-11T18:45:23Z

Task 70: Update syntaxhighlight tags - remove use of deprecated <source> tags

← Previous revision		Revision as of 18:45, 11 May 2020
Line 108:		Line 108:
	Should it not be explained that the following:		Should it not be explained that the following:

	<~~source~~ lang="JavaScript">		<syntaxhighlight lang="JavaScript">
	if(x==1){		if(x==1){
	something()		something()
Line 115:		Line 115:
	somethingelse();		somethingelse();
	}		}
			</syntaxhighlight>
	</source>
	the else if works like a shorthand if (without {})		the else if works like a shorthand if (without {})

	<~~source~~ lang="JavaScript">		<syntaxhighlight lang="JavaScript">
	if(x==1)		if(x==1)
	do something here		do something here
Line 131:		Line 131:
	}		}
	}		}
			</syntaxhighlight>
	</source>
	Sorry if that didn't make sense, I find it hard to explain.		Sorry if that didn't make sense, I find it hard to explain.

Line 145:		Line 145:
	== For loop: end-condition? ==		== For loop: end-condition? ==

	<~~source~~ lang="JavaScript">		<syntaxhighlight lang="JavaScript">
	for (initial;end-condition;loop statement) {		for (initial;end-condition;loop statement) {
	/*		/*
Line 153:		Line 153:
	*/		*/
	}		}
			</syntaxhighlight>
	</source>

	The condition should be called ''while-condition'', or just ''condition'', but never ''end-condition''. As in every C-like language, the for{} loop cycles '''while''' the condition is satisfied. --[[User:Comocomocomocomo\|Como]] ([[User talk:Comocomocomocomo\|talk]]) 14:28, 23 October 2008 (UTC)		The condition should be called ''while-condition'', or just ''condition'', but never ''end-condition''. As in every C-like language, the for{} loop cycles '''while''' the condition is satisfied. --[[User:Comocomocomocomo\|Como]] ([[User talk:Comocomocomocomo\|talk]]) 14:28, 23 October 2008 (UTC)
Line 208:		Line 208:
	The code could be changed to also illustrate the ternary operator <tt>? :</tt> :		The code could be changed to also illustrate the ternary operator <tt>? :</tt> :

	<~~source~~ lang="JavaScript">		<syntaxhighlight lang="JavaScript">
	return diff > 0 ? gcd(segmentB, diff) : gcd(segmentA, -diff)		return diff > 0 ? gcd(segmentB, diff) : gcd(segmentA, -diff)
			</syntaxhighlight>
	</source>

	Since the code might be copied, it would be well to change it, after testing, to the more efficient method, in which the second argument to the internal <tt>gcd</tt> is either <tt>A mod B</tt> or <tt>B mod A</tt>, which is approximately equally easy to read; or to the wondrous non-recursive form :		Since the code might be copied, it would be well to change it, after testing, to the more efficient method, in which the second argument to the internal <tt>gcd</tt> is either <tt>A mod B</tt> or <tt>B mod A</tt>, which is approximately equally easy to read; or to the wondrous non-recursive form :

	<~~source~~ lang="JavaScript">		<syntaxhighlight lang="JavaScript">
	function GCD(U, V) { // or HCF		function GCD(U, V) { // or HCF
	while (true) {		while (true) {
	if (!(U %= V)) return V		if (!(U %= V)) return V
	if (!(V %= U)) return U } }		if (!(V %= U)) return U } }
			</syntaxhighlight>
	</source>

	And, for the same reason, the alternative acronym HCF should be included. [[Special:Contributions/82.163.24.100\|82.163.24.100]] ([[User talk:82.163.24.100\|talk]]) 20:01, 24 July 2009 (UTC)		And, for the same reason, the alternative acronym HCF should be included. [[Special:Contributions/82.163.24.100\|82.163.24.100]] ([[User talk:82.163.24.100\|talk]]) 20:01, 24 July 2009 (UTC)
Line 268:		Line 268:

	<div style="font-size:75%;line-height:150%;margin-left:2.5em;padding-bottom:1.5em;">		<div style="font-size:75%;line-height:150%;margin-left:2.5em;padding-bottom:1.5em;">
	<~~source~~ lang="JavaScript">		<syntaxhighlight lang="JavaScript">
	// Automatic type coercion		// Automatic type coercion
	//Boolean operands will be converted to a number, if possible, or to a string (if the other is a string)		//Boolean operands will be converted to a number, if possible, or to a string (if the other is a string)
Line 286:		Line 286:
	alert(true === 1); // false		alert(true === 1); // false
	alert(true === "1"); // false		alert(true === "1"); // false
			</syntaxhighlight>
	</source>

	Examples with "falsy" and "truthy" values.		Examples with "falsy" and "truthy" values.

	<~~source~~ lang="JavaScript">alert(3?true:false); // true		<syntaxhighlight lang="JavaScript">alert(3?true:false); // true
	alert(true == 3); // false		alert(true == 3); // false
	// 3 is logically true(known as "truthy"), as are all non-0 non-nan numbers. However, it is not "true", even with type coercion.		// 3 is logically true(known as "truthy"), as are all non-0 non-nan numbers. However, it is not "true", even with type coercion.
Line 298:		Line 298:

	alert(false == +'NaN'); // false (shorthand for getting a NaN value)		alert(false == +'NaN'); // false (shorthand for getting a NaN value)
			</syntaxhighlight>
	</source>
	</div>		</div>
	:I think some of the permutations could potentially be eliminated but it's necessary to show, for example, that neither <code>true==2</code> nor <code>false==2</code> behave the way one might expect.		:I think some of the permutations could potentially be eliminated but it's necessary to show, for example, that neither <code>true==2</code> nor <code>false==2</code> behave the way one might expect.
Line 333:		Line 333:
	== Function example code misleading ==		== Function example code misleading ==

	<~~source~~ lang="JavaScript">		<syntaxhighlight lang="JavaScript">
	var obj1 = {a : 1};		var obj1 = {a : 1};
	var obj2 = {b : 2};		var obj2 = {b : 2};
Line 342:		Line 342:
	foo(obj1, 3); // Does not affect obj1 at all. 3 is additional parameter		foo(obj1, 3); // Does not affect obj1 at all. 3 is additional parameter
	alert(obj1.a + " " + obj2.b); // writes 1 3		alert(obj1.a + " " + obj2.b); // writes 1 3
			</syntaxhighlight>
	</source>

	This is misleading because obj1 can be modified by the function. It is quite odd (in an explanation) to pass a parameter to a function and then ignore it.		This is misleading because obj1 can be modified by the function. It is quite odd (in an explanation) to pass a parameter to a function and then ignore it.
	Consider:		Consider:
	<~~source~~ lang="JavaScript">		<syntaxhighlight lang="JavaScript">
	var obj1 = {a : 1};		var obj1 = {a : 1};
	var obj2 = {b : 2};		var obj2 = {b : 2};
Line 356:		Line 356:
	foo(obj1, 3); // Does affect obj1. 3 is additional parameter		foo(obj1, 3); // Does affect obj1. 3 is additional parameter
	alert(obj1.a + " " + obj2.b); // writes 7 3		alert(obj1.a + " " + obj2.b); // writes 7 3
			</syntaxhighlight>
	</source>
	Because the object parameter is passed by reference it can be modified.		Because the object parameter is passed by reference it can be modified.
	This is OR for me. I am just learning. But I was surprised that obj1 can be modified in the function, by p.a=7, yet p=obj2 does not affect obj1. This should be explained. [[User:QuentinUK\|QuentinUK]] ([[User talk:QuentinUK\|talk]]) 02:27, 28 June 2011 (UTC)		This is OR for me. I am just learning. But I was surprised that obj1 can be modified in the function, by p.a=7, yet p=obj2 does not affect obj1. This should be explained. [[User:QuentinUK\|QuentinUK]] ([[User talk:QuentinUK\|talk]]) 02:27, 28 June 2011 (UTC)
Line 406:		Line 406:

	The following		The following
	<~~source~~ lang="JavaScript">		<syntaxhighlight lang="JavaScript">
	alert( !0 === Boolean( !0 ) === !!1 === Boolean( 1 ) === true );		alert( !0 === Boolean( !0 ) === !!1 === Boolean( 1 ) === true );
	alert( !!0 === Boolean( 0 ) === !1 === Boolean( !1 ) === false );		alert( !!0 === Boolean( 0 ) === !1 === Boolean( !1 ) === false );
	alert( !"" === Boolean( !"" ) === !!"s" === Boolean( "s" ) === true );		alert( !"" === Boolean( !"" ) === !!"s" === Boolean( "s" ) === true );
	alert( !!"" === Boolean( "" ) === !"s" === Boolean( !"s" ) === false );		alert( !!"" === Boolean( "" ) === !"s" === Boolean( !"s" ) === false );
			</syntaxhighlight>
	</source>
	Gives the impression that equality can be chained together. A===B===C being true when they are all equal, this is not the case. [[User:QuentinUK\|QuentinUK]] ([[User talk:QuentinUK\|talk]]) 10:57, 11 August 2011 (UTC)		Gives the impression that equality can be chained together. A===B===C being true when they are all equal, this is not the case. [[User:QuentinUK\|QuentinUK]] ([[User talk:QuentinUK\|talk]]) 10:57, 11 August 2011 (UTC)

ShelfSkewed: Removed maintenance template—links fixed

2020-03-25T03:16:02Z

Removed maintenance template—links fixed

← Previous revision		Revision as of 03:16, 25 March 2020
Line 2:		Line 2:
	{{Talk header}}		{{Talk header}}
	{{WikiProject JavaScript\|class=\|imortance=}}		{{WikiProject JavaScript\|class=\|imortance=}}
	{{User:WildBot/m04\|sect={{User:WildBot/m03\|1\|Trigonometric_functions#Cosine\|Cosine}}, {{User:WildBot/m03\|1\|Trigonometric_functions#Sine\|Sine}}\|m04}}
	{{Backwardscopy		{{Backwardscopy
	\|author = Miller, F. P., Vandome, A. F., & McBrewster, J.		\|author = Miller, F. P., Vandome, A. F., & McBrewster, J.