From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Opcode Versioning Was: emacs master + org Wrong type argument: number-or-marker-p Date: Thu, 04 Aug 2022 18:11:18 -0400 Message-ID: References: <83bkt42ifq.fsf@gnu.org> <87a68ovw0b.fsf@posteo.net> <835yjc2c6f.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="6030"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Aug 05 00:12:19 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oJj4k-0001Ks-Ni for ged-emacs-devel@m.gmane-mx.org; Fri, 05 Aug 2022 00:12:18 +0200 Original-Received: from localhost ([::1]:56834 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oJj4i-0003n5-Te for ged-emacs-devel@m.gmane-mx.org; Thu, 04 Aug 2022 18:12:16 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:42890) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oJj3y-00037v-5H for emacs-devel@gnu.org; Thu, 04 Aug 2022 18:11:30 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:11992) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oJj3t-0002fx-6E for emacs-devel@gnu.org; Thu, 04 Aug 2022 18:11:29 -0400 Original-Received: from pmg2.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id 9D447802B6; Thu, 4 Aug 2022 18:11:23 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id 319E580058; Thu, 4 Aug 2022 18:11:22 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1659651082; bh=VuUHvqfRo/B218sskmUW9Cakz+ECKXdiLL0z+d5E860=; h=From:To:Subject:In-Reply-To:References:Date:From; b=mI8GpbstYg7v4BgefQKdQS1G/i51ydytKHs7M22v7eFKjRE4zCF7JsLf03NpaSJss iSnI35bEwr3wZBrDJJWkcvMNSC6q0E3xo2J0SQyDJpUgRcn9tp24Iyco5ZCmk5fFtb 1Y8LmpmLHPP72sNS7xSmCZYGY6cTFrtjQotfE/zWL3bnOdfyNTVpnq6fTxSQl9J51I nsSHcpePzltUpcIX6hIXk8TL9IMEWNj65Y2xo9jR9CewAizktaf1J0ZH6b9WXB39t2 5vjlcPGmR0NDEuuJURCHQnPBTHsnKvO7QEqmcVwOUDeIdn7afbqF9lPnEC17jdop1g d/cezGSDHte5g== Original-Received: from milanesa (unknown [46.44.221.102]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 93F8C1203E5; Thu, 4 Aug 2022 18:11:21 -0400 (EDT) In-Reply-To: (Sam Steingold's message of "Thu, 04 Aug 2022 10:59:46 -0400") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:293089 Archived-At: Sam Steingold [2022-08-04 10:59:46] wrote: >> Emacs instead aims to be able to keep loading old byte-compiled files >> so we try hard to change the byte-codes only in ways which are >> backward compatible. > This is a very noble aim. > Does it ever happen that Emacs breaks byte-codes as a design decision? IIRC we did drop some byte-codes, yes. Most of them are byte-codes which had never been generated by our byte-compiler, but I think there were a few other cases where we judged that it had been enough years. > Or is Emacs _supposed_ to be able to load ELC from 1990? More or less but not really: even if the byte code itself should probably work, it's likely to bump into incompatible changes in the functions we define (or fail to). Stefan