@serkonda7 since you re-opened this issue, I'm assuming that you'd be interested in adding VB6 support.

I can help, but I would need to know which option you want to use as discussed in my previous comment:

Interesting option. In the case of VBA and VB6, if we adopt the same logic, it would be VB6's grammar that would be included in VBA's grammar.

However, I think that if we want to keep things simple, a solution for someone using the VS code extension for VB6 is simply to add VBA as the language mode for the file extensions .Dsr and .ctl.

Option A:
VBA's grammar is an extension of VB6 (VB Classic)'s grammar.
Harder to implement since we would need to edit the VBA grammar to keep only elements specific to VBA not present in VB6.

%%{init: {'theme':'neutral'}}%%
graph TD
    A[source.wwb]
    B[source.vba]
    C[source.vb6]

    A -- includes --> B
    B -- includes --> C

Option B (Simpler approach):
VB6 extensions are simply supported using source.vba (indirectly).
The only element in the vb6 grammar would be:

scopeName: source.vb6
fileTypes:
  - .Dsr
  - .ctl

patterns:
  - include: source.vba

This approach is simple and considering that the differences between VBA and VB6 are minor, it seems like the most cost-effective way to get highlighting for VB6. The only downside is that it would highlight a few expressions inside VB6 that are not actually valid.

%%{init: {'theme':'neutral'}}%%
graph TD
    A[source.wwb]
    B[source.vba]
    C[source.vb6]

    A -- includes --> B
    C -- includes --> B

Uh oh!

Add VB6 highlighting (.ctl files) based on the VBA syntax #74

Description

Describe the feature

Proposed Solution

Additional Information

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions