Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:106904 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 50365 invoked from network); 8 Sep 2019 16:28:25 -0000 Received: from unknown (HELO php-smtp3.php.net) (208.43.231.12) by pb1.pair.com with SMTP; 8 Sep 2019 16:28:25 -0000 Received: from php-smtp3.php.net (localhost [127.0.0.1]) by php-smtp3.php.net (Postfix) with ESMTP id 041852D2188 for ; Sun, 8 Sep 2019 07:03:20 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp3.php.net X-Spam-Level: X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS3215 2.6.0.0/16 X-Spam-Virus: No Received: from mail-ot1-x330.google.com (mail-ot1-x330.google.com [IPv6:2607:f8b0:4864:20::330]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by php-smtp3.php.net (Postfix) with ESMTPS for ; Sun, 8 Sep 2019 07:03:19 -0700 (PDT) Received: by mail-ot1-x330.google.com with SMTP id 21so9996372otj.11 for ; Sun, 08 Sep 2019 07:03:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=D5st04UQ7nrRMgXmVrTyroAGuu7xJQV0cYh1PVup/FQ=; b=fFzS7AnFdmaVB2ggDCSdtNabX6h1jYgE55DG4X3gAltx4hEy3HsME1ZW/41Zf3SwB8 ndnKbw2rwSu1y3xSq3O9RVo/cAazg7c1xnoKf2o0AumR4zlOG4PmzZwL/+q2cT41wjWh tbwlnU7fZaVISu5lceSidbLWekc6b7Ui/fjLDdlYrPAaQZiMpdhCs+Rvvt4wlNCfyIxC NVmLW//2ErLjkNoN75sMyMRF5PuAUyLhcHkAdVFExltufVFhBSQGS/OA3ZcCGAs8dJFz gljnmqilkHT76kYGKdFD56SOOMdVrFpI6QbjNZ65OU+VmO6NRKeDK0ZGesIPbY503u9X +twg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=D5st04UQ7nrRMgXmVrTyroAGuu7xJQV0cYh1PVup/FQ=; b=hkyHYLoBBPLYL9tTz1oi7BENDSrLZmaTVr3ofnsgKyf/iZcMf2NSHDspXMG20RS9u7 fhZEg7HPbBnbtopYBL9ka4wwqpR9nwBACcT5zOvf8YwVZxbpeSksy0XEpfADN/aYjaOU t0vPDAIeG+spbYfTklls3cIoxW46DBVqlSL4ST7aQU1kIdg6sj55iqqKcgZ4yUNdXIdR dzHB0vuNKUpyHes1MwuW2V2EsLyLMP7tiuRJDuc9nVIj71bYFsAk6RHU7yoRzxQ4QxaI zDG9Ldd6CsEzLyh50JlCcGbNxTaTCR4S9JW949yxFl9d5Bdbc3yEEc2bHSpHHh0ZM3xx wFzg== X-Gm-Message-State: APjAAAUuhQqM1phxTzy270JYeY/5EbJwfCRgDFO+6UYSAu8zVh+5H3aV Eh55YmNhAmpseE9YUWazIFLR3nK7mv+/Ii4QcqOpRv3S X-Google-Smtp-Source: APXvYqwW+E7mYQ3GP3ncTmqDlkHYsw7VJ0t42E+0Y3+f/UZe3b5go1EHloFZ6c9bI+7PbG1jLjwTuM+EFhoKJQu65qc= X-Received: by 2002:a9d:224b:: with SMTP id o69mr14655750ota.45.1567951398526; Sun, 08 Sep 2019 07:03:18 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Sun, 8 Sep 2019 16:03:06 +0200 Message-ID: To: PHP Internals List Content-Type: multipart/alternative; boundary="00000000000022627105920b229f" X-Envelope-From: Subject: Re: Preloading experiments with Symfony From: nicolas.grekas+php@gmail.com (Nicolas Grekas) --00000000000022627105920b229f Content-Type: text/plain; charset="UTF-8" Hello, I didn't get any response to my email from June 17th, yet I think this is pretty critical, see below. I did not manage to make preloading with Symfony yet, see https://bugs.php.net/78512 also? Thanks for considering, the behavior is unexpected to me, as it deviates from common behavior. I opened https://bugs.php.net/bug.php?id=78169 but were asked to raise the > point on the list: > > When opcache.preload is used, requiring twice a file that declares a > preloaded class will not yield any error, while when preloading is not > used, one will get a cannot redeclare error. > > On the other side, when require_once is used, a preloaded class file is > not considered "already loaded", which means the require happens during > execution. > > Would it make sense to change both these behaviors to make them more in > line with normal engine behavior? i.e. "require_once" on a file that was > already preloaded wouldn't require it again, > and "require" on a preloaded file that contains a class declaration would > yield a "cannot redeclare" fatal error? > > This would be more expected to me. > Would it be possible? > > Thanks, > Nicolas > --00000000000022627105920b229f--