console.log

Question

console.log

pitust opened this issue 5 years ago · comments

https://github.com/coder-mike/microvium/blob/master/doc/getting-started.md says console.log and it doesnt work. Did you mean log, which does work?

pitust commented 4 years ago

Fixed

Michael Hunter · Answer 1 · Thu May 14 2020 07:05:31 GMT+0800 (China Standard Time)

Welcome! I think you may be the first person to try Microvium out, and certainly the first to contribute an issue!

I think the issue you're seeing is that you're probably using the latest (pre)release on npm, which was released before I had implemented support for object and properties like console.log. Things have progressed since then I changed it to console.log to make it more familiar to JS developers. I'll run through the getting-started guide again on my machine just to make sure it all works, and re-publish another (pre)release to npm.

Do you mind me asking, how did you hear about Microvium, since I haven't widely publicized it yet? And what are you considering using it for?

Michael Hunter · Answer 2 · Thu May 14 2020 16:39:11 GMT+0800 (China Standard Time)

@pitust See if (pre)release 0.0.8 fixes your issue.

I also added a regression test suite which programmatically executes the code in the getting-started.md file to help it from getting out of sync again in future.

pitust · Answer 3 · Thu May 21 2020 17:22:42 GMT+0800 (China Standard Time)

Embedding should be made easier IMO, if I want to embed, say, wasm2c'ed code (which lets you run Typescript via AssemblyScript), i need to implement (when writing with OSDev-level STL mind you): calloc and exports and call one function. There is no "resolveImport" which by the way, can be auto-generated, all arguments are normal C arguments (unless the language used has them). On the flip side, structure deserialization in wasm2c is a pain, because NOTHING lies on the stack, and every pointer is a pointer to a different address space.

Michael Hunter · Answer 4 · Thu May 21 2020 18:12:36 GMT+0800 (China Standard Time)

There is no "resolveImport"

I'm not familiar with wasm2c. If there's nothing analogous to resolveImport, then how do you call a C function from TypeScript code? Or, how do you import a function implemented by the host?

pitust · Answer 5 · Mon May 25 2020 19:30:06 GMT+0800 (China Standard Time)

You import them in TS like this:

declare function importedFunc(): void;

Then, compiled to wasm, it will be a WASM import:

  (type $t0 (func))
  (import "main" "importedFunc" (func $main.importedFunc (type $t0)))

which wasm2c will convert into a (mangled) name.
You then create a variable with that name, assign the function poitnter to it, and it will (hopefully) work.