Just an educational question about objectscript

[unitpoint]

Hello, thank you for good questions, I'll try to answer.

1. OS has parser and compiler. The parser splits input text to list of tokens. The compiler uses the tokens to make result opcodes used by OS virtual machine.
2. The parser doesn't know which purpose it has to expect but the compiler knows. For example "if" token expects boolean expression and body. The body could be started using "{" character. The compiler knows that the "{" character starts number of instructions but not OS object declaration.
3. It's C++ templates magic. OS binder uses template functions that convert OS arguments to C++.
4. Use objectscript.h, objectscript.cpp, os-heap.h, os-heap.cpp, os-binder.h to compile OS min version.

[IngwiePhoenix]

I see, thanks for the reply!

So the parser is only the step before the VM, I see. And, what is the „rough“ logic that the VM has to execute things? Sorry that I ask such deep questions, but I am very curios ^^;

Also, how would one teach the parser/vm additional syntax - and how hard is that, too?

And, Im totally going to implement Objectscript into an upcomming project - its jsut too awesome :)
Am So. Feb. 02 2014 21:18:04 schrieb Evgeniy Golovin:

Hello, I'll try to answer all questions.

OS has parser and compiler. The parser splits input text to list of tokens. The compiler uses the tokens to make result opcodes used by OS virtual machine.

The parser doesn't know which purpose it has to expect but the compiler knows. For example "if" token expects boolean expression and body. The body could be started using "{" character.

if(i > 0){ echo "OK" }

The compiler knows that the "{" character contains number of instructions but not OS object declaration.

It's C++ templates magic. OS binder uses template functions that convert OS arguments to C++.

Use objectscript.h, objectscript.cpp, os-heap.h, os-heap.cpp, os-binder.h to compile OS min version.

—
Reply to this email directly or view it on GitHub.

[unitpoint]

Not only, it contains Parser => Compiler => VM. OS::Core::execute() implements main VM logic.

New syntax should be implemented, debugged, tested, optimized, It should not conflict current syntax. So it depends on the new syntax.

[IngwiePhoenix]

Wat, that function is 1249 lines long?! Wow… That’ll take a lot of time untill I can wrap my head around that o-o

BTW. When I try to use

var $meep=“foo“;

I get an error that says that $ is a syntax error…but i saw nothing in the documentation that this way of variable naming was disallowed? o.o
Am Mo. Feb. 03 2014 09:57:58 schrieb Evgeniy Golovin:

Not only, it contains Parser => Compiler => VM. OS::Core::execute() implements main VM logic.

New syntax should be implemented, debugged, tested, optimized, It should not conflict current syntax. So it depends on the new syntax.

—
Reply to this email directly or view it on GitHub.

[unitpoint]

Sorry, $ is reserved for future purposes at the moment.

[unitpoint]

$ is not reserved now, you could use it for names of variables or functions

[IngwiePhoenix]

Awesome. I just tested it and made the function I wanted to make. Thanks for the info!