Skip to content

Why were specific built-in parsers per read -m removed? #994

@takusuman

Description

@takusuman

I was thinking more recently on this matter.
Why was the JSON parser dropped? I remember it having some bugs and crashes, it wasn't stable, but was it really difficult to fix?
I can imagine the .ini parser being a little bit "crude" and not supporting some variations in the format, but I haven't tested it.
If one put effort into fixing these, would they be merged again?

This is just a couple of questions, not actually an issue with this project. It's just because I think it would be fairly interesting to have built-in JSON in the Korn Shell instead of parsing it manually --- I even tried it once --- or using jq, which is an external binary and will be obviously slower.

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