From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTP id 0D1AE44087 for ; Mon, 23 Jan 2023 17:03:20 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id A3AF468BDB7; Mon, 23 Jan 2023 19:03:17 +0200 (EET) Received: from mail0.khirnov.net (red.khirnov.net [176.97.15.12]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 5BCBE68BABF for ; Mon, 23 Jan 2023 19:03:11 +0200 (EET) Received: from localhost (localhost [IPv6:::1]) by mail0.khirnov.net (Postfix) with ESMTP id D1F332404EC for ; Mon, 23 Jan 2023 18:03:10 +0100 (CET) Received: from mail0.khirnov.net ([IPv6:::1]) by localhost (mail0.khirnov.net [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id HNTpIheR7VLn for ; Mon, 23 Jan 2023 18:03:10 +0100 (CET) Received: from lain.khirnov.net (lain.khirnov.net [IPv6:2001:67c:1138:4306::3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "lain.khirnov.net", Issuer "smtp.khirnov.net SMTP CA" (verified OK)) by mail0.khirnov.net (Postfix) with ESMTPS id 37155240178 for ; Mon, 23 Jan 2023 18:03:10 +0100 (CET) Received: by lain.khirnov.net (Postfix, from userid 1000) id 17E821601B2; Mon, 23 Jan 2023 18:03:10 +0100 (CET) From: Anton Khirnov To: FFmpeg development discussions and patches In-Reply-To: <8b99815-8f2f-8366-68c3-82fe7698c36b@passwd.hu> References: <20230116133840.512-1-jamrial@gmail.com> <167407008302.4503.12911207010634660934@lain.khirnov.net> <20230120020509.GX1949656@pb2> <167431989409.26119.3043585718968218@lain.khirnov.net> <20230121213629.GZ1949656@pb2> <8b99815-8f2f-8366-68c3-82fe7698c36b@passwd.hu> Mail-Followup-To: FFmpeg development discussions and patches Date: Mon, 23 Jan 2023 18:03:10 +0100 Message-ID: <167449339006.26119.5457958520936000123@lain.khirnov.net> User-Agent: alot/0.8.1 MIME-Version: 1.0 Subject: Re: [FFmpeg-devel] [PATCH 00/26] Major library version bump X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: Quoting Marton Balint (2023-01-21 23:00:52) > > > On Sat, 21 Jan 2023, Michael Niedermayer wrote: > > > On Sat, Jan 21, 2023 at 05:51:34PM +0100, Anton Khirnov wrote: > >> Quoting Michael Niedermayer (2023-01-20 03:05:09) > >>> PS: iam not sure i fully understood the reason behind why versions should be > >>> set to "wrong" values during some period, so as always i might be missing > >>> something > >> > >> The reason is that after the major bump, the API and ABI are declared to > >> be unstable for some period, so people can freely > >> - break ABI, e.g. by reordering struct members > >> - modify API added during the instability period in an arbitrary way > >> without a new major bump for every such change, that would be normally > >> required. > >> > >> My concern is that the instability period is quite long and there is > >> very little indication for our users that they cannot depend on the > >> ABI/API being stable. So I'm proposing to introduce some mechanism to > >> make this more visible for our callers. > >> > >> Alternatively, we could just not have an instability period at all. > > > > Does anyone plan to use the next bumps instability period for anything ? > > If so, i assume theres a good reason why it cannot be done without such > > period easily? > > AVCodecContext->frame_number should be changed to int64_t. I guess you > could do something similar which was done for buffer_size_t, but that > seems like a lot of extra work and ifdefry for questionable benefit. Not breaking callers seems like a very solid benefit to me. -- Anton Khirnov _______________________________________________ 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".