Skip to content

CAN_x enums generated in wrong order #19

Description

@equationcrunchor

For example, on MY20:

typedef enum {
	CAN_3,
	CAN_1,
	CAN_2,
	INVALID_BUS
} CAN_Raw_Bus_T;

This doesn't break anything, but it is confusing.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions