On 2/24/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
There needs to be tests of XPCOM standalone and XPCOM not standalone, and this can work if they are automated and the tests test the specified component interfaces.
Long ago there was an effort made to make XPCOM standalone and not-standalone the same identical binary and to get rid of all of the IFDEFs. Did that work ever get finished? During that long ago time the idea was to first compile and test XPCOM standalone, NSPR and Spidermonkey in a standalone environment. Then something like XULrunner would be compiled, tested and run on top of this environment. I was quite in favor of this model since it greatly reduces the scope of component interactions during the testing phase. I never liked how Mozilla can only be compiled and tested as a single giant blob (of course XULrunner is on the way to breaking things up). There used to be a program around that built graphs of how all of the modules in Mozilla called APIs between each other. It looked like a giant bowl of spaghetti tied in a knot. Is it still around anywhere? -- Jon Smirl [EMAIL PROTECTED] _______________________________________________ dev-tech-xpcom mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-xpcom
