Skip to content

Proposal - additional symbology for VB6 and TwinBasic compatibility? #47

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
sancarn opened this issue May 17, 2025 · 0 comments
Open

Proposal - additional symbology for VB6 and TwinBasic compatibility? #47

sancarn opened this issue May 17, 2025 · 0 comments

Comments

@sancarn
Copy link
Owner

sancarn commented May 17, 2025

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?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sancarn