Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:82056
Return-Path: <leverton@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 85436 invoked from network); 6 Feb 2015 16:45:18 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 6 Feb 2015 16:45:18 -0000
Authentication-Results: pb1.pair.com smtp.mail=leverton@gmail.com; spf=pass; sender-id=pass
Authentication-Results: pb1.pair.com header.from=leverton@gmail.com; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.45 as permitted sender)
X-PHP-List-Original-Sender: leverton@gmail.com
X-Host-Fingerprint: 209.85.220.45 mail-pa0-f45.google.com  
Received: from [209.85.220.45] ([209.85.220.45:37689] helo=mail-pa0-f45.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id F0/2A-45146-79FE4D45 for <internals@lists.php.net>; Fri, 06 Feb 2015 11:45:14 -0500
Received: by mail-pa0-f45.google.com with SMTP id et14so18338620pad.4
        for <internals@lists.php.net>; Fri, 06 Feb 2015 08:45:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        bh=BvaX8zlEko3gSg+yGrCqYrylTXcWLkhm+kxNl+pLoTg=;
        b=nPzIdhKQiNzuyamPGQXLPtB4qHXiNOP9TgC7KDKi8ZZI5ViEn8lOHW2vv2ipxKLt0q
         GF3ixlKGPByQ+zsA5kn/WWjuVWdxp1xjDBDaUvjOrCSN7MSV8IWEMd/p8/2X1bwCSzCR
         0JFt4x8DHx3qpL9veIEWkxkNn0kCPe4eO/CEnXQfUKL6UDJDQ5Uc/jCwwV7Wmzy0aolA
         QhjnxYwSOKOw4PakzSf0gAwh1hwaX1/RXi+WIFOg/vywYIbGL8ZHsYLEUGCBluzs66/C
         yZHQLGahITZ9cjaoPHMtbi6v4tbqLJCUwFF6juxBL8/lAVxIGZjP/PpSkq7M4lFGeESc
         nhng==
MIME-Version: 1.0
X-Received: by 10.70.61.106 with SMTP id o10mr7270361pdr.46.1423241106712;
 Fri, 06 Feb 2015 08:45:06 -0800 (PST)
Received: by 10.70.65.130 with HTTP; Fri, 6 Feb 2015 08:45:06 -0800 (PST)
In-Reply-To: <CAGa2bXYzs=5FVF_OXFj+o=S1uq_7fhfMH7Ent9FHfd-ziV_W5Q@mail.gmail.com>
References: <CAGa2bXYzs=5FVF_OXFj+o=S1uq_7fhfMH7Ent9FHfd-ziV_W5Q@mail.gmail.com>
Date: Fri, 6 Feb 2015 10:45:06 -0600
Message-ID: <CAN=kQJcmBQZr4nabAUoiASymb8eJxZV6d+RODcPwoNUf3_VG9A@mail.gmail.com>
To: Yasuo Ohgaki <yohgaki@ohgaki.net>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] [RFC][DISCUSSION] Introduce scrpt_path
From: leverton@gmail.com (Matthew Leverton)

On Fri, Feb 6, 2015 at 6:02 AM, Yasuo Ohgaki <yohgaki@ohgaki.net> wrote:
> https://wiki.php.net/rfc/script_path
>
> It's work in progress, but I would like to start discuss.
>

I don't really like it; but I don't really like most INI-based solutions.

I agree that this is a problem with poorly written code, but at the
same time I don't know that a good solution is to compensate in this
regard. Bad programmers will always be bad programmers. Now we're
giving them a crutch that almost encourages unchecked includes by
relying on an INI configuration. What happens if you are using
multiple libraries and they are each overriding their (and your)
settings? It just feels messy.

The same thing could be accomplished config-less with a callback
system that is triggered on script includes (if any callback returns
false, an error is thrown), but I think I'd dislike that for similar
reasons.

--
Matthew Leverton