Il giorno mer 18 mar 2020 alle ore 13:07 David Kastrup <d...@gnu.org> ha 
scritto:
> It doesn't make sense to have convert-ly produce non-working code for
> version 2.19.40 .  And convert-ly cannot promise to fix code that never
> worked due to its combination of version statement and old syntax.
>
> It isn't guaranteed that you can run convert-ly multiple times for the
> same version range without producing invalid code.

Would it make sense to have the rule twice, once for the correct
version and once for post-2.20.0?
That would produce working code for 2.19.40, while also taking care of
files that were diligently converted with convert-ly up to 2.20.0 (the
invalid code in those files is not the user's error but convert-ly's).
Of course provided that the applying the rule twice doesn't ruin the code.

Davide

Reply via email to