From: Timo Rothenpieler <timo@rothenpieler.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] API enhancements / broken promises
Date: Fri, 19 Aug 2022 21:35:48 +0200
Message-ID: <ef480fc8-502d-1c80-d81c-a7462582d59d@rothenpieler.org> (raw)
In-Reply-To: <20220819183033.GH2088045@pb2>
On 19.08.2022 20:30, Michael Niedermayer wrote:
> ok
> but just to clarify what i meant / was thinking of was a simple
> key / value style parser no features beyond that. just enough so we can
> use it to read our own generated xml from some object serialization.
One can hardly call that XML then.
For something like that, it's much better to just use libxml2, if you
really want to use XML, or just use another, super trivial format, like
.ini or something.
XML, JSON, YAML and friends all have a massive amount of complexity
attached to them.
Any kind of parser we add for them would almost inevitably grow over
time, as people add more and more features to them. "Just one more
simple patch".
I'd rather not open that can of worms.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
prev parent reply other threads:[~2022-08-19 19:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 16:47 Nicolas George
2022-08-16 23:16 ` Stefano Sabatini
2022-08-17 17:21 ` Michael Niedermayer
2022-08-17 20:48 ` Nicolas George
2022-08-18 8:48 ` Tomas Härdin
2022-08-18 17:19 ` Jean-Baptiste Kempf
2022-08-19 18:30 ` Michael Niedermayer
2022-08-19 19:35 ` Timo Rothenpieler [this message]
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=ef480fc8-502d-1c80-d81c-a7462582d59d@rothenpieler.org \
--to=timo@rothenpieler.org \
--cc=ffmpeg-devel@ffmpeg.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
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git