Re: Best/Proper way to process an extension-specific configuration (ini) file.
| From: | Pierre Joye | Date: | Fri, 13 Feb 2009 22:11:11 +0000 |
| Subject: | Re: Best/Proper way to process an extension-specific configuration (ini) file. | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-43038@lists.php.net to get a copy of this message | ||
hi,
On Fri, Feb 13, 2009 at 11:01 PM, David M. Patterson
<dpatterson@dplhenterprises.com> wrote:
>
> On Fri, Feb 13, 2009 at 7:31 PM, David M. Patterson <
> Unfortunately, standard php.ini entries won't suffice in this case.
> The extension's config file will contain indeterminate keys and the normal
> php.ini processing requires that all keys be known at compile time (as far
> as I can tell).
You can use the ini parser function or its internal equivalent. An
example can be found in pecl/hidef
(http://cvs.php.net/viewvc.cgi/pecl/hidef/), it is an extension
defining custom constants at init time, like core constants.
Cheers,
--
Pierre
http://blog.thepimp.net | http://www.libgd.org