ChakraCore is the core part of the Chakra Javascript engine that powers Microsoft Edge
Intuitively, I would want that resolved against the module calling .map
And even if in this case we skip over internal library frames, the same issue could come up from shims or other things providing non-default library functionality
From an engine perspective, it's basically impossible to tell them apart I think, so the best way in my mind is to be specific and essentially bind the function to a particular context, e.g. specialize it for a given module
And yeah, I think the simplest way to do that is to do something like the commonjs approach where you inject a bit of code at the start
If you jam it all on one line, then it wouldn't impact user code much at all
But if they do put things on the first line (especially if it's minified) then that could be a pain
But as @MSLaguana points out, higher-order functions complicate matters
The error object is returned via
result IIRC
If you string coerce it you only get the error message but you can read properties off it instead
It’s the same thing you would get back in JS for
try { eval(invalid_code); } catch(err) { ... }
so I'm dense, or out of my depth here... I get what I think is the object you are talking about using JsGetAndClearException(obj). Using JsConvertValueToString/JsStringToPointer, I get the string I referred to above. So then I try to get the line property from it - using JsGetPropertyIdFromName and then JsGetProperty - and I get undefined for the value of the property.
Assuming you're using chakracore I generally would reccomend avoiding the APIs in ChakraCommonWindows.h; stick to the APIs in ChakraCommon.h and ChakraCore.h
@tondrej
I'll try to stick to the non-windows API. But... do they solely differ by parameter type? or is there more to it?
Otherwise valgrind doesn’t like the 32GB address space reservation and suicides
“Out of memory”
I think the working (though with some issues) static version of chakracore was part of this game engine project: https://github.com/Kode/Krom
AdobeFlashMan, you may find https://github.com/Kode/openfl interesting, it's basically a minimal incomplete implemention of OpenFL implemented on top of Kha and potentially suitable for use with Krom. As you may know OpenFL is a Haxe implementation of the flash api and compiles both to c++ and js. Kha is more of a renderloop approach like say starling's renderTexture but cleaner. Kha code base is mixed js/c build but uses haxe ( or C++ ) for coding. Haxe is quite similar to as3 but arguably a better. Kha can target js or c++, it uses Krom as one possible target, I think it might be built into 'Kode Studio' a variant of Visual Code Studio and used for testing and debugging Kha and shaders. Anyway the way Kha uses Krom is with shaders recompiled ( https://github.com/Kode/krafix ) so there is no Dom support and it's purely a JS shader engine. I don't know anything about static linking etc... being more front end x-flash and now a haxe dev. But if your looking for a way to create applications and games with ChakraCore then Kha is definitely an option, if your used to Flash then you will find the text support good but very low level. For GPU graphics it's much cleaner simpler than flash stage3d and starling and allows many workflows perhaps look and Armory3d and the core library Iron as one possible approach.
sorry my grammer is not ideal.
this applies to both to objects I pass into the javascript engine, and some objects created by the javascript code
a related question: I expose an object of mine to javascript, so that myObj.prop refers through to "prop" on my internal object, and myObj.prop = "test" sets the value of the prop on my object. But if the user accidentally does myObj.propx = "test", chakra creates a new js prop "propx" on the js wrapper object. I haven't found a way to either prevent this or get notified about it, so the property gets lost and it's effectively a silent bug. What are my options here?
@grahamegrieve to mark an object as immutable, I think you could use Object.freeze(), for hooking property setters/getters perhaps you could use a Proxy or, if you only want to prevent adding new properties, Object.preventExtensions()