Project

Profile

Help

Source code for Saxon HE .NET 10.8 missing class Feature<T>?

Added by Martin Honnen over 1 year ago

For Saxon HE 10(.8) .NET, there is a documented class public class Feature<T> https://www.saxonica.com/html/documentation10/dotnetdoc/Saxon/Api/Feature.html.

When I download the Saxon C# source for 10.8 from Sourceforge, I don't find the source code for that class Feature<T>, as far as I have searched and VS tell me when loading all files.

In which source file should it be defined/contained? It is used/referenced in Configuration.cs in the methods public void SetProperty<T>(Feature<T> feature, T value) and public T GetProperty<T>(Feature<T> feature) { but for some reasons I don't find Feature<T> in the source code.


Replies (3)

Please register to reply

RE: Source code for Saxon HE .NET 10.8 missing class Feature<T>? - Added by Martin Honnen over 1 year ago

Trying to understand why the file might be missing or where it can be found I have run into a build script and https://saxonica.plan.io/projects/saxonmirrorhe/repository/he/revisions/he-saxon10_6/entry/build-n.gradle#L39 which seems to suggest two C# classes Saxon.Api/Feature.cs and Saxon.Api/FeatureKeys.cs are generated with XSLT from an input file featureKeys/FeatureKeys.xml.

Is that lack of those generated files in the source release simple an omission to copy the generated files into the source folder before zipping?

RE: Source code for Saxon HE .NET 10.8 missing class Feature<T>? - Added by Michael Kay over 1 year ago

Indeed, these are generated files rather than true source files, which is why they are not under change control in the repository.

For SaxonJ we've always tried to package up the source-code-after-preprocessing to make it easier for people to build the product for source, but I'm not sure we've ever done that for Saxon on .NET.

I've attached versions of the two files in case it helps.

RE: Source code for Saxon HE .NET 10.8 missing class Feature<T>? - Added by Norm Tovey-Walsh over 1 year ago

Saxonica Developer Community writes:

For SaxonJ we've always tried to package up the
source-code-after-preprocessing to make it easier for people to build
the product for source, but I'm not sure we've ever done that for
Saxon on .NET.

It is supposed to be the case that if you check out the HE repository,
you can build (including generating the files if necessary). But that’s
possibly not well tested. Certainly, I haven’t personally tested it
recently.

Be seeing you,
norm

--
Norm Tovey-Walsh
Saxonica

    (1-3/3)

    Please register to reply