Skip to content

Conversation

silverweed
Copy link
Contributor

The description was trying to refer to a website but no URL was there. The message was also compactified a bit to save vertical space.

The description was trying to refer to a website but no URL was there.
The message was also compactified a bit to save vertical space.
@silverweed silverweed self-assigned this Sep 2, 2025
Copy link

github-actions bot commented Sep 2, 2025

Test Results

    19 files      19 suites   3d 11h 10m 35s ⏱️
 3 656 tests  3 654 ✅   0 💤 2 ❌
67 842 runs  67 740 ✅ 100 💤 2 ❌

For more details on these failures, see this check.

Results for commit 96df320.

Copy link
Collaborator

@ferdymercury ferdymercury left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

Not related to this PR:
I find root-argparse, related Python cmdlineOption helper scripts and generateHeader RootMacro (used for hadd, dictgen, root, ...) an unnecessary hetero-complexity, when there are ready-to-go header-only C++ libraries such as https://github.com/CLIUtils/CLI11 that could be linked via CMake without problems.

Also, there was some discussion about removing root wrapper and just redirecting to root.exe, in which case this help would have to be moved there, too.
see https://its.cern.ch/jira/browse/ROOT-10697

@silverweed
Copy link
Contributor Author

silverweed commented Sep 2, 2025

I find root-argparse, related Python cmdlineOption helper scripts and generateHeader RootMacro (used for hadd, dictgen, root, ...) an unnecessary hetero-complexity

100% agree, I will see them gone at some point in the future.

Using a common C++ library to parse options already emerged some time ago, but there is the issue of executables using heterogeneous and non-standard styles for options (e.g. some executables accept single-dash long options, and some use weird conventions where the same flag means different things depending on the argument).
These can probably all be resolved, but needs to be thought through a bit.

I would also be in favor of removing the root wrapper, but again the implications needs to be considered first.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants