Sami Vaarala

I now have an OpenIndiana VM, using gcc 6.5.0 (OpenIndiana 6.5.0-oi-2). I looked at the output of `gcc -dM -E - < /dev/null | sort` and at a glance it...

@Toasterson Regarding this comment https://github.com/svaarala/duktape/pull/1514#issuecomment-533431807: I'm not sure I understand what you meant by: > The fact that it detects current Solaris and Illumos Systems as "Old" is definitely wrong....

> __SUNPRO_C does not indicate a version of Solaris, but the use of the Sun/Oracle Studio compilers instead of gcc or clang. I think it was used as a proxy...

Agreed.

There's no support for that, but there is a debugger protocol which one can interface with, see https://duktape.org/guide.html#debugger. It would indeed be nice if it would be possible to proxy...

There are two existing module loaders in the repo: - https://github.com/svaarala/duktape/tree/master/extras/module-duktape - https://github.com/svaarala/duktape/tree/master/extras/module-node Both of these load modules by taking the module source code and encapsulating it in a `function...

> It says about duk_compile_lstring and duk_dump_function. What's the difference between them and modules, and what is preferred? When executing a script ("program") you first compile it, and then execute...

How much memory and flash are you working with? In general, you should use tools/configure.py to configure Duktape for compilation. It's also possible to edit `duk_config.h` manually, but it's easier...

Duktape has been used in some environments with less than 64kB of memory, but that requires use of low memory options (especially "ROM built-ins") and a good, pool-based memory allocator...

One documented starting point is to (on Linux) say: ``` $ make duk-low-rom $ ./duk-low-rom ``` This compiles a low memory optimized Duktape command line for testing. It uses around...