From: Markus Elfring <Markus.Elfring@web.de>
To: cocci@inria.fr, kernel-janitors@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [cocci] [RFC] Keeping more higher level structures for efficient data processing?
Date: Fri, 14 Mar 2025 08:52:10 +0100 [thread overview]
Message-ID: <8f9fba3e-3b89-4e24-9b0e-d56d31ac6712@web.de> (raw)
Hello,
Well-known data processing approaches can depend on various input files.
The input files are usually transformed into higher level structures.
This data transformation needs some resources and efforts.
https://en.wikipedia.org/wiki/Parsing
You might be looking for ways to avoid the repetition of such resources and efforts.
I imagine that an information system can be constructed which would manage
corresponding higher level structures for a while.
How will circumstances evolve for further software evolution in such directions?
Regards,
Markus
reply other threads:[~2025-03-14 7:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=8f9fba3e-3b89-4e24-9b0e-d56d31ac6712@web.de \
--to=markus.elfring@web.de \
--cc=cocci@inria.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).