Hi Marcus,
so here's my take on the matters. For 5.4 we collect ideas and implement
them. So that 5.4 comes out with mostly PECL. I guess we can collect
action
items on Lukas' wiki.
Greg tells me he's been working so hard on ext/phar lately that Pyrus is
still pre-alpha - it's not going to be ready in time for 5.3. So your
approach sounds good to me...
Lukas?
- Steph
marcus
Saturday, February 16, 2008, 2:05:06 AM, you wrote:
I'm with Dmitry - but syntax aside, the only way this becomes even
halfway
important is if the whole PECL scenario is sorted out in a way that makes
good sense to the end users.
Back to square one. Sorry guys but sooner or later this has to be dealt
with. We need to be sure of what a PHP installation is likely to mean...
to
everybody.
- Steph
----- Original Message -----
From: "Dmitry Stogov" <[EMAIL PROTECTED]>
To: "PHP Internals List" <internals@lists.php.net>
Cc: <[EMAIL PROTECTED]>; "Marcus Boerger" <[EMAIL PROTECTED]>; "Andi
Gutmans"
<[EMAIL PROTECTED]>; "Jani Taskinen" <[EMAIL PROTECTED]>
Sent: Friday, February 15, 2008 2:38 PM
Subject: Re: [PHP-DEV] [RFC] Conditional INI support
The idea makes sense too, but mix of C and SH syntax isn't good.
Dmitry.
BuildSmart wrote:
Now that what-if's are occurring in the theoretical world of
intelligent
INI, what about file testing capabilities so that the following can be
used to preload extensions by existance?
#if -f ${EXTENSIONS_DIR}/gd.so
extension=gd.so
#endif
or some other syntax that allows testing to include an extension
On Feb 15, 2008, at 8:19 AM, Jani Taskinen wrote:
Currently UNDEFINED would be just string 'UNDEFINED'.
Doesn't atoi() for non-numeric string make it 0 ??
(or null..:) So that would work without changing anything..
--Jani
Dmitry Stogov kirjoitti:
I think it will work.
#ifdef UNDEFINED > 5 (false)
#ifdef UNDEFINED <= 5 (true)
(but anyway I think it is possible to find out an unclear condition)
Dmitry.
Marcus Boerger wrote:
Hello Dmitry,
shouldn't this be like in C/C++ where a non existing value is
treated like
an empty string which behaves like false in boolean evaluations?
marcus
Friday, February 15, 2008, 11:25:42 AM, you wrote:
#if defined(PHP_MAJOR_VERSION) && PHP_MAJOR_VERSION >= 6
extension="unicode.so"
#endif
Here PHP_MAJOR_VERSION is a PHP constant that is not defined in
php-5.3 but might be defined in the future version.
Dmitry.
Jani Taskinen wrote:
On Fri, 2008-02-15 at 13:02 +0300, Dmitry Stogov wrote:
Jani Taskinen wrote:
c) We can use just "value" insted of ${value} in conditions.
Yup. ${foobar} is actually not any "variable" per se, but just a
reference to existing ini entry in the file. And I don't think
that
needs to change.
Oh, I see. Then we can use just "$string" (or "$str.str") for ini
entries and "string" for PHP constants. We can also implement
defined() macro-function, to check if constant defined.
Why? Don't make php.ini parsing any more complex than it already
is(n't).
Any string which can pass as constant will have that constant's
(or
environment variable) value. Why do you need any "variable" in
there
anyway? And why do you need defined() ??? (examples please? :)
--Jani
Best regards,
Marcus
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
-- Dale
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Best regards,
Marcus
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
