[Mono-bugs] [Bug 74279][Wis] Changed - XML parsing Bug in MiniParser

[bugzilla-daemon@bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by sebastien@ximian.com.

http://bugzilla.ximian.com/show_bug.cgi?id=74279

--- shadow/74279	2005-04-08 18:11:40.000000000 -0400
+++ shadow/74279.tmp.5465	2005-04-08 18:21:11.000000000 -0400
@@ -148,6 +148,31 @@
 2) rewrite the security parser to work with another xml parser
 (System.Xml.Document)
 
 But as you said the Miniparser is a really nice small parser that can
 be used to write own specific parsers. I think i bad to get rid of the
 MiniParser.
+
+------- Additional Comments From sebastien@ximian.com  2005-04-08 18:21 -------
+Option #1 (fixing MiniParser) *may* be required for 2.0 - but I still
+have no proof that 2.0 requires mixed content XML. If it doesn't then
+MiniParser won't change (or at least I won't be the one making the
+changes).
+
+
+Option #2 isn't possible. That would requires mscorlib.dll to have a
+dependency on System.Xml.dll (which already depends on mscorlib.dll).
+The class SecurityElement exists in corlib for that very reason.
+
+Even if we could compile it this would also slow down all applications
+because the SecurityParser is used in many place in the security
+runtime. That would requires to load/jit System.Xml.dll (which also
+depends on System.dll)... and then if you have System.Xml handy why
+not use it directly in the first place ?
+
+
+Finally I don't intend to "get rid" of MiniParser ever ;-). I'm unsure
+where you got that feeling.
+
+
+Note: leaving bug OPEN as NEEDINFO as I'm still unsure if a fix will
+be required for 2.0.