I don't think it makes sense to document d8 the way you would like to. It's meant merely as a test bed, and as such, subject to changing requirements. I would rather suggest to use node.js instead. Other than that, I'd say the test cases in test/mjsunit serve the purpose of showing how to use d8.
Cheers, Yang On Saturday, November 12, 2016 at 2:24:27 AM UTC+1, Rong Jie wrote: > > I understand that the primary purposes of d8 are merely testing and > debugging, but the built-in I/O functions are actually enough to serve some > educational purposes. For example, Codeforces (online competitive > programming website) uses (outdated version of) d8 to judge JavsScript > solution. > > In that case, it will be good if we can have a simple documentation or > tutorial on how to use d8. There are some blog posts for this, but they are > not kept up-to-date. For instance, they do not mention about printErr which > was only implemented recently (1/11/2016). > > I have put most of my own findings on StackOverflow documentation ( > http://stackoverflow.com/documentation/v8/7745/getting-started-with-d8), > but I still think it will be a great idea if we can have something like > this directly in Github wiki for visibility. > -- -- 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.
