I agree with Stef, do not be afraid to put it out there.
Nobody else knows your exact situation and hence the decisions you had to make to get to a certain design or implementation. Nobody is perfect. Worse things have been released but are still useful.
<rant>Look for example at the design of Roslyn. That thing is so hard to use and it's so unclear why things go wrong when they do. Yet it's supposed to be built by people who know very well what they are doing. Good luck if you want to
use it and get it to work 100%. I still have some cases where it cannot give me receiver type information even though it is trivial to deduce (and visual studio does it without problems).</rant>
--
Johan Fabry,
Senior Software Engineer.
johan@raincode.com | Email too brief? Here's why! http://emailcharter.org
From: Moose-dev [mailto:moose-dev-bounces@list.inf.unibe.ch]
On Behalf Of Stéphane Ducasse
Sent: Wednesday, May 16, 2018 10:20 PM
To: Moose-related development <moose-dev@list.inf.unibe.ch>
Subject: [Moose-dev] Re: C# importer ?
Hi thomas
Do the best that you can.
Now you see if you open-source a badly implemented solution (and say to the guys that it is in bad shape then we know it), people in need may even do a pass on it.
This is not like certain tools full of getClass.equal() everywhere that pretend that this is the correct design :) They believe that they know object-oriented programming.
We are waiting that Synectique situation clarifies (it will probably die) and from that day we will open-source everything we did.
The C++, C importers are already open-source and we should structure the moose git repo.
Stef