On Sat, Jul 20, 2013 at 5:12 PM, Richard S <[email protected]> wrote:
> Okay, then is there a way to return an undefined object on an improper > constructor? And I still have yet to solve the problem with values not > being what they're supposed to be :/ > To signal a bad constructor, throw a JS-side exception by calling v8::ThrowException(). -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal -- -- 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/groups/opt_out.
