RFC: Flag parsing

[BogdanTheGeek]

DO NOT MERGE!!!!!
Draft attempt at a new flag parsing methodology. Currently it has the following known limitations:

• no combined args: -3tb
• order is not retained (-a -b == -b -a)
• not all flags have been implemented with new method, fallbacks to old method

Things gained:

• aliases: -help | -h
• usage() is updated automatically (there were quite a few flags missing)
• variables as flags
• defaults

[cnlohr]

I do have a strong preference for maintaining order, because sometimes I do personally sequence things, especially surrounding unbricking, etc. I.e. applying power doing X removing power.

Also, I really wish we had long-arguments.

[BogdanTheGeek]

We can define multiple arguments that point to the same variable, like -h/-help.

…

On Mon, 3 Nov 2025, 19:50 cnlohr, ***@***.***> wrote: *cnlohr* left a comment (cnlohr/ch32fun#732) <#732 (comment)> I do have a strong preference for maintaining order, because sometimes I do personally sequence things, especially surrounding unbricking, etc. I.e. applying power doing X removing power. Also, I really wish we had long-arguments. — Reply to this email directly, view it on GitHub <#732 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACDKK6UE3EWLVDZSB7ZFEND326PYZAVCNFSM6AAAAACKTCC4EKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTIOBSGI2TIMRYG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[cnlohr]

@monte-monte @BogdanTheGeek @dwillmore is there any hope for us to fix flags in minichlink?

I think we have to have --long-parameters

[cnlohr]

This branch is no longer compatible btw