Re: [PATCH 0/3] argparse: improve handling of multi-instance args

2025-06-27 Thread Thomas Monjalon
27/06/2025 11:53, Bruce Richardson: > On Fri, Jun 20, 2025 at 09:44:15AM +0100, Bruce Richardson wrote: > > On Mon, Jun 16, 2025 at 11:49:40AM +0100, Bruce Richardson wrote: > > > Coverity (correctly) identified an issue[1] where, after the recent > > > rework[2], the internal flag, used by argpars

Re: [PATCH 0/3] argparse: improve handling of multi-instance args

2025-06-27 Thread Bruce Richardson
On Fri, Jun 20, 2025 at 09:44:15AM +0100, Bruce Richardson wrote: > On Mon, Jun 16, 2025 at 11:49:40AM +0100, Bruce Richardson wrote: > > Coverity (correctly) identified an issue[1] where, after the recent > > rework[2], the internal flag, used by argparse to track what arguments > > were previousl

Re: [PATCH 0/3] argparse: improve handling of multi-instance args

2025-06-24 Thread Bruce Richardson
On Mon, Jun 16, 2025 at 11:49:40AM +0100, Bruce Richardson wrote: > Coverity (correctly) identified an issue[1] where, after the recent > rework[2], the internal flag, used by argparse to track what arguments > were previously encountered or not, was out of range for the type and no > longer having

Re: [PATCH 0/3] argparse: improve handling of multi-instance args

2025-06-20 Thread Bruce Richardson
On Mon, Jun 16, 2025 at 11:49:40AM +0100, Bruce Richardson wrote: > Coverity (correctly) identified an issue[1] where, after the recent > rework[2], the internal flag, used by argparse to track what arguments > were previously encountered or not, was out of range for the type and no > longer having

[PATCH 0/3] argparse: improve handling of multi-instance args

2025-06-16 Thread Bruce Richardson
Coverity (correctly) identified an issue[1] where, after the recent rework[2], the internal flag, used by argparse to track what arguments were previously encountered or not, was out of range for the type and no longer having any effect. Fixing this flag to be back into range then, somewhat surpris