[Soot-list] Soot release

[Marc-Andre Laverdiere-Papineau]

Hello,

This is my software engineering side that is showing here - soot is 
already very big, so any duplicate functionality is good to remove.

It doesn't help software comprehension either. I recall as a noob (which 
I still am, BTW, only slightly less than before) at first, wondering 
"What in the world is Polyglot??? What should I use?"

Also, we have a dependency on an unmaintained package, which translates 
to me as "disaster waiting to happen".

I also understand that nobody wants make our users suffer either - so we 
sort of have to keep it as long as someone will want to use it.

I think deprecation is the right way to go short term. Maybe we can had 
some output like the following?

** WARNING WARNING  you are using the Polyglot front-end, which is 
deprecated. Please consider using the JastAddJ front-end

Regards,

Marc-André Laverdière-Papineau
Doctorant - PhD Candidate

On 13-01-15 02:25 AM, Eric Bodden wrote:
> Hi Marc-Andre.
>
>> So one possibility is that some projects would depend on the Polyglot
>> AST - maybe some rewriting of some kind?
>
> Yes, such tools do exist.
>
>> If that is the case, then we have to keep this component working
>> forever. But I would like to have their maintainers confirming that need.
>
> I would be ok with marking the support as deprecated, though,
> discouraging people to still build on it in the future.
>
> I am not quite clear what your motivation is for removing polyglot
> anyway. It's true that our polyglot-related code is old and in some
> parts buggy but it did not seem to hurt much over the past few years.
> Did you encounter any problems with it?
>
> Eric
>