Follow-up Comment #12, bug#64571 (group make):
Wow, that's great stuff from Tim. I was really re-treading his steps there,
even with the same flag name `--print-data-base-json`!
Definitely valid limitations of nested JSON, very tricky to parse without the
right tools. However, in this context, is that an issue? If JSON output is opt
in with `--format json`, then it's on the caller whether or not they have the
required tooling available to handle the output. I wasn't imagining that
make's bash completion would be re-written building on the new JSON output. Is
there a risk that would happen?
Once there's a `--format` option, then there's space for other formats (`git
log` offers several bespoke formats). A new line delimited, bespoke tabular
format could be added, which would be more easily parsed by standard POSIX
tools, and could be a better option for reworking bash completion if this was
wanted / needed.
Thank you for the information regarding `-n` and `-p`. Will need to have a
think about that one (and refresh my knowledge on rebuilding make files)!
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?64571>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
