Skip to content

Split result of make_opcodes by extensions #3

@x87

Description

@x87

After sannybuilder/dev#74 it's unclear where to save the list of commands extracted from a source with multiple extensions. Each extension owns their own opcodes.txt.

Short-term: overwrite default''s opcodes.txt
Long-term: analyze commands and sort them by extensions. Make separate opcodes.txt for each extensions and save into appropriate locations. Requires providing extensions information (currently known as extensions.txt) into make_opcodes

Originally posted by @x87 in sannybuilder/dev#14 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions