joshuathijssen - saffire-intro-ipc.pdf

Transcript

1. Saffire “programming the web since 2013”
3. Saffire Goals • Be a (not the) programming language. • Suitable for web (fastCGI) and command line. • Try and fix some of the shortcomings of other languages. • Cool, workable, enjoyable language.
4. History • Primarily based on PHP / Python syntax with some ideas from other languages (java, ruby, javascript). • We’re 10-15 years behind, but 10-15 years of traps and pitfalls we can avoid.
5. Selling points • Everything is an object. • Even “foo”, 2, /reg?ex*/ and 3.14159265. • UTF-8 out of the box. • No functions, just objects and methods. • Method and operator overloading. • Threaded system
6. Hello world use io; io.print(“hello world”);
7. Variables and such use io; $a = 1; $b = “foo”.length(); // 3 $c = “björk”.length(); // 5! $d = “björk”.bytes().length(); // 6! $e = “foo”.reverse().upper(); // “OOF” io.print(“$e equals: ”,$e);
8. Classes use io; class Foo { const PI = 3.1415; protected property $a = 1; public method ctor() { io.printf(“Constructor called!\n”); } public method dtor() { io.printf(“Destructor called!\n”); } public method Bar() { self.$a++; } } $f = Foo(); io.printf(“PI is %0.3f“, Foo.PI); io.print(“First call: “, $f.bar()); io.print(“Second call: “, $f.bar()); $f.destroy(); // $f is no more
9. Saffire for PHP devs • FastCGI and CLI only • “compiled” bytecode (*.sfc files) • UTF-8 - strlen(), strpos() etc. • Objects everywhere • Method and operator overloading • There are no arrays (hashmaps & lists ...) • Multi assignments: $a, $b = 1, 2; • Empty assignments: $a, ,$b = 1, 2, 3;
10. Saffire for PHP devs • By default returns “self” ($this) (fluent interface) • foreach/else while/else breakelse • try / catch / finally • “ducktyping” and interfacing are supported • Out of the box annotation-reader
11. Current status • Initial scanning / parsing done (flex/bison). Might change to lemon & re2c • Language specification on its way. • Still figuring out problems. • Abstract Syntax Trees (AST) can be generated. • Initial object module engine created (heavily based on Python’s) • Initial interpreter on it’s way
12. $./saffire test.sf --dot test.dot
13. What’s next • Finish the language specification. • Implementation specification • Bytecode + optimization phase (peephole) • Create the interpreter. • Create a more stable lex / parse system (pure_parser / lemon) • ??? • Profit
14. (Un)Stable release? • Depends on the help! • 0.01 not until somewhere (late) 2013. • Roadmap hasn’t been created. • First (dutch) meetup: 26 october 2012
15. We need YOU... • C programmers, but many, many others for websites, documentation, language specification, testing/QA, app writers, framework writers, evangelists, logo designers, etc, etc.. • USERBASE! • If you can read this, you can help us!
16. Find us! • IRC: freenode.org #saffire • website: http://saffire-lang.org • github: https://github.com/saffire/saffire • mailinglist: https://groups.google.com/group/ saffire-internals • twitter: @saffire-lang
17. io.print(“Thank you!”);