3 ms·
Sounds... incredible. A few questions: - Which object model & garbage collector system are you using? (in C) - How do you handle scoping differences between
by deckiedan 13y ago
Sounds... incredible.
A few questions:
- Which object model & garbage collector system are you using? (in C)
- How do you handle scoping differences between JS/PHP/C?
- Which bignum and string libraries are you using in C? Is the String library fully unicode happy?
- How do you deal with 'eval', and other JS-specific functionality?
- You mention the classes being easily turned into C++ classes... how does that work with the dynamic nature of POJO objects, when at any time new methods and properties can be added to any object, or prototype?
Sounds intriuging, anyway...
- lucio 13y agoGreat questions!, I guess I didn't express myself correctly. I meant: LiteScript is designed with the Grammar https://github.com/luciotato/LiteScript/blob/master/source/Grammar.lite.md https://github.com/luciotato/LiteScript/blob/master/source/G... separated from the "production" of target code https://github.com/luciotato/LiteScript/blob/master/source/Producer_js.lite.md https://github.com/luciotato/LiteScript/blob/master/source/P... I "want" to (and think I can) add new "producer" modules other than "producer_js", but I've not even started. The idea -so far- is to compile to a node native extension http://nodejs.org/api/addons.html#addons_hello_world http://nodejs.org/api/addons.html#addons_hello_world so most C answers are: V8's With respect to PHP, I think it's simpler. The idea is to generate PHP but do not support all PHP quirks, just generate PHP code that is "js-like", (PHP mimics allmost all js functionality) and have support libs in LiteScript unifying APIS. Some things like "eval" can throw a compiler error, when the target is PHP.