IronSapphire

What makes IronSapphire better than Sapphire.NET

• Executes faster
• Support for creating classes (Because of new JIT-Parser)
• Some backward compatibility with old syntax (has keywords like "say" and "var")
• Better OO Support (Python inspired)
• Still can be embeded in applications.
• Support for For Loops
• More comming soon.

Roadmap of Features

• JIT-Parser : 75% (Doesn't support parameters for functions in classes yet, For loops in classes cause the parser to fail.)
• For Loop : 100% (Maybe be buggy)
• If Statement : 10% (Gathering my ideas)
• Support for All .NET classes : 0% (Not started; Planned)
• Runs on DLR : 0% (Researching)

Example Syntax

Printing Text

 say("This is text")

For Loop

 for(var i = 0 -> 20) //Loops until 20//
 :{
        say(i)
 :i} //End of the for loop. REQUIRED: You must put the var name in the end brackets because of parsing problems.

Script Entry point

main()
{
}

Math Operations

        //This code tests math operations//
	var d = "2"
	var c <- eval(2+3+d)
	say(c)

String Concatenation

        //The following code tests string combining.//
	var e = "Hello,"
	var f = " World!"
	var g <- combine(e,f," :P")
	say(g)

Getting Console Input

        //This gets input from Console.ReadLine//
	var g <- input("What is your name?")
	say(g)

Known Bugs

1. For Loops in classes made in IronSapphire cause the Parser to fail. For right now, execute all your for-loops in the main area.