Here's one of the posts from Joshua Allen I was referring to,http://lists.xml.org/archives/xml-dev/200106/msg00552.html
On 10/25/06, M. David Peterson <[EMAIL PROTECTED]> wrote:
Hi Seo,System.Xml is compliant with both DOM Level 1 and Level 2. You can find the the SDK documentation @
http://msdn2
Hi Seo,System.Xml is compliant with both DOM Level 1 and Level 2. You can find the the SDK documentation @ http://msdn2.microsoft.com/en-us/library/system.xml.aspx
In addition, as per the intro into the above linked page,
The System.Xml namespace provides standards-based support for processing
2006/10/25, Sanghyeon Seo <[EMAIL PROTECTED]>:
> Where can I read about W3C Document Object Model Binding for .NET?
>
> http://www.w3.org/DOM/
>
> W3C only defines bindings for Java and ECMAScript.
W3C also defines the interface in OMG IDL, but I can't find anything
about .NET on OMG website, whil
Where can I read about W3C Document Object Model Binding for .NET?
http://www.w3.org/DOM/
W3C only defines bindings for Java and ECMAScript. Python binding is
defined in the Python Library Reference, and linked here:
http://www.w3.org/DOM/Bindings
But I can't find anything about .NET there. Esp
I have made some changes to my pyexpat module for IronPython, and it
can run some simple xml.dom codes now.
https://svn.sourceforge.net/svnroot/fepy/trunk/lib/pyexpat.py
Test cases were written too. It exercises DOM Level 1 constructs
(tagName, getAttribute, childNodes, data) and DOM Level 2 name
Import bugs seem to be especially difficult to reduce the testcase,
since it's often unclear what the hell is going on.
Reduced from some large bunch o' code:
$ ipy test.py
False
$ python test.py
True
File contents follow:
# test.py
import a
print hasattr(a, 'c')
# a/__init__.py
import b
# a/
Great find! I've opened CodePlex bug 4716.
(http://www.codeplex.com/WorkItem/View.aspx?ProjectName=IronPython&WorkItemId=4716).
The problem goes away if you change the name from items = So I suspect
this is a conflict between the name binder & our built-in cache, but I need to
investig
Yep, most definitely doesn't work.I'm happy to rebuild and test as necessary. Let me know if I can be of any help.On 10/24/06, M. David Peterson
<[EMAIL PROTECTED]> wrote:I've run into this on my Mac -- This was a while back, around the time there were various issues being resolved between the Un
