Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:43036 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 95892 invoked from network); 13 Feb 2009 21:55:36 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 13 Feb 2009 21:55:36 -0000 Authentication-Results: pb1.pair.com header.from=mikko.koppanen@gmail.com; sender-id=pass; domainkeys=bad Authentication-Results: pb1.pair.com smtp.mail=mikko.koppanen@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.128.187 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: mikko.koppanen@gmail.com X-Host-Fingerprint: 209.85.128.187 fk-out-0910.google.com Received: from [209.85.128.187] ([209.85.128.187:27420] helo=fk-out-0910.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 44/79-43210-85CE5994 for ; Fri, 13 Feb 2009 16:55:36 -0500 Received: by fk-out-0910.google.com with SMTP id b27so709135fka.7 for ; Fri, 13 Feb 2009 13:55:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type; bh=GTdLGfl6j/SNgnPVkv6+rI/SpbR43xa4juVmz58j/a4=; b=KeJcIfTxhRXhV/1EW5qdNWg3ccNM6o5ReRupSx2Rt2yKOHokIPfD0NpONiT7x684ge i8jiIINE5PXofozG1Qi7PoGYjbVKYSpCDAR9xRQ8rkpqRdJuYppd6EQv5d22qwNTVTxy +CXoduS2xIMwONwbgQytsBPsYD0wIW3No8me8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=RxE5nkbgDVnWt5jOUFlMdxgcsUUdqtT04mQkzbK0OmNzIqQr50ejMOOJNSPZDD2M4Q GHugSUPfel5qKT9/Q6EYUdOV7U+Fpb9wY6wit9oqhTBG64arNCd9ta/4g1PJBwe6dE2o 4Trgcv3SJYpSkS1QxJey0XWUSQXT6yApxYMWo= MIME-Version: 1.0 Sender: mikko.koppanen@gmail.com Received: by 10.181.158.2 with SMTP id k2mr76951bko.145.1234562133369; Fri, 13 Feb 2009 13:55:33 -0800 (PST) In-Reply-To: References: Date: Fri, 13 Feb 2009 21:55:33 +0000 X-Google-Sender-Auth: c994eee90c0b6b99 Message-ID: <8cf711460902131355g3c916ca7w571b341383d7f9c@mail.gmail.com> To: "David M. Patterson" Cc: internals@lists.php.net Content-Type: multipart/alternative; boundary=0016e6d77c9d69a5100462d3e5a3 Subject: Re: [PHP-DEV] Best/Proper way to process an extension-specific configuration (ini) file. From: mkoppanen@php.net (Mikko Koppanen) --0016e6d77c9d69a5100462d3e5a3 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On Fri, Feb 13, 2009 at 7:31 PM, David M. Patterson < dpatterson@dplhenterprises.com> wrote: > I am writing an extension that requires its own configuration file. > > I would prefer to not re-invent the parse a config file wheel and so, have > been trying to use zend_parse_ini_file() function. Unfortunately, I have > been unable to make this work, so far. > > If someone would either provide a code snippet for this or point me to one, > I'd really appreciate it. > The normal way is to use PHP ini-entries. You can find examples in just about every extension out there. Are you sure you need a separate configuration file for your extension? -- Mikko Koppanen --0016e6d77c9d69a5100462d3e5a3--