Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:121780 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 48000 invoked from network); 23 Nov 2023 12:43:05 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 23 Nov 2023 12:43:05 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 22877180050 for ; Thu, 23 Nov 2023 04:43:09 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-3.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,DMARC_PASS,FREEMAIL_FROM, HTML_MESSAGE,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=4.0.0 X-Spam-Virus: No X-Envelope-From: Received: from mail-yb1-f175.google.com (mail-yb1-f175.google.com [209.85.219.175]) (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) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Thu, 23 Nov 2023 04:43:08 -0800 (PST) Received: by mail-yb1-f175.google.com with SMTP id 3f1490d57ef6-db4422fff15so337727276.1 for ; Thu, 23 Nov 2023 04:43:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1700743384; x=1701348184; darn=lists.php.net; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=oYvvbJkb2LuUbazVWYktWJmHiBIKwhRstyP8hA4UnXI=; b=nPUJms6Jo/tl0E3CM/PzhQ9I7Rv6zNiwGmIVVmyGlaVCUwf7NzQVwSRBcgL/lKcp3t yVet5DWSLTB0K0YOoTUTmsHx6yCvoKV41ae1P+VaDZkD9bRcjzRbPcQ/F6lE6Ym2lPxV o1W3xn4osuUEjSgrNd/8vV8yywgRA5njtFTStG2g3uXskc5asGj2D1Xhc3oljfJmEtiB XdgydnVRSNU2M+lBljSlJWgSWMlWwsedhzNGtSTuQgEbSIyGDfZbfdumDBDeEu4m/APA ydXDUrC4hETxg0PFPYWWajrlE1X41g3EXIu2cDox+G4olgE3dNDRV9MzkcBqskV4V4b7 pkeQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700743384; x=1701348184; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=oYvvbJkb2LuUbazVWYktWJmHiBIKwhRstyP8hA4UnXI=; b=P1Yv5FGNl8vez38O+KWFqvJMZ2W/f2gyMq3FZh8JEBBQ2hGgYxi7/UEqww9vdmmY5I 3lq5O00Cd/D78lno8lXGwemrks1l/u7cElGDkOSNqchDff9ukYsacqUJLa6TFfHSOBrh +0eJxAnUe4IO9PYvICFDRx3nSSiZ4mEzvAJfrkbVCBO3BqMi7iJ0AP2lpL+fNVXOeRbs R4WYeyC2moRN0i+7u0BMB1Mbuv32idYqZ91BCB4KvysFDZviqbB5Wdo6v/zSmu3w70qe xJtZwpGfAsayZACMBBDMGflAWNDM/mZFxHzzRY/FOKGRhg3+PSnP2pUrFQZlu5GcvslV 3bbA== X-Gm-Message-State: AOJu0YzRmEOqFmgoSFlJMazPLanMTTz+jICp15p4TDwJnTW+gGTaJqOD 8lw/HEhcoZ2hH3SnzwlsT/A+vWZ/sTsTLMr8kzMe0oYf+RY= X-Google-Smtp-Source: AGHT+IEqhcKybL+yZR1uxgJRA+kYLGUWDxMsRrpDHXdlNee1mG2JifBcc4anMA+teCY6NKfmx6YVTa7S+jTpztkxrYc= X-Received: by 2002:a25:abe1:0:b0:d9c:2c30:ebb1 with SMTP id v88-20020a25abe1000000b00d9c2c30ebb1mr5173472ybi.12.1700743383771; Thu, 23 Nov 2023 04:43:03 -0800 (PST) MIME-Version: 1.0 References: <79d675e3-95b4-40bb-baf4-3e1c998f5390@online-presence.ca> <34979AED-893F-45DD-B641-A9F4F39B2928@newclarity.net> <2D505086-6AD9-4596-A515-85B50F5D12C5@koalephant.com> In-Reply-To: Date: Thu, 23 Nov 2023 12:42:51 +0000 Message-ID: To: PHP internals Content-Type: multipart/alternative; boundary="0000000000003e6fa1060ad12de8" Subject: Re: [PHP-DEV] RFC Proposal - static modifier for classes From: rowan.collins@gmail.com (Rowan Tommins) --0000000000003e6fa1060ad12de8 Content-Type: text/plain; charset="UTF-8" On Thu, 23 Nov 2023 at 11:48, Stephen Reay wrote: > > Respectively, I disagree that it's "not a big problem" if your goal is to > encourage people to use regular functions over classes with static methods. > Just to be clear, my answer was specifically addressing your point about using Composer as an argument for not including things. I was not saying "... and therefore the argument is true", only "... and therefore we can discuss the argument without mentioning Composer if we want to". > PHP ships with a built in class autoloader function, and pretending that using 'require_once' everywhere a function is used, is just as easy for the developer seem disingenuous to be honest. PHP ships with *the ability to configure* an autoloading function; it will not load any files without you first telling it where to look. The workaround being proposed is not to use require_once every time you want a function, it's to use require_once in the same place you configure your autoloader. I totally agree that we can debate whether that workaround is sufficient. I'm just trying to frame that debate as "autoloading vs require", rather than a distraction of "Composer vs something else". Regards, -- Rowan Tommins [IMSoP] --0000000000003e6fa1060ad12de8--