Hello,
Is there any chance that dirname(__FILE__) being exposed as a constant,
i.e. __DIRNAME__?
On Feb 9, 2008 9:42 PM, Pierre Joye [EMAIL PROTECTED] wrote:
Hi Marcus,
On Feb 9, 2008 2:39 PM, Marcus Boerger [EMAIL PROTECTED] wrote:
Hello Pierre,
yeah nice idea. I am wondering if you
Jan Schneider wrote:
Zitat von Jingcheng Zhang [EMAIL PROTECTED]:
Hello,
Is there any chance that dirname(__FILE__) being exposed as a constant,
i.e. __DIRNAME__?
No. Constants are per request, dirname(__FILE__) is obviously different
per file.
That's not entirely true, isn't it? Think
-1. Keep the query functions and return FALSE. No need to unnecessarily
break b/c for scripts that were just trying to do the right thing by coping
with both possibilities. It's just one more roadblock to PHP 6 adoption.
Hello,
i've written the following code using Etiennes LSB. But I'm facing some
problems.
?php
class A {
function foo() {
echo get_called_class();
}
}
class B extends A {
}
class C {
function moo() {
B::foo();
}
Gregory Beaver wrote:
Hi Marcus,
FYI, this change:
http://cvs.php.net/viewvc.cgi/php-src/ext/spl/spl_directory.c?view=diffr1=1.146r2=1.147
breaks about 20 tests in phar, it's a potentially serious BC break. I
understand the reasoning behind it, but you may find other users up in
arms.
Hi Marcus,
FYI, this change:
http://cvs.php.net/viewvc.cgi/php-src/ext/spl/spl_directory.c?view=diffr1=1.146r2=1.147
breaks about 20 tests in phar, it's a potentially serious BC break. I
understand the reasoning behind it, but you may find other users up in
arms. The main problem is that this
Hi!
1) Ternary support for values
setting = ${value?1:2}
I think it's an overkill. If you need PHP, write it in PHP. Building
another programming language into the config system looks wrong to me.
It's complex enough as it is. We already have the programming language,
and we have
Hello there,
Just wondering if there is any interest in bringing w32api up to speed.
The docs say it was moved to PECL as of 5.1.0, however is this not the
case. Rumor has it that it was to be replaced by ffi, however again,
this is not the case (ffi is in alpha and probably dead).
Anyone
Is there any chance that dirname(__FILE__) being exposed as a constant,
i.e. __DIRNAME__?
No. Constants are per request, dirname(__FILE__) is obviously different
per file.
Actually, just as __FILE__, __LINE__, __CLASS__ etc. dirname(__FILE__)
can be a parser constant. And if somebody
