[xsd-users] XSD C++17 Support

[Schrader, Glenn - 1002 - MITLL]

I would argue against dropping c++98. There are some compiler vendors (in the embedded space) with no plans to advance beyond that standard.

-----Original Message-----
From: xsd-users-bounces at codesynthesis.com <xsd-users-bounces at codesynthesis.com> On Behalf Of Boris Kolpackov
Sent: Friday, February 15, 2019 9:13 AM
To: Corey Barnwell <barnwell9 at gmail.com>
Cc: xsd-users at codesynthesis.com
Subject: Re: [xsd-users] XSD C++17 Support

Corey Barnwell <barnwell9 at gmail.com> writes:

> Are there any plans for adding C++17 support to XSD? Seems to be 
> riddled with auto_ptr usage.

>From the NEWS file entry for the 4.0.0 release:

  * New option, --std, specifies the C++ standard that the generated code
    should conform to. Valid values are c++98 (default) and c++11.

    The C++ standard affects various aspects of the generated code that are
    discussed in more detail in mapping-specific documentation (guides and
    manuals). Overall, when C++11 is selected, the generated code relies on
    the move semantics and uses std::unique_ptr instead of deprecated
    std::auto_ptr. See also the documentation for the --std option in the
    XSD compiler command line manual (man pages).

Though it's probably time to make c++11 the default (or maybe even drop
c++98 entirely).


> Or is XSD a dead project? I noticed it doesn't seem to have been 
> updated since 2014.

It's a mature project that is in the maintenance mode. But a release is long overdue, that's true. You can try the latest pre-release if you are
interested:

https://codesynthesis.com/~boris/tmp/xsd/4.1.0.a11/