代码之家  ›  专栏  ›  技术社区  ›  jedmao

如何将IDL翻译成C#?

  •  3
  • jedmao  · 技术社区  · 16 年前

    例如 DOM specification IDL definitions ,其中之一是 Interface Node . 你会如何把这一部分翻译成实际的C?我是说,你从哪里开始?据我所知,C#的接口的行为与IDL在这里调用的接口有很大的不同。我错了吗?

    interface Node {
    
      // NodeType
      const unsigned short      ELEMENT_NODE                   = 1;
      const unsigned short      ATTRIBUTE_NODE                 = 2;
      const unsigned short      TEXT_NODE                      = 3;
      const unsigned short      CDATA_SECTION_NODE             = 4;
      const unsigned short      ENTITY_REFERENCE_NODE          = 5;
      const unsigned short      ENTITY_NODE                    = 6;
      const unsigned short      PROCESSING_INSTRUCTION_NODE    = 7;
      const unsigned short      COMMENT_NODE                   = 8;
      const unsigned short      DOCUMENT_NODE                  = 9;
      const unsigned short      DOCUMENT_TYPE_NODE             = 10;
      const unsigned short      DOCUMENT_FRAGMENT_NODE         = 11;
      const unsigned short      NOTATION_NODE                  = 12;
    
      readonly attribute DOMString       nodeName;
               attribute DOMString       nodeValue;
                                            // raises(DOMException) on setting
                                            // raises(DOMException) on retrieval
    
      readonly attribute unsigned short  nodeType;
      readonly attribute Node            parentNode;
      readonly attribute NodeList        childNodes;
      readonly attribute Node            firstChild;
      readonly attribute Node            lastChild;
      readonly attribute Node            previousSibling;
      readonly attribute Node            nextSibling;
      readonly attribute NamedNodeMap    attributes;
      // Modified in DOM Level 2:
      readonly attribute Document        ownerDocument;
      // Modified in DOM Level 3:
      Node               insertBefore(in Node newChild, 
                                      in Node refChild)
                                            raises(DOMException);
      // Modified in DOM Level 3:
      Node               replaceChild(in Node newChild, 
                                      in Node oldChild)
                                            raises(DOMException);
      // Modified in DOM Level 3:
      Node               removeChild(in Node oldChild)
                                            raises(DOMException);
      // Modified in DOM Level 3:
      Node               appendChild(in Node newChild)
                                            raises(DOMException);
      boolean            hasChildNodes();
      Node               cloneNode(in boolean deep);
      // Modified in DOM Level 3:
      void               normalize();
      // Introduced in DOM Level 2:
      boolean            isSupported(in DOMString feature, 
                                     in DOMString version);
      // Introduced in DOM Level 2:
      readonly attribute DOMString       namespaceURI;
      // Introduced in DOM Level 2:
               attribute DOMString       prefix;
                                            // raises(DOMException) on setting
    
      // Introduced in DOM Level 2:
      readonly attribute DOMString       localName;
      // Introduced in DOM Level 2:
      boolean            hasAttributes();
      // Introduced in DOM Level 3:
      readonly attribute DOMString       baseURI;
    
      // DocumentPosition
      const unsigned short      DOCUMENT_POSITION_DISCONNECTED = 0x01;
      const unsigned short      DOCUMENT_POSITION_PRECEDING    = 0x02;
      const unsigned short      DOCUMENT_POSITION_FOLLOWING    = 0x04;
      const unsigned short      DOCUMENT_POSITION_CONTAINS     = 0x08;
      const unsigned short      DOCUMENT_POSITION_CONTAINED_BY = 0x10;
      const unsigned short      DOCUMENT_POSITION_IMPLEMENTATION_SPECIFIC = 0x20;
    
      // Introduced in DOM Level 3:
      unsigned short     compareDocumentPosition(in Node other)
                                            raises(DOMException);
      // Introduced in DOM Level 3:
               attribute DOMString       textContent;
                                            // raises(DOMException) on setting
                                            // raises(DOMException) on retrieval
    
      // Introduced in DOM Level 3:
      boolean            isSameNode(in Node other);
      // Introduced in DOM Level 3:
      DOMString          lookupPrefix(in DOMString namespaceURI);
      // Introduced in DOM Level 3:
      boolean            isDefaultNamespace(in DOMString namespaceURI);
      // Introduced in DOM Level 3:
      DOMString          lookupNamespaceURI(in DOMString prefix);
      // Introduced in DOM Level 3:
      boolean            isEqualNode(in Node arg);
      // Introduced in DOM Level 3:
      DOMObject          getFeature(in DOMString feature, 
                                    in DOMString version);
      // Introduced in DOM Level 3:
      DOMUserData        setUserData(in DOMString key, 
                                     in DOMUserData data, 
                                     in UserDataHandler handler);
      // Introduced in DOM Level 3:
      DOMUserData        getUserData(in DOMString key);
    };
    
    1 回复  |  直到 16 年前
        1
  •  6
  •   Abel    16 年前

    背景

    对于几乎所有的IDL命令,在C#中都有相同的可能性,尽管并不总是在just-in接口中。COM的基本接口总是 IUknown

    在演讲中,当谈到COM接口时,通常会谈到实现。在c#中,您通常谈论调用方和实现方理解的空契约。

    翻译IDL

    如上所述,上面的IDL是DOM的。DOM是用C实现的,比它的COM同类(以及许多版本)强大得多。如果确实要创建一个可以调用COM DOM接口的C类包装器:

    • 然后运行tlbimp.exe(与.NET一起提供)创建一个.NET COM包装器,您可以将其包含在项目中。

    也可以直接在COM DLL(进程中)或可执行文件(进程外)上运行tlbimp.exe来创建.NET COM包装器。

    更多信息

    一个基本的,但极其辉煌和全面的介绍COM是唐盒的名著 Essential COM ,关于IDL,我建议 Essential IDL by Gudgin .

    当然,关于COM和.NET的所有知识都写在了一本综合性的,但略显臃肿的, .NET and .COM The Complete Interoperability Guide

    推荐文章