From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Interest in nt_load_image? Date: Mon, 30 Mar 2020 15:39:11 -0400 Message-ID: References: <86369r0xcv.fsf@csic.es> <83k1324m60.fsf@gnu.org> <86imimwa4t.fsf@csic.es> <838sji3qhx.fsf@gnu.org> <86lfnhsyei.fsf@csic.es> <83v9ml3kpx.fsf@gnu.org> <86r1x9rf7w.fsf@csic.es> <83pnct3ikf.fsf@gnu.org> <83imil3d8r.fsf@gnu.org> <83blod3c26.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="79440"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: juanjose.garciaripoll@gmail.com, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Mar 30 21:39:53 2020 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 1jJ0GH-000KZJ-Ob for ged-emacs-devel@m.gmane-mx.org; Mon, 30 Mar 2020 21:39:53 +0200 Original-Received: from localhost ([::1]:55556 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jJ0GG-0003Ax-R4 for ged-emacs-devel@m.gmane-mx.org; Mon, 30 Mar 2020 15:39:52 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:57096) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jJ0Fi-0002ZE-Pe for emacs-devel@gnu.org; Mon, 30 Mar 2020 15:39:19 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jJ0Fh-00077e-96 for emacs-devel@gnu.org; Mon, 30 Mar 2020 15:39:18 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:30724) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1jJ0Ff-00075l-Ch; Mon, 30 Mar 2020 15:39:15 -0400 Original-Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 6AD1C44FA59; Mon, 30 Mar 2020 15:39:14 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 12DBA44FA4C; Mon, 30 Mar 2020 15:39:13 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1585597153; bh=ZS8HhGiOKHs5K/4afGP2CmDRj16CMf0mkzqzWTWdcr8=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=lJh+Tf38UDPs3PR0WWq91RRVqDAZijghTU00V5rjyoUuJNjlDv/BHOFGWfbPMqEE2 7Zqqt42XSH+QV5ar1MlyE4ziNcXEKrpsyxF5ZZ7ueFMPJIpyJsEvRZ8s2ZPkhleJRn orAowEy7DCPyjt6YO5Pemp9i55FgSxM8r2wTwQZ23JtBjYl5d7juRDTKErtbOb5Iic UjAN8NV52RDkqTs0fgI+RKTP8U3Wzy6sPhOtf6kBeBP78ZyiG8uprXSXWWfO8lHoC4 7M+wX64zQic/ECfO6UONdK1vyj+sJkg0Esw66lrIpLU2Q7VPxu2V9sQPt/H49Dam+H 44Ira3SO/ghzw== Original-Received: from alfajor (unknown [104.247.241.114]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 5DF0212079C; Mon, 30 Mar 2020 15:39:12 -0400 (EDT) In-Reply-To: <83blod3c26.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 30 Mar 2020 21:57:53 +0300") X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 132.204.25.50 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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:246066 Archived-At: >> I don't see what resources you're talking about. > Resources needed to try to figure out whether we need the > compatibility code, devise probes, waiting for someone to holler and > remembering to check if someone did... I'm not suggesting we do any of those things. I suggest we write the code under the assumption that GDI+ is available and that's it. "waiting for someone to holler" is already taken care of by debbugs, so it doesn't take any resources. As for remembering to check, there's no need to do that either: if noone hollers, then we do nothing. >> From where I stand, you're suggesting to "waste precious resources" >> trying to make the code hypothetically work in Windows-98, whereas I'm >> suggesting we don't do that and let other people come whining if they >> suffer the consequences. > There are no consequences. The paradigm of loading a shared library > dynamically and testing whether doing that succeeded is so boilerplate > in the w32 code that it never takes more than a simple copy/pasta to > add one more. But what do we do if the loading fails? If we simply fail to display the image, then that's fine by me. If OTOH we go through the trouble of falling back on some other code which otherwise wouldn't be needed in the build (and would hence never be tested, BTW), then it sounds like "waste precious resources". >> > One day it will die of natural causes, no need to invest even >> > a minimal effort in that. >> I'm not sure how that would happen > It will happen when 32-bit builds will die. 2038 at the latest. Are we sure sure 32bit Windows installations will have all disappeared by 2038 ? ;-) Stefan "who finds 18 more years of support for Windows-98 rather excessive"