Emit commented ScriptSharp code when converter cannot handle a given code construct

[guidoren]

When the converter hits a construct that it cannot translate, it throws errors. Consider to emit the original source instead as commented code. You can add //TODO: convert this as well.

That way, the result may not be a fully converted TypeScript file, but at least you would have a skeleton to work with.

[andry-tino]

This will be treated as a MUST for the release of the code converter.

Priority

Due to urgent work to be completed on the ScriptSharp definition generation, this feature will be done after completing the milestone concerning the former.

Effort estimation

Effort should be medium. This feature was not thought of. Impacted areas:

• AST Walkers and Translation Units are impacted.
• Design required. Should we do this in ITranslationUnits or in ASTWalkers?
• Possibility to create a separate component for carrying nodes to output as they are in commented flavor, thus might be possible to restrict this to ASTWalkers only.