[Mono-devel-list] patch for xslt standalone tests
This patch fixes the following things:
* eliminates the need to run xsltproc on catalog.xml to produce
catalog-out.xml
* fixes the hack that distinguishes between Xalan and Microsoft
compliance tests
* changes the output of the test: instead of endless scroll of test
names now it prints '.' and 'E' if test was passed and exception thrown,
respectfully. In the future I will check the expected results and print
'e' if the results are different.
If no one objects, I will commit it tomorrow.
Andrew Skiba.
Index: simplify.xsl
===
--- simplify.xsl(revision 44028)
+++ simplify.xsl(working copy)
@@ -1,34 +0,0 @@
-
-http://www.w3.org/1999/XSL/Transform";>
-
-
-
-
-
-
-
-
-
-
-
-
-
Valueof
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Index: catalog.sed
===
--- catalog.sed (revision 44214)
+++ catalog.sed (working copy)
@@ -1,3 +1,4 @@
s/outp\([0-9]+\)/output\1/g
s/str\([0-9]+\)/string\1/g
s/expr\([0-9]+\)/expression\1/g
+s/Value-of<\/file-path>/Valueof<\/file-path>/
Index: ChangeLog
===
--- ChangeLog (revision 44214)
+++ ChangeLog (working copy)
@@ -1,5 +1,12 @@
2005-05-08 Andrew Skiba <[EMAIL PROTECTED]>
+ * catalog.sed : fix a bad dirname for Value-of tests
+ * Makefile, alltests.cs : make alltests.cs use the same catalog as
+ xslttest.cs and output '.' and 'E' for test results
+ * simplify.xsl : deleted
+
+2005-05-08 Andrew Skiba <[EMAIL PROTECTED]>
+
* catalog.sed : fix a typo
2005-05-08 Andrew Skiba <[EMAIL PROTECTED]>
Index: alltest.cs
===
--- alltest.cs (revision 44028)
+++ alltest.cs (working copy)
@@ -12,7 +12,7 @@
static ArrayList excludedTests = new ArrayList (new string [] {
});
- static void Process (string id, string path, string data,
+ static void Process (string submitter, string id, string path,
string data,
string stylesheet, string output, string resDirName)
{
string dirToCheck = Path.Combine(resDirName, path);
@@ -21,11 +21,12 @@
string resFileName = Path.Combine ("../..",
Path.Combine(dirToCheck, id + ".rst"));
- // hacky!
- if (path [0] >= 'a')
+ if (submitter == "Lotus")
Directory.SetCurrentDirectory (Path.Combine
("Xalan_Conformance_Tests", path));
- else
+ else if (submitter == "Microsoft")
Directory.SetCurrentDirectory (Path.Combine
("MSFT_Conformance_Tests", path));
+ else
+ return; //unknown directory
#if NET_2_0
XslCompiledTransform xslt = new XslCompiledTransform();
@@ -34,6 +35,7 @@
#endif
StreamWriter strWr = new StreamWriter (resFileName,
false, System.Text.Encoding.UTF8);
XmlTextWriter wr = new XmlTextWriter (strWr);
+ bool success = true;
try {
XmlDocument xml = new XmlDocument();
xml.Load (data);
@@ -47,9 +49,14 @@
strWr.Close();
strWr = new StreamWriter (resFileName, false,
System.Text.Encoding.UTF8);
strWr.Write("{0}",
x.GetType().ToString());
+ success = false;
}
strWr.Flush();
s
[Mono-devel-list] Assembly Unloading
Hi Zoltan, Now that Sebastien has helped make the security situation clearer, I think unloading assemblies is (hopefully) the last big issue I need to resolve. I've had a look at mono_assembly_close and it looks like it might be OK to just call that to get rid of the assmembly for a script. Referenced assemblies won't be unloaded, but as scripts should only be referencing library assemblies, which can stay loaded, that seams OK. Looking at the other things that mono_domain_free does hightlights some issues which might be more problematic. It seems to go through trashing vtable, class info, static data and jit output hash tables. Presumably if I wanted to unload an assembly I'd need to selectively remove the data relating to the assembly from these hash tables. Is there a way to find out which entries relate to the assembly I want to unload? In the case of LSL assemblies there is no static data, which might make things easier, although there will presumably be class info and jit output. Could I use the mechanisms used by DynamicMethod to manage the collection of JIT output? Would that just leave me class info to clean up? Given that I know which class I want to get rid of would that be easy enough to find? Is this a reasonable approach to take? Is there anything else I need to think about? Should I just use separate domains for each of the (1000s) of scripts? Should I just implement Richard's suggestion of saving the scripts, destroying the domain and then loading the ones I need again to clear out the assemblies and JIT output? Thanks for all your help, Cheers, Jim. ___ How much free photo storage do you get? Store your holiday snaps for FREE with Yahoo! Photos http://uk.photos.yahoo.com ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-devel-list] Tests/System.Xml.Schema/standolone_tests patch
* Makefile : track the timestamp so tar does not run when not needed
* xsdtest.cs : fix the case of the directory name
If no one objects, I'll commit tomorrow
Index: Test/System.Xml.Schema/standalone_tests/xsdtest.cs
===
--- xsdtest.cs (revision 44028)
+++ xsdtest.cs (working copy)
@@ -100,7 +100,7 @@
void RunTest (string subdir)
{
- string basePath = @"Xsd-Test-Suite" + SEP;
+ string basePath = @"xsd-test-suite" + SEP;
XmlDocument doc = new XmlDocument ();
doc.Load (basePath + subdir + SEP + "tests-all.xml");
Index: Test/System.Xml.Schema/standalone_tests/ChangeLog
===
--- ChangeLog (revision 44028)
+++ ChangeLog (working copy)
@@ -1,3 +1,9 @@
+2005-05-08 Andrew Skiba <[EMAIL PROTECTED]>
+
+ * Makefile : track the timestamp so tar does not run when not
+ needed
+ * xsdtest.cs : fix the case of the directory name
+
2004-01-17 Atsushi Enomoto <[EMAIL PROTECTED]>
* Makefile : report details.
Index: Test/System.Xml.Schema/standalone_tests/Makefile
===
--- Makefile(revision 44028)
+++ Makefile(working copy)
@@ -12,18 +12,19 @@
xs-psci-compare.exe : xs-psci-compare.cs
$(MCS_RUNTIME) $(MCS) xs-psci-compare.cs
-$(MASTERS) : $(MASTER_ARCHIVE) xsd-test-suite
- cd xsd-test-suite; tar zxvf ../$(MASTER_ARCHIVE); cd ..
+$(MASTERS) : $(MASTER_ARCHIVE)
+ mkdir xsd-test-suite 2>/dev/null; true
+ cd xsd-test-suite && tar zxvf ../$(MASTER_ARCHIVE)
+ touch $(MASTERS)
-$(TESTS) : $(TEST_ARCHIVE) $(MASTERS) xsd-test-suite
- cd xsd-test-suite; tar zxvf ../$(TEST_ARCHIVE); cd ..
+$(TESTS) : $(TEST_ARCHIVE) $(MASTERS)
+ mkdir xsd-test-suite 2>/dev/null; true
+ cd xsd-test-suite && tar zxvf ../$(TEST_ARCHIVE)
+ touch $(TESTS)
$(TEST_ARCHIVE) :
wget
http://www.w3.org/2001/05/xmlschema-test-collection/XSTC-20020116.tar.gz
-xsd-test-suite:
- mkdir xsd-test-suite
-
run-test :
$(RUNTIME) $(RUNTIME_FLAGS) xsdtest.exe --xml --reportsuccess --testall
--details --report:TestResult.xml $(XSD_TEST_FLAGS)
@echo "SUCCESS: `grep -c \"OK\" TestResult.xml` NORMAL FAILURE: `grep
-c should TestResult.xml` UNEXPECTED `grep -c unexpected TestResult.xml`"
[Mono-devel-list] Test/System.Xml/standalone_tests patch
take care of timestamps to achieve minimal necessary build If no one objects, I will commit Andrew Skiba. Index: ChangeLog === --- ChangeLog (revision 44028) +++ ChangeLog (working copy) @@ -1,3 +1,7 @@ +2005-05-08 Andrew Skiba <[EMAIL PROTECTED]> + + * Makefile : care of timestamps to make a minimal build + 2004-11-08 Atsushi Enomoto <[EMAIL PROTECTED]> * xmltest.cs : reformat; easier to check. Index: Makefile === --- Makefile(revision 44028) +++ Makefile(working copy) @@ -11,15 +11,14 @@ $(MCS_RUNTIME) $(MCS) domdump.cs $(MCS_RUNTIME) $(MCS) eventdump.cs -$(TESTS) : $(TEST_ARCHIVE) xml-test-suite - cd xml-test-suite; unzip -n ../$(TEST_ARCHIVE); cd .. +$(TESTS) : $(TEST_ARCHIVE) + mkdir xml-test-suite 2>/dev/null; true + cd xml-test-suite && unzip -n ../$(TEST_ARCHIVE) + touch $(TESTS) $(TEST_ARCHIVE) : wget http://www.w3.org/XML/Test/xmlts20031210.zip -xml-test-suite: - mkdir xml-test-suite - test : $(RUNTIME) $(RUNTIME_FLAGS) xmltest.exe @@ -37,6 +36,7 @@ xmlreader-result-ms.txt dom-result-ms.txt event-result-ms.txt : unzip -n $(DUMP_RESULTS_ARCHIVE) + touch $@ # be careful to use it. This removes ALL files in xml-test-suite! # clean:
[Mono-devel-list] Signal handlers problem on os x
Hi, I just filed: http://bugzilla.ximian.com/show_bug.cgi?id=74869 I'd like to hear if anyone is going to work on this during the next month or ever? Joachim Ante --- When a null exception is thrown in mono on os x, it will invoke the crashreporter. This is a known bug in os x, where the crashreporter is invoked although there is a null exception signal handler. I filed a bug on this with Apple but they refuse to fix the issue. http://developer.apple.com/technotes/tn2004/tn2123.html (CrashReporter Limitations) The crashreporter will write the crashlog. In the case of a GUI application it will also popup the crashreporter application. In a GUI application this makes people think the application crashed while it actually is still running because mono catched the null exception. So for gui applications this is a real issue. One way to solve this is to use mach-o exception handlers instead of signals: http://www.omnigroup.com/mailman/archive/macosx-dev/2000-June/002030.html I asked Timothy J. Wood if this will make the crashreporter not popup. And he confirmed that it will not pop it up and not write a crashlog. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-devel-list] System.Web.Hosting
Hi Everybody, When using ApplicationHost.CreateApplicationHost, are the values set using AppDomain.SetData the same as on MS.NET? Also, is it possible to host ASP.NET in the same appdomain as the main entry point procedure is ran? Greets, Matthijs BEGIN:VCARD VERSION:2.1 N:ter Woord;Matthijs FN:Matthijs ter Woord ORG:ter Woord Computers ADR;WORK:;;Lindenallee 22;Ellewick-Vreden;;48691;Germany LABEL;WORK;ENCODING=QUOTED-PRINTABLE:Lindenallee 22=0D=0AEllewick-Vreden 48691=0D=0AGermany URL;WORK:http://www.terwoord.nl EMAIL;PREF;INTERNET:[EMAIL PROTECTED] REV:20050508T155809Z END:VCARD
Re: [Mono-devel-list] Some new goodies in Mono.GetOptions
Rafael Teixeira escribió: Hi Knocte see answer inline: On 5/7/05, knocte <[EMAIL PROTECTED]> wrote: Commited to SVN 2005-05-06:2 Rafael Teixeira <[EMAIL PROTECTED]> * Adding Samples directory with mcat Sample (changed main Makefile but didn't add to the SUBDIRS) * Mono.GetOptions/Options.cs, Mono.GetOptions/OptionList An overrideable DefaultArgumentProcessor was added to base class Options that just collects them to the string[] RemainingArguments property as before. It is a virtual method, but it can also be overriden by another method tagged with the ArgumentProcessorAttribute in the derived class to stay binary compatible with old code. * Added Mono.GetOptions/KillOptionAttribute.cs This new attribute permit to hide (kill) an inherited option when overriding the virtual base member. * Added Mono/AdditionalInfoAttribute.cs This new attribute permit to add some extra text at the end of the automatically generated help screen * Added Mono/ReportBugsToAttribute.cs This new attribute adds a "Report bugs to " message at the end of the automatically generated help screen Hello Rafael, thanks for your work. Can this library be used with VS.NET2003 besides Mono? How? Sure, it has no dependencies besides the base framework classes. Just reference the compiled Mono.GetOptions.dll from VS.NET (that normally copies the library to your output directory, and use. If you don't have the setup to compile mono's mcs tree from SVN on your Windows machine, I can send you a compiled dll, just tell me. Note that in my unique "bad timing" style, I just added all those new things a few days after release 1.1.7 was born, so it's VERY unlikely that a packaged version of mono containing the updated library will be available soon. :) Thanks for your answer Rafael. Oh, yes please, send me a DLL if you don't mind. And if you know any small tutorial or reference guide or small example on how to use it, send me also. It would be very appreciated. Regards, Andrés -- ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-devel-list] System.Web.Hosting
On Sun, 2005-05-08 at 17:58 +0200, Matthijs ter Woord (meddochat) wrote: > Hi Everybody, > > When using ApplicationHost.CreateApplicationHost, are the values set using > AppDomain.SetData the same as on MS.NET? They might or might not. Some of them such as appVHost and others are the same thing. > > Also, is it possible to host ASP.NET in the same appdomain as the main entry > point procedure is ran? No. Your application host is created in another domain. That's why it needs to be MarshalByRef. -Gonzalo ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-devel-list] Tests/System.Xml.Schema/standolone_tests patch
Andrew Skiba wrote: (B> * Makefile : track the timestamp so tar does not run when not needed (B> * xsdtest.cs : fix the case of the directory name (B> (B> If no one objects, I'll commit tomorrow (B (BThis patch looks ok. (B (BAtsushi Eno (B___ (BMono-devel-list mailing list (BMono-devel-list@lists.ximian.com (Bhttp://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-devel-list] Test/System.Xml/standalone_tests patch
Andrew Skiba wrote: (B> take care of timestamps to achieve minimal necessary build (B> (B> If no one objects, I will commit (B (BThis patch looks ok too. Thanks. (B (BAtsushi Eno (B___ (BMono-devel-list mailing list (BMono-devel-list@lists.ximian.com (Bhttp://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-devel-list] patch for xslt standalone tests
Andrew Skiba wrote: (B> This patch fixes the following things: (B> (B> * eliminates the need to run xsltproc on catalog.xml to produce (B> catalog-out.xml (B> * fixes the hack that distinguishes between Xalan and Microsoft (B> compliance tests (B> * changes the output of the test: instead of endless scroll of test (B> names now it prints '.' and 'E' if test was passed and exception thrown, (B> respectfully. In the future I will check the expected results and print (B> 'e' if the results are different. (B> (B> If no one objects, I will commit it tomorrow. (B (BIt looks ok, actually the result now looks pretty. Please go ahead. (B (BAtsushi Eno (B___ (BMono-devel-list mailing list (BMono-devel-list@lists.ximian.com (Bhttp://lists.ximian.com/mailman/listinfo/mono-devel-list
