From: SAIFI <msk@strikr.io>
To: gcc@gcc.gnu.org
Subject: Re: [RFC] database with API information
Date: Fri, 09 Sep 2022 18:40:52 +0000 [thread overview]
Message-ID: <20220909184052.45384.qmail@s810.sureserver.com> (raw)
In-Reply-To: <CAH6eHdTehHCD_j5X4GH4+oeMaFakWhGcYK+hb++456HKw-k+6A@mail.gmail.com>
> -------Original Message-------
> From: Jonathan Wakely <jwakely.gcc@gmail.com>
>
> > Would any of the C++11 compliant CSV parsing libraries make the cut
> > in your analysis ?
>
> I'm not going to waste my time looking.
>
> > Vince CSV parser (RFC4180 + flavours)
> > https://github.com/vincentlaucsb/csv-parser
> >
> > C++11 header only (MT can be turned on/off).
> > https://github.com/ben-strasser/fast-cpp-csv-parser
> >
> > If not, Is there is something else that is needed for the CSV
> > parsers to qualify ?
>
> Why add an extra dependency that would have to be included in the GCC
> sources, when Python already has what's needed to do this.
>
> Somebody has written a new tool, and you seem to be asking them to
> rewrite it for your preferences. If you want to rewrite the script in
> C++ feel free to proposed a patch, but this digression for your
> curiousity doesn't seem productive to me.
Well, it seems then the 'innocent CSV' proposed by Ulrich is the strawman that leads to meson !
Please feel free to correct me if that is not the 'unstated' intent.
warm regards
Saifi.
next prev parent reply other threads:[~2022-09-09 18:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 6:22 Ulrich Drepper
2022-09-07 10:56 ` Richard Sandiford
2022-09-07 12:33 ` Martin Liška
2022-09-09 15:26 ` Iain Sandoe
2022-09-09 17:07 ` Ulrich Drepper
2022-09-09 17:13 ` Iain Sandoe
2022-09-09 11:40 ` SAIFI
2022-09-09 11:47 ` Jonathan Wakely
2022-09-09 12:29 ` SAIFI
2022-09-09 15:06 ` Jonathan Wakely
2022-09-09 16:41 ` SAIFI
2022-09-09 18:21 ` Jonathan Wakely
2022-09-09 18:40 ` SAIFI [this message]
2022-09-09 20:05 ` Jonathan Wakely
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220909184052.45384.qmail@s810.sureserver.com \
--to=msk@strikr.io \
--cc=gcc@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).