From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <ffmpeg-devel-bounces@ffmpeg.org>
Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100])
	by master.gitmailbox.com (Postfix) with ESMTP id 5F3604B462
	for <ffmpegdev@gitmailbox.com>; Sat,  6 Jul 2024 18:03:33 +0000 (UTC)
Received: from [127.0.1.1] (localhost [127.0.0.1])
	by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 4D9D868DBD2;
	Sat,  6 Jul 2024 21:03:30 +0300 (EEST)
Received: from b-painless.mh.aa.net.uk (b-painless.mh.aa.net.uk [81.187.30.52])
 by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id C71F668DB00
 for <ffmpeg-devel@ffmpeg.org>; Sat,  6 Jul 2024 21:03:23 +0300 (EEST)
Received: from
 3.4.3.5.7.1.0.f.c.9.9.9.9.3.2.a.0.5.8.0.9.1.8.0.0.b.8.0.1.0.0.2.ip6.arpa
 ([2001:8b0:819:850:a239:999c:f017:5343] helo=andrews-2024-laptop.sayers)
 by painless-b.tch.aa.net.uk with smtp (Exim 4.96)
 (envelope-from <ffmpeg-devel@pileofstuff.org>) id 1sQ9km-002IH1-1A
 for ffmpeg-devel@ffmpeg.org; Sat, 06 Jul 2024 19:03:22 +0100
Date: Sat, 6 Jul 2024 19:03:21 +0100
From: Andrew Sayers <ffmpeg-devel@pileofstuff.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Message-ID: <ZomG6UZVD3okjGEn@andrews-2024-laptop.sayers>
References: <ZoMuv89bLCVPsMWf@mariano>
 <20240702090917.319956-1-ffmpeg-devel@pileofstuff.org>
 <ZokQTzkL6ZqI/c3g@mariano>
 <CAPYw7P7jQ21EDzJfZFAVb5S1nMXChaLyX=APwfRjmPnNeFbhrg@mail.gmail.com>
 <20240706164951.GH4991@pb2>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <20240706164951.GH4991@pb2>
Subject: Re: [FFmpeg-devel] [PATCH v4 0/3] s/RUNTIME/POST_INIT_SETTABLE/
X-BeenThere: ffmpeg-devel@ffmpeg.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: FFmpeg development discussions and patches <ffmpeg-devel.ffmpeg.org>
List-Unsubscribe: <https://ffmpeg.org/mailman/options/ffmpeg-devel>,
 <mailto:ffmpeg-devel-request@ffmpeg.org?subject=unsubscribe>
List-Archive: <https://ffmpeg.org/pipermail/ffmpeg-devel>
List-Post: <mailto:ffmpeg-devel@ffmpeg.org>
List-Help: <mailto:ffmpeg-devel-request@ffmpeg.org?subject=help>
List-Subscribe: <https://ffmpeg.org/mailman/listinfo/ffmpeg-devel>,
 <mailto:ffmpeg-devel-request@ffmpeg.org?subject=subscribe>
Reply-To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ffmpeg-devel-bounces@ffmpeg.org
Sender: "ffmpeg-devel" <ffmpeg-devel-bounces@ffmpeg.org>
Archived-At: <https://master.gitmailbox.com/ffmpegdev/ZomG6UZVD3okjGEn@andrews-2024-laptop.sayers/>
List-Archive: <https://master.gitmailbox.com/ffmpegdev/>
List-Post: <mailto:ffmpegdev@gitmailbox.com>

On Sat, Jul 06, 2024 at 06:49:51PM +0200, Michael Niedermayer wrote:
> On Sat, Jul 06, 2024 at 12:40:07PM +0200, Paul B Mahol wrote:
> [...]
> 
> > its much more text to type too.
> 
> shorter options:
> 
> AV_OPT_FLAG_ALTERABLE_PARAM
> 
> AV_OPT_FLAG_MUTABLE_PARAM
> 
> (just in case consensus ends on a rename, i am not sure a rename is a good idea here)

I'm fine with someone doing s/POST_INIT_SETTABLE/MUTABLE/g on the patch before
committing it if they feel that's better, but ALTERABLE seems like a bad idea.

I guess you could argue a sufficiently inattentive reader might read
"POST_INIT_SETTABLE" to mean "*only* settable after init", even though
the documentation says otherwise.  But such a reader might also read
"ALTERABLE" to somehow mean "data type can be altered" (like SQL's ALTER TABLE
statement), whereas "mutable" conventionally means "contents can be altered".

But this is just a nitpick - POST_INIT_SETTABLE is still fine by me.
_______________________________________________
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".