gnscript demo - a script language for Windows applications

Features

• Programming language syntax that is used in many other programming languages
• Script language contains a large set of system functions
• Exception handling with try and catch
• 94 example scripts that demonstrate the script language usage and can help to learn programming
• Small programming language interpreter designed for integration into Windows applications
• Extendable programming language by features of a main Windows application (application functions, binding to application data)
• Unit testing of scripts (all examples are designed as self testing unit tests)
• Example 100-createindexpage.gnscript reads all other example gnscript files and creates a file index.txt that tells which syntax elements are used in which script files.
• Internal script debugger with conditional breakpoints
• Internal script profiler (for speed optimization to find the slow parts within a script
• gnscript syntax and standard functions

Ideas for uses

• Demo can be used to learn programming from examples. It is definitetly easier to learn programming from code examples. Syntax of a programming language is secondary. Important for good programming is solving a problem by an algorithm (a way that a solution for the problem can be found) and then formulate it using programming statements.
• GNMIDI application uses the scripting language by a plugin to extend GNMIDI by user functions for analysing or modifying binary MIDI files.
• GNMIDI application adds many functions and data access possibilities into the scripting language so that binary MIDI files can be fully read, written, analysed, manipulated.
• GNMIDI application uses gnscript unit tests to test MIDI functions. The tests are automatically run without GNMIDI before releases of MIDI applications.
• Search and replace text in files tool adds expert mode fields that may contain gnscript source code to only change lines or files where certain gnscript programmed conditions are matching (source text is interpreted using eval() function and has access to certain data e.g. line number, text line, file name).
• Unit testing of scripts (all examples are designed as self testing unit tests)
• Applications that need some different behaviors for different users could use gnscript for optional defining the different behavior (e.g. Some customers want filenames and folder structures to be designed very different (including date formatting)
• There exist powerful tools extendable by scripts that require use of horrible postfix script languages
  e.g. BRIEF editor

  ;**	delete white spaces until find non white
  				
  (macro delete_white
  	(							
  		(while (|| (== (read 1) " ") (== (read 1) "\t"))
  			(delete_char)
  		)
  	)
  )
  
  

  With gnscript it could look like:

  //	delete white spaces until find non white
  
  function delete_white()
  {
  	while (read(1) ==  " " || read(1) == "\t")
  	{
  		delete_char();
  	}
  }
  

  e.g. Cakewalk CAL script

  (do
  	(= Now (makeTime (+ (meas Now) 8) 1 0))
  )
  

  Not sure what that unreadable code really means but maybe With gnscript such mysterious code could be written as:

  foreach (var ev in song.events)
  {
  	ev.Time = makeTime(meas(ev.Time)+8, 1, 0);
  )
  
  

  
  Those scripts in polish notation will work powerful but for a human programmer this syntax is not helpful and not necessary and not even good readable for programming experts.

Test feedback

unittest_areequal(myfunction(myargument), "expected result", __CODEPOS__() );
unittest_areequal(unittest_count(), 1, "incomplete");
print(unittest_results());