Skip to content

Better handling of NoParser option #12

@bbengfort

Description

@bbengfort

The NoParser option is intended to allow users to define their own parser function, however it is required that users define it since the parser is used in the generated functions. So … what do we do if the user hasn't defined it?

One way to make this more clear is to have a ParserFunc option that must be set if NoParser is true -- this specifies the name of the Parser function symbol that we use in the other functions.

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