On Wed, 18 Sep 2013, Nicolas Cellier wrote:

> After my late changes, it is now possible to interact with a SyntaxError and manually correct source code in the MC loading/merging process.
> Maybe the package won't be marked dirty as it should be, but it already is something...
> I wanted to favour correction of code over workaround for keeping a statu quo.
> So I did not propose yet any change of Preferences/settings.
> If many methods are incorrect, the manual change will be too teddious, and won't be of much help.
> IMO, the preferences change can come later by analyzing the kind of error and proposing some alternative actions thru the pop up menu, or other means (a line of buttons...).
> Better could be an automatic correction (if it ALWAYS works, or at least knows when it works, there is nothing worse than automatic actions that sometimes work, sometimes don't...)

This is already a great improvement, but I think the best would be if 
there were a way to see which methods/classes won't compile, and need 
fixing.


Levente