Bruce Pascoe
Bruce Pascoe
@moar82 If you’re expecting that `require("http")` to work automatically with the node module loader, it won’t unless you provide your own implementation of the `http` module... This is just a...
Sounds like a compiler bug to me.
I have MSVC 2015, I should check that out.
@darkuranium Sorry, I forgot all about this issue. :sweat_smile: I just checked, and the following compiles and runs successfully using MSVC 2015/`cl.exe` v19.00: ``` c #include struct eaty { int...
@svaarala I don't have a copy of MSVC 2013 installed anywhere, but I did some quick Google searching and it looks like MSVC 2013 was the first version to support...
One important thing to note is that module resolution in Node.js is file-based, and that must be emulated for full compatibility. The module ID of a loaded module is exactly...
Is this still relevant? We have the Node.js loader extra now, which I believe is also Duktape 1.x compatible.
Update on this: The segfault only seems to occur when calling `JsGetModuleNamespace()` on modules that fail loading due to an early error (e.g. syntax errors). If the module is still...
~This sounds to me more like a issue with DirectX and/or the graphics drivers than Allegro; Allegro is a pretty thin interface and doesn’t tend to do a lot of...
Yeah, I edited my post above after reading the linked threads. I had forgotten that Allegro does a pretty heavy trial-and-error enumeration of display modes when creating a display.