On Wed, Jan 11, 2012 at 12:38 AM,
<v8-j...@googlecode.com> wrote:
Comment by bionicba...@gmail.com:
Hi again, Badger! (i'm replying on our mailing list instead of as a response to your wiki comment.)
First off: my apologies for keeping my response so brief. i have a back injury and sitting in front of the computer is very painful, so i need to keep this short...
I've incorporated the V8 shell into a GUI app and it works very well for most intents and purposes. I like the framework and it sure beats having to set up all the V8 structures manually.
Great, i'm glad someone has gotten some use out of it. Forewarning: V8Shell was never really intended to be "production grade", but more as a bootstrapping tool for test/demo code for cvv8. Because of that, it has some rough edges, such as what you mention here:
While I've added my own text output routines, one problem I have is with error outputs. I can't easily redirect errors to my output window using SetExecuteErrorReporter() because I need static functions to do so (to my knowledge). Could other (error) output redirection
SetExecuteErrorReporter() is new to me.
methods be provided so that shells can be more easily incorporated into applications that can't rely on std::cerr or static functions for error reporting.
I know I could modify the code myself, but I like keeping libraries as "kosher" as possible if only so that I can update my code with the latest updates without problems.
If you have concrete suggestions for how best to add/change the error reporting, i'm all for it. If you have made changes to your copy which you would like to see integrated into the main copy, just send them to the list - i'm always happy to give write access to contributors. i unfortunately can't investigate it more closely at the moment due to my back injury - the only position i can hold right now without whining like a baby the whole time is laying down on my side (and i don't have a computer which can work well in that position).