On 6/6/19 1:32 PM, Martin Sebor wrote:
> Hi Jeff,
>
> It looks like the updated comment for get_range_strlen didn't make
> it into the strlen fixup commits last December and the function
> still has the old description. (Not surprising given there are
> at least two overloads of the same function
On Thu, Jun 06, 2019 at 01:32:14PM -0600, Martin Sebor wrote:
> Hi Jeff,
>
> It looks like the updated comment for get_range_strlen didn't make
> it into the strlen fixup commits last December and the function
> still has the old description. (Not surprising given there are
> at least two overloa
