Re: [Vtd-xml-users] Problems building vtd-xml C# 2.12

[Jimmy Z. <jz...@xi...>]

The source distribution include a few files not really need to build
the binary lib... 
.flex and .cup are the files that does the flex and xpath parsing
compiler generation... they are the basis for yylexcs and
parser.cs...some of the files like
 .#FuncExpr.cs.1.28 [1].
are old database file for CVS that survived(unfornately) a few rounds
of cleanup 
As to pragma's I am not sure the cause of the problems.yet, at least
my own build does not exhibit such issues.....
All other warning should be safely ignored... 
I will try to look into bundling the C# project files ... was a bit
hesitate on doing so lest it cause back-compatibility issues for old
version of Visual Studios
Overall, C# of vtd-xml is not as well focused as Java version..
next version 2.13 will try to clean things up to meet higher
standards...
Thanks for the input

----- Original Message -----
From: al...@sa...
To:
Cc:
Sent:Thu, 26 May 2016 13:09:22 -0300
Subject:[Vtd-xml-users] Problems building vtd-xml C# 2.12

 Wanted to update my project from 2.11 to 2.12.

 Downloaded the source for vtd-xml 2.12 from sourceforge and tried to
build in VisualStudio 2013 and
 Mono 4.

 The build of vtd-xml 2.12 C# fails for a lot of reasons.

 Here are the issues found trying to build vtd-xml 2.12 from source:
 - There are source code files with a pattern like .#FuncExpr.cs.1.28
[2].
 They do not compile. They appear to be diff or merge results.
 - There are other files with .flex, and .cup file extensions. They
don't appear to be actual source
 code and they don't build.
 - All code with pragma warnings comes up as a build error with
'Unknown Number'. The comments around
 the warnings don't seem correct, so its hard to know what the correct
number should be.
 Have to remove all pragma statements to get the code to compile.
 - Many classes in com.ximpleware.xpath [3] complain that there is 'no
suitable method found to override'
 for the isFinal(), markCacheable(), or clearCache() methods.
 This is very odd because the problem classes extend an abstract class
which does not have the
 aforementioned 3 methods There is no interface, so the abstract
class is even more confusing.
 - It appears that com.ximpleware [4] source is dependent on TUVienna,
which has the same issues with the
 source code as vtd-xml.

 QUESTIONS about building vtd-xml 2.12:

 1. Is the source code supposed to be in this condition? 
 Seems like its not really 'release ready'.
 2. If the C# source won't build without heavy modification, does that
mean it was never tested
 before it was released?
 3. How would you suggest resolving the problem with the xpath
classes? I want my version of vtd-xml
 to match what you intended to release.

 ------------------------------------------------------------------------------
 Mobile security can be enabling, not merely restricting. Employees
who
 bring their own devices (BYOD) to work are irked by the imposition of
MDM
 restrictions. Mobile Device Manager Plus allows you to control only
the
 apps on BYO-devices by containerizing them, leaving personal data
untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j [5]
 _______________________________________________
 Vtd-xml-users mailing list
Vtd...@li... [6]
https://lists.sourceforge.net/lists/listinfo/vtd-xml-users [7]


Links:
------
[1] http://sitemail.hostway.com/http:/
[2] http://sitemail.hostway.com/http:
[3] http://com.ximpleware.xpath
[4] http://com.ximpleware
[5] https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
[6] mailto:Vtd...@li...
[7] https://lists.sourceforge.net/lists/listinfo/vtd-xml-users