GScript - Revision history

Reel.Deal: add archived downloads section

2020-05-23T15:03:26Z

add archived downloads section

Reel.Deal: add x64 version

2020-05-23T14:53:42Z

add x64 version

Raffriff42: /* Avisynth+ */ "incompatible changes" clarification

2017-10-29T15:06:15Z

‎Avisynth+: "incompatible changes" clarification

Raffriff42: /* Avisynth+ */ one more touch up

2017-10-10T21:05:51Z

‎Avisynth+: one more touch up

Raffriff42: /* Avisynth+ */ one more touch up

2017-10-08T15:36:07Z

‎Avisynth+: one more touch up

Raffriff42: one more touch-up

2017-10-06T13:53:27Z

one more touch-up

Raffriff42: one more touch-up

2017-10-06T02:12:05Z

one more touch-up

Raffriff42: /* Examples */ typo

2017-10-06T02:11:05Z

‎Examples: typo

Raffriff42: one more touch-up

2017-10-06T01:58:33Z

one more touch-up

Raffriff42: /* Avisynth+ */ link to Examples section

2017-10-06T01:51:18Z

‎Avisynth+: link to Examples section

← Older revision		Revision as of 15:03, 23 May 2020
Line 214:		Line 214:
	v1.0 (Gavino, 18th June 2009): first release		v1.0 (Gavino, 18th June 2009): first release

