Hi Kevin, [ + google-caja-discuss +mikesamuel ]
On Mon, Oct 12, 2009 at 4:24 AM, Kevin Reid <[email protected]> wrote: > Point: The *tests* currently require E support; the library itself > does not. Got it. > These tests are all of infrastructure though; none of them are > actually at the level a *user* of the system would be working, because > that level has not been implemented yet. > > A user of a full CapTP system works purely in terms of SturdyRefs, far > refs, and the Introducer/MakeSturdyRef authorities; they don't see any > of the infrastructure currently existant. Sure ... but the user would presumably also be plugging in a transport, with the appropriate interface, right? So anyway -- there ought to be an example, in Cajita, of setting up vats A and B talking to each other. Mike Stay and I were merely trying to do this the hard way -- by working through the code bottom-up. If you are willing to do it for us the easy way, we would be delighted. :) > Based on a Google search I just looked at http:// > jsdoc.sourceforge.net/ and http://code.google.com/p/jsdoc-toolkit/ and > JSDoc seems to be a Javadoc-style tool, with no testing functionality. > What am I missing? You are missing this: http://codereview.appspot.com/8706/show Mike Samuel has created a JS doc tool that (as I understand it) allows Updoc style tests in the documentation. I have not used it, but please ask Mike about it and see if it suits your needs. Specifically, I think you need it to run *Cajita* code as Updoc, not simply regular JavaScript code. I don't know if, or how, Mike's JSDoc supports that. Please do ask him. Ihab -- Ihab A.B. Awad, Palo Alto, CA
