AW: [xsde-users] c++/Hybrid: element names and line numbers

[Christian Sell]

I just looked at our code base and have to conclude that moving to XSD is a
non-option, given all the dependencies on XSD/e classes and APIs.

Hacking may be an option.  I just wonder why there isn't flexibility to
implement this in a clean way. Since the XSD/e Parser is event-driven, it
should have access to everything. And the XSD/e Hybrid name sounds as if
there was a lower event-driven layer into which one could kick down..

-----Ursprüngliche Nachricht-----
Von: Boris Kolpackov [mailto:boris at codesynthesis.com] 
Gesendet: Donnerstag, 22. Januar 2015 16:41
An: Christian Sell
Cc: xsde-users at codesynthesis.com
Betreff: Re: [xsde-users] c++/Hybrid: element names and line numbers

Hi Christian,

Christian Sell <christian at gsvitec.com> writes:

> We have a large dependency on XSD(/e) at development time for code 
> generation, and some at runtime. We could move (back, argh!) to XSD 
> for the development part, and stick with XSD/e for the runtime. We 
> just wanted to avoid having to maintain 2 tools.

Yes, that sounds hairy. If you only need access to this information during
development, then maybe your could hack something up directly in libxsde?
Maybe store this information in a global variable or some such?

Boris