−	~~''Document v1.1 (Gavino, 6th December 2009)''~~
	</div>		</div>
		+	<br>
		+	== Archived Downloads ==
		+	<div style="max-width:62em" >
		+	{\| class="wikitable" border="1"; width="600px"
		+	\|-
		+	!!width="100px"\| Version
		+	!!width="150px"\| Download
		+	!!width="150px"\| Mirror
		+	\|-
		+	!v1.1 (x86/x64)
		+	\|[http://www.mediafire.com/file/nticdylrh0u6vef/GScript_32_64.7z/file GScript_32_64.7z]
		+	\|[https://web.archive.org/web/20200523165020if_/https://files.videohelp.com/u/223002/GScript_32_64.7z GScript_32_64.7z]
		+	\|-
		+	!v1.1
		+	\|[https://forum.doom9.org/attachment.php?attachmentid=10552&d=1260141726 GScript_11.zip]
		+	\|[https://web.archive.org/web/20200523170142if_/https://files.videohelp.com/u/223002/GScript_11.zip GScript_11.zip]
		+	\|-
		+	\|}
		+	* x86/x64 version compiled by [https://forum.doom9.org/showthread.php?t=173259 Groucho2004].
		+	</div>
		+	<br>
		+	<br>
		+	-----------------------------------------------
		+	'''Back to [[External_filters#Support_filters\|External Filters]] ←'''

@@ Line 1: / Line 1: @@
-[[Category:External_filters]]
+<div style="max-width:62em" >
-[[Category:Support_filters]]
+{{FilterCat4|External_filters|Plugins|Plugins_x64|Support_filters}}
 <!-- '''GScript - extends the Avisynth scripting language''' -->
 <div style="max-width:62em" >
-'''GScript''' provides Avisynth developers with additional [[Control_structures|control-flow constructs]]:
+'''GScript''' provides AviSynth developers with additional [[Control_structures|control-flow constructs]]:
 * <code>for</code> loops
@@ Line 10: / Line 19: @@
 '''GScript''' effectively extends the language [[AviSynth_Syntax|syntax]], making it easy to use these constructs in a natural way as you would in a language like C or JavaScript.<br>
 </div>
+<br>
-__TOC__
+== Requirements ==
+* [x86] [[AviSynth+]] or [https://sourceforge.net/projects/avisynth2/ AviSynth 2.6.0]
+* [x64] [[AviSynth+]]
 ==Syntax and Parameters ==
 <div style="max-width:62em" >
@@ Line 56: / Line 57: @@
   GImport("MyGScript.avs")
 </div>
-For completeness, there is also a function '''GEval''', analogous to the standard [[Internal_functions/Eval|Eval]], which evaluates a string containing Avisynth and GScript [[Grammar|statements]].
+For completeness, there is also a function '''GEval''', analogous to the standard [[Internal_functions/Eval|Eval]], which evaluates a string containing AviSynth and GScript [[Grammar|statements]].
 ==== Additional Notes ====
-* As the 'GScript language' includes all standard Avisynth constructs too, you can even put your entire script inside a call to GScript if you want. There is no need to put each 'if' statement in a separate call, for example.
+* As the 'GScript language' includes all standard AviSynth constructs too, you can even put your entire script inside a call to GScript if you want. There is no need to put each 'if' statement in a separate call, for example.
 * A function declared inside the GScript environment can be called from outside, and vice versa. So you can add GScript constructs to a function without changing the calling code.
@@ Line 67: / Line 68: @@
 * The loops are purely 'compile-time' constructs. There is no loop in the run-time filter graph, only in the ''construction'' of the graph (just as with a recursive function).
-* Within GScript, comments are allowed before a '<b>{</b>'. This applies not only in the GScript constructs (''if'', etc), but also to standard uses of '<b>{</b>' in function declarations and ''try/catch''. Arguably, it is a bug that Avisynth itself does not permit this (see [http://forum.doom9.org/showthread.php?t=145168 this thread]).
+* Within GScript, comments are allowed before a '<b>{</b>'. This applies not only in the GScript constructs (''if'', etc), but also to standard uses of '<b>{</b>' in function declarations and ''try/catch''. Arguably, it is a bug that AviSynth itself does not permit this (see [http://forum.doom9.org/showthread.php?t=145168 this thread]).
-==== Avisynth+ ====
+==== AviSynth+ ====
 Two notable differences exist between the plugin and the {{AvsPluscon}} implementation:
 *There is no need to use the string wrapper shown above. The language extensions became native and can be used transparently.<br>For example,
@@ Line 97: / Line 98: @@
+  }
 </div>
-:where ''condition'' is any boolean (true/false) [[Grammar|expression]]. The ''statements'' can be any Avisynth statements, including GScript extension statements, and so the new constructs can be ''nested''. The <code>else</code> clause is optional.
+:where ''condition'' is any boolean (true/false) [[Grammar|expression]]. The ''statements'' can be any AviSynth statements, including GScript extension statements, and so the new constructs can be ''nested''. The <code>else</code> clause is optional.
 :GScript also provides the <code>else if</code> construct, which may be repeated as needed. Thus the full form of the <code>if</code> statement is:

@@ Line 71: / Line 71: @@
 ==== Avisynth+ ====
 Two notable differences exist between the plugin and the {{AvsPluscon}} implementation:
-*There is no need to use the string wrapper shown above. The language extensions became native and can be used transparently.
+*There is no need to use the string wrapper shown above. The language extensions became native and can be used transparently.<br>For example,
-*The '''return''' statement has been changed to not only exit the inner-most code block, but to terminate the function (or script) in which it is placed. This is one of the very few incompatible changes compared to classic AviSynth.
+<div {{BoxWidthIndent|22|1.5}}>
 See [[#Examples|Examples]] section below.<br>
 See discussion [http://forum.doom9.org/showthread.php?p=1712511#post1712511 here] (doom9.org)

@@ Line 68: / Line 68: @@
 * Within GScript, comments are allowed before a '<b>{</b>'. This applies not only in the GScript constructs (''if'', etc), but also to standard uses of '<b>{</b>' in function declarations and ''try/catch''. Arguably, it is a bug that Avisynth itself does not permit this (see [http://forum.doom9.org/showthread.php?t=145168 this thread]).
 ==== Avisynth+ ====
@@ Line 76: / Line 75: @@
 See [[#Examples|Examples]] section below.<br>
 See discussion [http://forum.doom9.org/showthread.php?p=1712511#post1712511 here] (doom9.org)

@@ Line 67: / Line 67: @@
 * The loops are purely 'compile-time' constructs. There is no loop in the run-time filter graph, only in the ''construction'' of the graph (just as with a recursive function).
-* Within GScript, comments are allowed before a '{'. This applies not only in the GScript constructs (''if'', etc), but also to standard uses of '{' in function declarations and ''try/catch''. Arguably, it is a bug that Avisynth itself does not permit this (see [http://forum.doom9.org/showthread.php?t=145168 this thread]).
+* Within GScript, comments are allowed before a '<b>{</b>'. This applies not only in the GScript constructs (''if'', etc), but also to standard uses of '<b>{</b>' in function declarations and ''try/catch''. Arguably, it is a bug that Avisynth itself does not permit this (see [http://forum.doom9.org/showthread.php?t=145168 this thread]).
 </div>
-==== Avisynth+====
+==== Avisynth+ ====
-{{AvsPluscon}} Two notable differences exist between the plugin and the AviSynth+ implementation:[http://forum.doom9.org/showthread.php?p=1712511#post1712511]
+Two notable differences exist between the plugin and the {{AvsPluscon}} implementation:
 *There is no need to use the string wrapper shown above. The language extensions became native and can be used transparently.
-*There is no need to use the string wrapper shown above. The language extensions became native  and can be used transparently.
+*The '''return''' statement has been changed to not only exit the inner-most code block, but to terminate the function (or script) in which it is placed. This is one of the very few incompatible changes compared to classic AviSynth.
-*The '''return''' statement has been slightly changed to not only exit the inner-most code block, but to terminate the whole function (or script). See [[#Examples|Examples]] section below. This is one of the very few incompatible changes compared to classic AviSynth.
+See [[#Examples|Examples]] section below.<br>

@@ Line 150: / Line 150: @@
 | {{AvsPluscon}} native
 |-
-| style="vertical-align:top" | <pre>
+| style="vertical-align:top" |
-LoadPlugin("GScript.dll")
+ ''[[LoadPlugin]]("GScript.dll")''
-BlankClip(width=240, height=160)
+ [[BlankClip]](width=240, height=160)
-Subtitle("GScript plugin test", align=8)
+ [[Subtitle]]("GScript plugin test", align=8)
-GScript("""
+ ''GScript("""''
-for (i=0, 5) {
+ for (i=0, 5) {
-  Subtitle(String(i), y=18*i)
+   Subtitle([[Internal_functions#String|String]](i), y=18*i)
-  if (i>=3) {
+   if (i>=3) {
-    Subtitle("i>=3", align=5)
+     Subtitle("i>=3", align=5)
-    return Last
+     return Last
-−
+   }
-−
+ }
-""")
+ ''""")''
-return Subtitle("(exit)", align=3)
+ return Subtitle("(exit)", align=3)
-</pre>
 | &nbsp;&nbsp;
-| style="vertical-align:top" | <pre>
+| style="vertical-align:top" |
-BlankClip(width=240, height=160)
+ &nbsp;
-Subtitle("GScript AVS+ test", align=8)
+ [[BlankClip]](width=240, height=160)
-for (i=0, 5) {
+ [[Subtitle]]("GScript AVS+ test", align=8)
-  Subtitle(String(i), y=18*i)
-  if (i>=3) {
+ for (i=0, 5) {
-    Subtitle("i>=3", align=5)
+   Subtitle([[Internal_functions#String|String]](i), y=18*i)
-    return Last
+   if (i>=3) {
+     Subtitle("i>=3", align=5)
+     return Last
 return Subtitle("(exit)", align=3)
-</pre>
 |-
 |[[Image:GScript-test-10.png]]

@@ Line 191: / Line 191: @@
 </div>
 </div>
 == Plugin Revision History ==

@@ Line 186: / Line 186: @@
 ''"(exit)" line is executed''
 | &nbsp;&nbsp;
-| ''Loop IS terminated by 1st 'return Last' statement;''<br>
+| ''Loop IS terminated by 'return Last' statement;''<br>
 ''"(exit)" line NOT executed''
 |}
 </div>
 </div>
 == Plugin Revision History ==

@@ Line 74: / Line 74: @@
 *There is no need to use the string wrapper shown above. The language extensions became native  and can be used transparently.
-*The '''return''' statement has been slightly changed to not only exit the inner-most code block, but to terminate the whole function (or script), as anybody with even the slightest scripting experience would expect. This is one of the very few incompatible changes compared to classic AviSynth.
+*The '''return''' statement has been slightly changed to not only exit the inner-most code block, but to terminate the whole function (or script). See [[#Examples|Examples]] section below. This is one of the very few incompatible changes compared to classic AviSynth.
-−
 == The constructs in detail ==