On Friday, 1 June 2018 04:06:41 UTC-4, Ben Noordhuis wrote: > > You can retrieve the script id after compiling with > v8::UnboundScript::GetId(). (Yes, the casing is inconsistent.) > > Can't use the script object - there are multiple scripts in play because one script "includes" other scripts and when I catch an exception, all I have is an instance of `v8::Message`, which does have the script origin that is out of sync with the actual script.
> You should treat it as an arbitrary number but if you're curious why > it starts at 10, the first few are V8's internal helper scripts. > I assumed as much with regards to the base value, which makes it impossible to rely on that value to always be that. Thanks for confirming that. As for the arbitrary number, it has no usefulness on its own - unless I can link it back to the script that triggered the exception with this message, how would you possibly use almost a random value that has no relation to the script that triggered that exception? -- -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
