Update upstream source from tag 'upstream/4.2.0'

Update to upstream version '4.2.0'
with Debian dir 1b38df7bbcf313223de3c50107ac0255090fe647

1 files changed, 0 insertions, 45 deletions

diff --git a/xsd/examples/cxx/tree/mixed/README b/xsd/examples/cxx/tree/mixed/README
deleted file mode 100644
index fc23faa..0000000
--- a/xsd/examples/cxx/tree/mixed/README
+++ /dev/null
@@ -1,45 +0,0 @@
-This example shows how to access the underlying DOM nodes in the
-C++/Tree mapping in order to handle raw, "type-less content" such
-as mixed content models, anyType/anySimpleType, and any/anyAttribute.
-
-For an alternative (and recommended) approach that employs ordered
-types see the order/mixed example.
-
-For an alternative approach that employes type customization see
-examples in the custom/ directory, in particular, custom/mixed and
-custom/wildcard.
-
-In this example we use mixed content model to describe text with
-embedded links, e.g.,
-
-  This paragraph talks about <a href="uri">time</a>.
-
-The example transforms such text into plain text with references, e.g.,
-
-  This paragraph talks about time[0].
-
-  [0] uri
-
-The example consists of the following files:
-
-text.xsd
-  XML Schema which describes "text with links" instance documents.
-
-text.xml
-  Sample XML instance document.
-
-text.hxx
-text.cxx
-  C++ types that represent the given vocabulary and a set of parsing
-  functions that convert XML instance documents to a tree-like in-memory
-  object model. These are generated by XSD from text.xsd.
-
-driver.cxx
-  Driver for the example. It first calls one of the parsing functions
-  that constructs the object model from the input file. It then uses
-  both the underlying DOM and statically-typed mapping to perform the
-  transformation.
-
-To run the example on the sample XML instance document simply execute:
-
-$ ./driver text.xml