Proposal - additional symbology for VB6 and TwinBasic compatibility?

[sancarn]

Options

1. Seperate awesome-vb6 and awesome-twinbasic
2. Allow VB6/TB projects onto awesome-vba given certain conditions

If 2 what should those conditions be?

VB6

• Many VB6 solutions compatible with VBA given certain constraints.
• VB6 solutions which aren't compatible with VBA can often be quickly ported to VBA specific examples.

TwinBasic

• TwinBasic is "the future" as it were.
• TwinBasic may be of interest to VBA developers given it's compatibility arc.
• Some TwinBasic solutions are 100% backward compatible with VBA
• Incompatible TwinBasic solutions may be harder to port than typical VB6 solutions due to new syntax sugar.

Might want to discuss with Wayne about the best abstraction for this if at all. Does it make sense to be an application flag?