I can take a look when I get home from work, but my C#/.NET experience is ancient, last time I actively used it for anything must have been back in the 2.0 days...
Oh well, a good chance to brush up a bit :) BR, Dennis -----Original Message----- From: Kasper Sørensen [mailto:i.am.kasper.soren...@gmail.com] Sent: 5. september 2017 05:38 To: dev@metamodel.apache.org Subject: Re: Port to C# (DotNet Core) 0.2.0 released and answers to feedback Hi Michel, Thank you for the update on the project :-) I'm definately going to take it for a spin shortly, but just super busy myself at the moment so I can't react as quickly as I'd like. If anyone else has any C# insights and can poke around a bit, I think that would be very valuable! Kasper 2017-08-31 0:36 GMT-07:00 Echopraxium <echoprax...@gmail.com>: > Hello Dev team > > I've just released v 0.2.0 of a 'port to Csharp' prototype, here it is: > https://github.com/Echopraxium/apache_metamodel_dotnet_core_bud > > Now the codebase is big enough (i.e. the 'engine' is ready) which > allows to run the unit tests (via 'MetaModel-cli-test' console app) > but still a lot of validation / debug pending (e.g. in > JsonDataContextTest.testDocumentsOnEveryLineFile() only the first > Assert succeeds). Previously I sais that I applied a "brute force" > and "bottom up" approach. Now I would say that it's more the approach > seems more like porting a legacy codebase. > > I agree with Kasper that a rewrite with CSharp strengths and > weaknesses makes more sense than a "1 to 1 Force Fit". Beyond that > each language brings its own set of "design biases" > with the entropy/negentropy side effect of its idioms. Then my feeling > is that this prototype may hightlight the parts where such 'bias' > occured. > > I just hope that this prototype may raise enough motivation to start a > "dotnet" child project within Apache MetaModel. > > Best Regards > > Michel Kern (echopraxium) >
