Skip to content

use str* API in place of isdigit() in server/conf.c #676

Closed

Description

@clepple

isdigit() takes a char/int, not a char*.

Originally mentioned here, but we need to fix this before the next release.

Activity

  1. added this to the 2.7.5 milestone on Mar 13, 2019
  2. self-assigned this
    on Mar 13, 2019
  3. added a commit that references this issue on Mar 13, 2019
    dd6cdbe
  4. added
    ready / code reviewAuthor (and CI) consider the PR worthy of human rewievers' time
    on Mar 13, 2019
  5. removed
    ready / code reviewAuthor (and CI) consider the PR worthy of human rewievers' time
    on Apr 29, 2019
  6. changed the title [-]fix invocation of isdigit(), or use str* API[/-] [+]use str* API in place of isdigit() in server/conf.c[/+] on Apr 29, 2019
  7. modified the milestones: 2.7.5, 2.7.6 on Apr 29, 2019
  8. clepple commented on Apr 29, 2019

    @clepple
    MemberAuthor

    I'm bumping the milestone from 2.7.5 to 2.7.6 because we merged #690, which fixes the misuse of isdigit(). I still think that a slightly reworked version of #677 (with signed/unsigned expanded out into separate variables, etc.) should be merged into the following release.

  9. added
    refactor/fightwarnPR or issue proposal to improve code maintainability without functional changes, or to fix warnings
    on Nov 14, 2021
  10. removed this from the 2.8.1 milestone on Jan 6, 2023
  11. 1 remaining item

  12. modified the milestones: 2.8.2, 2.8.3 on Apr 4, 2024
  13. added
    C-strIssues and PRs about C/C++ methods, headers and data types dealing with strings and memory blocks
    on Apr 10, 2024
  14. modified the milestones: 2.8.3, 2.8.4 on Sep 12, 2024
  15. modified the milestones: 2.8.4, 2.8.5 on Jul 29, 2025
  16. modified the milestones: 2.8.5, 2.8.6 on Feb 12, 2026
  17. added
    HardeningIdeas and implems to make NUT deployments more robust and secure (relaxed convenience may suffer)
    on Jun 5, 2026
  18. user01010111 commented on Sep 1, 2026

    @user01010111
    Contributor

    PR #677 remains conflicting and changes-requested. Would you be happy for me to prepare a fresh parsing-only PR from current master that supersedes it, preserves the existing public types, and reuses the current str_to_* helpers?

  19. jimklimov commented on Sep 1, 2026

    @jimklimov
    Member

    @user01010111 : generally yes, but maybe a bit later - the CI resources are already overwhelmed and will be for a few days to come, with currently open PRs (which is generally a good thing) :)

    I also hoped to tackle different C-str, C-bool etc. cleanups after finally merging the FTY branch into main code, to avoid fixing those troubles twice.

  20. user01010111 commented on Sep 1, 2026

    @user01010111
    Contributor

    @jimklimov, just keeping the machines feed 😂

    Have mostly just been trying to clear the lower-hanging fruit for 2.8.6 and addressing the other items where I can be helpful without (hopefully) treading on anyone's toes.

    Ping me in here when you'd like me to pick it up, and I can continue if so. Thanks, Jim.

  21. added a commit that references this issue on Sep 14, 2026
    af8abed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

C-strIssues and PRs about C/C++ methods, headers and data types dealing with strings and memory blocksHardeningIdeas and implems to make NUT deployments more robust and secure (relaxed convenience may suffer)refactor/fightwarnPR or issue proposal to improve code maintainability without functional changes, or to fix warnings

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions