{"id":215,"date":"2011-02-11T15:49:19","date_gmt":"2011-02-11T15:49:19","guid":{"rendered":"http:\/\/www.ericwhite.com\/home2\/bm8qcmjy\/public_html\/blog\/?p=215"},"modified":"2011-02-24T22:57:08","modified_gmt":"2011-02-24T22:57:08","slug":"simulating-virtual-extension-methods","status":"publish","type":"post","link":"https:\/\/www.ericwhite.com\/blog\/2011\/02\/11\/simulating-virtual-extension-methods\/","title":{"rendered":"Simulating Virtual Extension Methods"},"content":{"rendered":"

When considering the problem of how to generate code that will create some arbitrary XML tree, it is interesting to examine the LINQ to XML class hierarchy, which uses polymorphism. The XObject<\/a> class is an abstract base class of both the XAttribute<\/a> and XNode<\/a> classes. The XNode class is an abstract base class of XContainer<\/a>, XComment<\/a>, XDocumentType<\/a>, XProcessingInstruction<\/a>, and XText<\/a>. XContainer is the base class for XElement<\/a> and XDocument<\/a>.<\/p>\n

This post is the sixth in a series of blog posts. Here is the complete list: Generating Open XML WordprocessingML Documents Blog Post Series<\/a><\/p>\n

The following diagram shows the class hierarchy of the LINQ to XML classes that are important when considering serializing a LINQ to XML tree as code. There are other classes in LINQ to XML, but they don\u2019t impact this discussion.<\/p>\n

\"Image1\"<\/a><\/p>\n

Software systems such as LINQ to XML are typically written using a recursive approach. The XNode class has an abstract virtual method WriteTo. Each derived class must override the WriteTo method and provide its own method for serializing. When serializing an XElement object by calling WriteTo, internally, LINQ to XML calls the WriteTo method for each of the child nodes of the XElement object. This is the approach that we want to use when generating code to create an arbitrary XML tree.<\/p>\n

What would be ideal is to write \u2018Virtual Extension Methods\u2019. There would be an abstract virtual extension method for XObject named ToCode. This extension method would be overridden in each of the concrete classes. Classes that include child objects, such as XElement and XDocument can then iterate through their children and use the virtual extension method to convert each node in the XML tree to the appropriate C# code to create the node.<\/p>\n

However, C# does not include support for the idea of a virtual extension method. When you call an extension method, it is bound at compile time to an extension method based on the type of the variable, not based on the type of the object in the variable. To show exactly what I mean, consider the following snippet:
\n
\npublic static class MyExtensions
\n{
\n    public static string ToCode(this XObject o)
\n    {
\n        return \"Called extension method on XObject\";
\n    }<\/p>\n

    public static string ToCode(this XElement e)
\n    {
\n        return \"Called extension method on XElement\";
\n    }
\n}<\/p>\n

class Program
\n{
\n    static void Main(string[] args)
\n    {
\n        XElement e = new XElement(\"Root\");
\n        Console.WriteLine(e.ToCode());
\n        XObject o = e;
\n        Console.WriteLine(o.ToCode());
\n    }
\n}
\n<\/code><\/p>\n

The above snippet calls the ToCode extension method twice for the same object. However, even though the type of the object is XElement, when the object is assigned to a variable with type XObject (which is valid because XElement is derived from XNode, which derives from XObject), and the program calls the ToCode extension method, the extension method on XElement is not called. Instead, the extension method on XObject is called.<\/p>\n

Because the LINQ to XML programming interface is fairly simple, we can simulate virtual extension methods by implementing an extension method on XObject that simply dispatches to the appropriate extension method based on the actual type of the object. The following listing shows the implementation of the ToCode extension method for XObject.
\n
\npublic static string ToCode(this XObject xObject)
\n{
\n    XAttribute a = xObject as XAttribute;
\n    if (a != null)
\n        return a.ToCode();
\n    XElement element = xObject as XElement;
\n    if (element != null)
\n        return element.ToCode();
\n    XCData cdata = xObject as XCData;
\n    if (cdata != null)
\n        return cdata.ToCode();
\n    XText text = xObject as XText;
\n    if (text != null)
\n        return text.ToCode();
\n    XComment comment = xObject as XComment;
\n    if (comment != null)
\n        return comment.ToCode();
\n    XProcessingInstruction pi = xObject as XProcessingInstruction;
\n    if (pi != null)
\n        return pi.ToCode();
\n    throw new CodeGenerationException(\"Internal error\");
\n}
\n<\/code><\/p>\n

Next, we can examine the ToCode method that is implemented on XAttribute. The code calls an Indentation method that determines the number of spaces to precede the \u2018new XAttribute\u2019. This enables the code to be properly indented, so that it is easy to examine the generated code. Other than this, it is pretty straightforward code to generate the code to new up an XAttribute object.
\n
\npublic static string ToCode(this XAttribute attribute)
\n{
\n    return Indentation(attribute) +
\n        String.Format(\"new XAttribute(\\\"{0}\\\", \\\"{1}\\\"),\" + Environment.NewLine,
\n        attribute.Name, attribute.Value);
\n}
\n<\/code><\/p>\n

As initially written, the generated code to create an XAttribute or XElement object includes appending the comma before the new line.\u00a0 One minor issue that must be solved is that when passing a number of parameters to a function that takes a params array, a comma immediately before the closing parenthesis is invalid.<\/p>\n

\"Image2\"<\/a><\/p>\n

The approach I took to solve this problem is that after assembling all of the code to create the child nodes of an XElement object, the code calls a method to trim off the final comma.
\n
\npublic static string ToCode(this XElement element)
\n{
\n    var c = element.Attributes().Cast<XObject>().Concat(element.Nodes().Cast<XObject>());
\n    if (c.Count() == 0)
\n        return Indentation(element) +
\n            String.Format(\"new XElement(\\\"{0}\\\"),\" + Environment.NewLine, element.Name);
\n    else
\n        return Indentation(element) +
\n            String.Format(\"new XElement(\\\"{0}\\\",\" + Environment.NewLine, element.Name) +
\n            TrimFinalComma(c.Select(n => n.ToCode()).StringConcatenate()) +
\n            Indentation(element) + \"),\" + Environment.NewLine;
\n}
\n<\/code><\/p>\n

TrimFinalComma looks like this:
\n
\nprivate static string TrimFinalComma(string code)
\n{
\n    if (code.EndsWith(\",\" + Environment.NewLine))
\n        return code.Substring(0, code.Length - (\",\" + Environment.NewLine).Length) +
\n            Environment.NewLine;
\n    return code;
\n}
\n<\/code><\/p>\n

You can see the rest of the ToCode extension methods in Generating C# code from an XML Tree using Virtual Extension Methods<\/a>.<\/p>\n

One Final Note<\/h1>\n

Some people will recognize the similarity in functionality between the Paste XML as LINQ<\/a> sample and the code presented in this and the last post.\u00a0 The code presented in the Paste XML as LINQ sample is imperative code that iterates through the nodes outputting code.\u00a0 I need a completely different structure for my code.\u00a0 By coding as a recursive functional transform, I can easily alter the transform as appropriate for special purpose content controls that contain C#.<\/p>\n","protected":false},"excerpt":{"rendered":"

Discusses how I similated ‘virtual extension methods’ to write code to generate code to create an arbitrary XML tree.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_bbp_topic_count":0,"_bbp_reply_count":0,"_bbp_total_topic_count":0,"_bbp_total_reply_count":0,"_bbp_voice_count":0,"_bbp_anonymous_reply_count":0,"_bbp_topic_count_hidden":0,"_bbp_reply_count_hidden":0,"_bbp_forum_subforum_count":0,"_s2mail":"","footnotes":""},"categories":[7,8,3,5],"tags":[],"class_list":["post-215","post","type-post","status-publish","format-standard","hentry","category-document-generation-series","category-functional-programming","category-open-xml","category-wordprocessingml"],"_links":{"self":[{"href":"https:\/\/www.ericwhite.com\/blog\/wp-json\/wp\/v2\/posts\/215","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.ericwhite.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.ericwhite.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.ericwhite.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.ericwhite.com\/blog\/wp-json\/wp\/v2\/comments?post=215"}],"version-history":[{"count":10,"href":"https:\/\/www.ericwhite.com\/blog\/wp-json\/wp\/v2\/posts\/215\/revisions"}],"predecessor-version":[{"id":255,"href":"https:\/\/www.ericwhite.com\/blog\/wp-json\/wp\/v2\/posts\/215\/revisions\/255"}],"wp:attachment":[{"href":"https:\/\/www.ericwhite.com\/blog\/wp-json\/wp\/v2\/media?parent=215"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.ericwhite.com\/blog\/wp-json\/wp\/v2\/categories?post=215"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.ericwhite.com\/blog\/wp-json\/wp\/v2\/tags?post=215"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}