Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:35483 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 41739 invoked by uid 1010); 14 Feb 2008 09:08:01 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 41724 invoked from network); 14 Feb 2008 09:08:01 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 Feb 2008 09:08:01 -0000 Authentication-Results: pb1.pair.com header.from=lars@strojny.net; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=lars@strojny.net; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain strojny.net designates 85.10.204.248 as permitted sender) X-PHP-List-Original-Sender: lars@strojny.net X-Host-Fingerprint: 85.10.204.248 milch.schokokeks.org Received: from [85.10.204.248] ([85.10.204.248:55561] helo=milch.schokokeks.org) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id FE/F3-33682-0F404B74 for ; Thu, 14 Feb 2008 04:08:00 -0500 Received: from [192.168.0.8] (xdsl-87-79-231-250.netcologne.de [::ffff:87.79.231.250]) (AUTH: PLAIN lars@schokokeks.org, SSL: TLSv1/SSLv3,256bits,CAMELLIA256-SHA) by milch.schokokeks.org with esmtp; Thu, 14 Feb 2008 10:07:57 +0100 id 000000000002000A.0000000047B404ED.00006912 To: Jochem Maas Cc: Pierre Joye , PHP Internals List In-Reply-To: <47B383C1.3030303@iamjochem.com> References: <1202917630.25345.6.camel@localhost> <1202943887.7717.7.camel@localhost> <47B383C1.3030303@iamjochem.com> Date: Thu, 14 Feb 2008 10:07:56 +0100 Message-ID: <1202980076.7717.12.camel@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit X-Mailer: Evolution 2.21.5 Subject: Re: [PHP-DEV] [RFC] prepend_include_path()/append_include_path() From: lars@strojny.net (Lars Strojny) Hi Jochem, Am Donnerstag, den 14.02.2008, 00:56 +0100 schrieb Jochem Maas: > I think Lars has a point ... maybe set_include_path() could > be given a second parameter instead to mitigate the need for seperate > funcs?: > > set_include_path('foo', INCPATH_OVERRIDE); // default > set_include_path('foo', INCPATH_APPEND); > set_include_path('foo', INCPATH_PREPEND); Thanks for your support, but this seems counter intuitive. Why should *set*_include_path() be used to *append* or *prepend* to the include path? Also learning another mouthful of constants is maybe suboptimal. Getting used to prepend_/append_...() is easy from my point of view, as the name is derived from what's currently present (set_include_path()). cu, Lars