Hey,
Just wanted to thank everyone who helped get PHP 5.1 out of the door
after a lot of efforts.
Special thanks to Steph who stepped up to make the upgrading guide
happen. I think this should become a standard for future PHP releases.
Also thanks to Ilia who picked up the last few rounds of PH
Zeev Suraski wrote:
For those of you who submitted patches to 5.1 since RC1 - do you
believe that we need another RC or can we go ahead and roll 5.1 final
and run a sanity test for 24 hours? I went over the patches, none of
them appears to be too dangerous, but if any of you thinks
different
At 11:31 01/09/2005, Derick Rethans wrote:
On Wed, 31 Aug 2005, Derick Rethans wrote:
> On Tue, 30 Aug 2005, Zeev Suraski wrote:
>
> > For those of you who submitted patches to 5.1 since RC1 - do you
believe that
> > we need another RC or can we go ahead and roll 5.1 final and run a
sanity tes
On Wed, 31 Aug 2005, Ondrej IvaniÄ wrote:
Jani Taskinen wrote:
On Tue, 30 Aug 2005, Andrei Zmievski wrote:
On Aug 30, 2005, at 10:30 AM, Rasmus Lerdorf wrote:
Also, I see the following 6 failed test cases on my Linux box:
-Bug #16069 [ext/iconv/tests/bug16069.phpt]
According to the last
On Thu, 1 Sep 2005, Derick Rethans wrote:
On Wed, 31 Aug 2005, Derick Rethans wrote:
On Tue, 30 Aug 2005, Zeev Suraski wrote:
For those of you who submitted patches to 5.1 since RC1 - do you believe that
we need another RC or can we go ahead and roll 5.1 final and run a sanity test
for 24 ho
On Wed, 31 Aug 2005, Derick Rethans wrote:
> On Tue, 30 Aug 2005, Zeev Suraski wrote:
>
> > For those of you who submitted patches to 5.1 since RC1 - do you believe
> > that
> > we need another RC or can we go ahead and roll 5.1 final and run a sanity
> > test
> > for 24 hours? I went over the
Done. All distros should have at least 2.6.8. Most have 2.6.16 or above..
--Jani
On Wed, 31 Aug 2005, Rob Richards wrote:
I would suggest bumping up the libxm2 minimum version to 2.6.8. Had forgotten
about this until a recent bug, but 2.6.6 and 2.6.7 can cause memory corruption
that
Rasmus,
please send an update what you think you can do on your side...
Thanks,
Andi
At 08:33 PM 8/30/2005, Wez Furlong wrote:
http://bugs.php.net/search.php?cmd=display&status=Open&bug_type%5B%5D=PDO+related
http://pecl.php.net/bugs/search.php?cmd=display&status=Open&package_name%5B%5D=PDO&pa
I would suggest bumping up the libxm2 minimum version to 2.6.8. Had
forgotten about this until a recent bug, but 2.6.6 and 2.6.7 can cause
memory corruption thats fixed in 2.6.8.
Rob
Zeev Suraski wrote:
For those of you who submitted patches to 5.1 since RC1 - do you
believe that we need ano
Jani Taskinen wrote:
On Tue, 30 Aug 2005, Andrei Zmievski wrote:
On Aug 30, 2005, at 10:30 AM, Rasmus Lerdorf wrote:
Also, I see the following 6 failed test cases on my Linux box:
-Bug #16069 [ext/iconv/tests/bug16069.phpt]
According to the last two comments in that bug report, glibc icon
On Tue, 30 Aug 2005, Zeev Suraski wrote:
> For those of you who submitted patches to 5.1 since RC1 - do you believe that
> we need another RC or can we go ahead and roll 5.1 final and run a sanity test
> for 24 hours? I went over the patches, none of them appears to be too
> dangerous, but if any
On Tue, 30 Aug 2005, Andrei Zmievski wrote:
On Aug 30, 2005, at 10:30 AM, Rasmus Lerdorf wrote:
Also, I see the following 6 failed test cases on my Linux box:
-Bug #16069 [ext/iconv/tests/bug16069.phpt]
According to the last two comments in that bug report, glibc iconv() does not
support CP
http://bugs.php.net/search.php?cmd=display&status=Open&bug_type%5B%5D=PDO+related
http://pecl.php.net/bugs/search.php?cmd=display&status=Open&package_name%5B%5D=PDO&package_name%5B%5D=PDO_FIREBIRD&package_name%5B%5D=PDO_MYSQL&package_name%5B%5D=PDO_OCI&package_name%5B%5D=PDO_ODBC&package_name%5B%5D
Rasmus Lerdorf wrote:
> -Bug #31142 test #2 (imap_mail_compose() generates incorrect output)
> [ext/imap/tests/bug31142_2.phpt]
This bug was just fixed.
Ilia
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hello Andrei,
Tuesday, August 30, 2005, 10:16:43 PM, you wrote:
> On Aug 30, 2005, at 10:30 AM, Rasmus Lerdorf wrote:
>> Also, I see the following 6 failed test cases on my Linux box:
>>
>> -Bug #16069 [ext/iconv/tests/bug16069.phpt]
> According to the last two comments in that bug report, glibc
On Tue, 30 Aug 2005, Rasmus Lerdorf wrote:
> Would probably help if I included the diffs:
>
> > -Bug #33414 [2] (Comprehensive list of incorrect days returned after
> > strotime() / date() tests) [ext/date/tests/bug33414-2.phpt]
>
> 033+ result=Wednesday 1970-01-07 00:00:00 PST 0
> 033- result=W
On Aug 30, 2005, at 10:30 AM, Rasmus Lerdorf wrote:
Also, I see the following 6 failed test cases on my Linux box:
-Bug #16069 [ext/iconv/tests/bug16069.phpt]
According to the last two comments in that bug report, glibc iconv()
does not support CP932 and this test should be skipped instead of
Would probably help if I included the diffs:
> -Bug #33414 [2] (Comprehensive list of incorrect days returned after
> strotime() / date() tests) [ext/date/tests/bug33414-2.phpt]
033+ result=Wednesday 1970-01-07 00:00:00 PST 0
033- result=Wednesday 1970-01-06 00:00:00 PST 0
> -Bug #16069 [ext/ico
Wez Furlong wrote:
> There's a bunch of open PDO bugs that need to be fixed before we go
> with 5.1 final.
Do you have some sort of plan/timeline for these getting fixed? Do you
need some help? We can't wait indefinitely on PDO. If you have a list
of outstanding issues I can throw some resource
There's a bunch of open PDO bugs that need to be fixed before we go
with 5.1 final.
--Wez.
On 8/29/05, Zeev Suraski <[EMAIL PROTECTED]> wrote:
> For those of you who submitted patches to 5.1 since RC1 - do you believe
> that we need another RC or can we go ahead and roll 5.1 final and run a
> san
For those of you who submitted patches to 5.1 since RC1 - do you believe
that we need another RC or can we go ahead and roll 5.1 final and run a
sanity test for 24 hours? I went over the patches, none of them appears to
be too dangerous, but if any of you thinks differently, let me know.
Zeev
What's the status with 5.1 release? Somehow I've got
the feeling that nobody's doing anything about it after
the unicode merge..? (nobody == Dmitry :)
And who is the RM for PHP_5_1 branch anyway?
--Jani
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe,
If I understood correctly, the fixed XML_RPC pear package
was updated to the PHP_5_1 branch already. Why is ext/xmlrpc
still required?
--Jani
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Per my online conversation with Andi, I will be committing the gcov
stuff prior to the deep-freeze tomorrow morning -- expect a cvs commit
and a follow-up e-mail on usage early tomorrow morning.
John
On Mon, 2005-08-08 at 23:11 -0700, Andi Gutmans wrote:
> At 07:57 AM 8/9/2005 +0200, Sebastian Be
Andi et al,
I am hoping to finish rough draft of HTTP input decoding today. I'd
rather not merge in half-finished stuff. Besides that, do you think we
need a write up on what has been changed in the core, new APIs,
function upgrade guidelines, etc?
Ping me on IM if you can.
-Andrei
On Aug
On Tue, 9 Aug 2005, Sebastian Bergmann wrote:
> Andi Gutmans schrieb:
> > I just branched off PHP 5.1 (PHP_5_1).
>
> Does that mean that PHP_5_1 is in feature-freeze or are changes like
> the one Derick proposed (making type hint violations throw an exception
> instead of raising a fatal error
Andi Gutmans schrieb:
> Feature-freeze.
Okay.
--
Sebastian Bergmann http://www.sebastian-bergmann.de/
GnuPG Key: 0xB85B5D69 / 27A7 2B14 09E4 98CD 6277 0E5B 6867 C514 B85B 5D69
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.ne
At 07:57 AM 8/9/2005 +0200, Sebastian Bergmann wrote:
Andi Gutmans schrieb:
> I just branched off PHP 5.1 (PHP_5_1).
Does that mean that PHP_5_1 is in feature-freeze or are changes like
the one Derick proposed (making type hint violations throw an exception
instead of raising a fatal error) s
Andi Gutmans schrieb:
> I just branched off PHP 5.1 (PHP_5_1).
Does that mean that PHP_5_1 is in feature-freeze or are changes like
the one Derick proposed (making type hint violations throw an exception
instead of raising a fatal error) still possible for PHP 5.1?
--
Sebastian Bergmann
Hi all,
I just branched off PHP 5.1 (PHP_5_1). I will roll a tarball later on or
tomorrow for RC1. Please from now on commit bug fixes to both PHP_5_1 and
HEAD (and if critical, I suggest to do so with PHP_5_0 too in case we need
to release another mini release). We should be able to kill it o
Today I was trying to reduce the number of tests that fail on my solaris
boxes. (because I don't remember to see PHP pass all the tests)
I needed to patch a couple of tests that didn't work well on that plataform.
Detailed explanation (I hope):
ext/date/tests/bug32555.phpt
strftime is system/lo
Hello Andi,
na you convinced me. I only wanted to make fun out of the situation and
we really all forgot about the issue, didn't we?
regards
marcus
Thursday, July 28, 2005, 11:45:52 PM, you wrote:
> We'll save the discussion for after the Unicode merge but I actually came
> up with some very
At 11:59 PM 7/28/2005 +0200, Marcus Boerger wrote:
Hello Andi,
na you convinced me. I only wanted to make fun out of the situation and
we really all forgot about the issue, didn't we?
:)
Andi
regards
marcus
Thursday, July 28, 2005, 11:45:52 PM, you wrote:
> We'll save the discussion f
We'll save the discussion for after the Unicode merge but I actually came
up with some very good reasons why it's dangerous. Marcus just likes to
ignore them :)
At 10:51 PM 7/27/2005 +0200, Marcus Boerger wrote:
Hello Adam,
"we accepted that availability of enough excuses to delay it furthe
Honestly it's only a patch to the build system to add basically
--enable-gcov to the configure (much like --enable-debug). Basically it
just checks for the proper libraries and utilities during configure as
it should and if everything is okay builds PHP with the proper compile-
time flags and libr
Okay cool. In any case, when it's convenient sending it over to internals@
(maybe after OSCON) makes sense as many here weren't at ApacheCon EU.
Andi
At 08:37 PM 7/28/2005 +0200, Marcus Boerger wrote:
Hello Andi,
during apacheCon EU it only needed a few more tweaks which should be done
by n
Hello Andi,
during apacheCon EU it only needed a few more tweaks which should be done
by now (john?). And i can only say it looks really great! But anyway it's
sense is to produce more tests where we don't have any yet. And since
writing tests requires a lot of work most people hate i guess we c
Is this an extension or changes to the core? Do you already have a patch?
In any case, this would have to wait until earliest after the branch and go
to HEAD.
But I suggest to first make a proposal and show what you're planning on
doing here on internals@
Andi
At 03:02 PM 7/27/2005 -0400, Joh
Hello Adam,
"we accepted that availability of enough excuses to delay it further
in the hope we never implement it :-)"
To be honest, we all - obviously including you - forgot about the issue
completley and only realized it during beta process. And for a thing that
need so heavy testing sin
I can't remember the status of __toString(), but I thought we agreed
improving it was a 5.1 feature, pending an investigation to make sure
we were able to handle this gracefully in the engine.
I don't remember seeing any updates to this code, so I wanted to see
if I missed it, or if we decided to
I'd also like to get this in to PHP 5.1+ after we branch before Unicode:
http://blog.coggeshall.org/archives/204_Code_Coverage_Support_for_PHP_5.html
John
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
These should be definately fixed:
http://bugs.php.net/bug.php?id=33772&edit=1 (destruct thing)
http://bugs.php.net/bug.php?id=33723&edit=1 (apache + php_admin_value issue)
These would be nice to get fixed:
http://bugs.php.net/bug.php?id=31177&edit=1 (memory leak)
http:/
We probably shouldn't merge anything in until after OSCON. When is
Dmitriy back?
-Andrei
On Jul 26, 2005, at 5:50 PM, Andi Gutmans wrote:
Hi all,
As planned (a tiny bit delayed), I'd like to RC1 PHP 5.1 within the
next few days. I suggest to aim for Tuesday in a week.
If there are any cr
Hi all,
As planned (a tiny bit delayed), I'd like to RC1 PHP 5.1 within the next
few days. I suggest to aim for Tuesday in a week.
If there are any critical issues which need addressing please email me.
As previously mentioned, I'd like to branch of PHP_5_1 after RC1 in order
to allow for the
On Tuesday 21 June 2005 05:30, Andi Gutmans wrote:
> Hi,
>
> You can reach Beta 2 at http://snaps.php.net/~andi/
> If there are no surprise show stoppers I'll put it live tomorrow evening.
../configure --with-apxs=/usr/local/apache/bin/apxs --with-openssl
--with-curl --with-zlib --with-bz2 --enabl
On Tue, 21 Jun 2005, Nuno Lopes wrote:
> There are also a couple of tests related with strtotime() (or date()) that
> fail on Solaris:
> http://mega.ist.utl.pt/~ncpl/php_test_results_20050621_2035.txt
That is a broken date() implementation AFAICT. That's next on my todo
list.
Derick
--
Derick
Hi Andi,
On Tuesday 21 June 2005 04.30, Andi Gutmans wrote:
> Hi,
>
> You can reach Beta 2 at http://snaps.php.net/~andi/
> If there are no surprise show stoppers I'll put it live tomorrow
> evening.
Here are some test results from various systems:
FreeBSD 5.4 alpha:
Number of tests : 1907
It's a build related tweak, so it really does need to get in there;
commited it this morning.
--Wez.
On 6/21/05, Andi Gutmans <[EMAIL PROTECTED]> wrote:
> What config.m4 patch? Is it crucial for Beta 2? I don't want to keep Beta 2
> delayed indefinitely... It's only worth it if it's a critical bu
Hello Andi,
current head with a few more exts all build in:
=
TIME END 2005-06-21 20:56:57
=
TEST RESULT SUMMARY
--
What config.m4 patch? Is it crucial for Beta 2? I don't want to keep Beta 2
delayed indefinitely... It's only worth it if it's a critical bug.
Andi
At 06:30 PM 6/21/2005 -0400, Wez Furlong wrote:
On 6/21/05, Ilia Alshanetsky <[EMAIL PROTECTED]> wrote:
> A large chunk of tests fails because PHP
Yeah it's definitely worrying. I am hoping that Derick will get those tests
sorted out as I was hoping to RC in a short time frame. Hopefully when Beta
2 gets out there we'll get some more testing.
Andi
At 08:41 PM 6/21/2005 +0200, Rasmus Lerdorf wrote:
Andi Gutmans wrote:
> Hi,
>
> I just ta
On 6/21/05, Ilia Alshanetsky <[EMAIL PROTECTED]> wrote:
> A large chunk of tests fails because PHP cannot run them, missing DB
> connection. This is true for MySQLi tests and PDO_ODBC tests, the latter
> requires a patch to prepare.inc, that only IBMers can apply.
Andi Gutmans wrote:
Hi,
You can reach Beta 2 at http://snaps.php.net/~andi/
If there are no surprise show stoppers I'll put it live tomorrow evening.
Andi
SuSE 9.1 (9.2 packages)
./configure --disable-cgi --enable-cli --with-mysql=/usr/local/mysql
--with-mysqli=/usr/local/mysql/bin/mysql_co
A large chunk of tests fails because PHP cannot run them, missing DB
connection. This is true for MySQLi tests and PDO_ODBC tests, the latter
requires a patch to prepare.inc, that only IBMers can apply.
Ilia
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://
Andi Gutmans schrieb:
Please check new packages at http://snaps.php.net/~andi
Will release tomorrow if there's not another major screwup :)
Hi Andi,
more than 160 tests failed on the IRIX 6.5 platform. Test results are
under http://www.irixworld.net/php_test_results_20050621_2239.txt
TEST
Sebastian Nohn wrote:
It compiles fine.
Andi Gutmans wrote:
Please check new packages at http://snaps.php.net/~andi
Will release tomorrow if there's not another major screwup :)
There are still some strtotime() issues to work out.
echo date("m d Y",strtotime("Jan 14, 2004"));
correctly giv
Derick Rethans wrote:
> On Tue, 21 Jun 2005, Rasmus Lerdorf wrote:
>
>
>>Andi Gutmans wrote:
>>
>>>Hi,
>>>
>>>I just talked to Derick, and we think it's best to post Beta 2
>>>regardless to get more feedback and testing.
>>>In any case, this is definitely something that should be addressed
>>>(al
On Tue, 21 Jun 2005, Rasmus Lerdorf wrote:
> Andi Gutmans wrote:
> > Hi,
> >
> > I just talked to Derick, and we think it's best to post Beta 2
> > regardless to get more feedback and testing.
> > In any case, this is definitely something that should be addressed
> > (although it seems that it wa
Andi Gutmans wrote:
> Hi,
>
> I just talked to Derick, and we think it's best to post Beta 2
> regardless to get more feedback and testing.
> In any case, this is definitely something that should be addressed
> (although it seems that it was never documented).
My worry is mostly that this is a br
Hi,
I just talked to Derick, and we think it's best to post Beta 2 regardless
to get more feedback and testing.
In any case, this is definitely something that should be addressed
(although it seems that it was never documented).
Thanks,
Andi
At 07:28 PM 6/21/2005 +0200, Rasmus Lerdorf wrote
On Tue, 21 Jun 2005, Rasmus Lerdorf wrote:
> There are still some strtotime() issues to work out.
>
> echo date("m d Y",strtotime("Jan.14, 2004"));
>
> gives: 06 21 2005
Fixed in CVS.
Derick
--
Derick Rethans
http://derickrethans.nl | http://ez.no | http://xdebug.org
--
PHP Internals - PHP
Sebastian Nohn wrote:
> It compiles fine.
>
> Andi Gutmans wrote:
>
>>Please check new packages at http://snaps.php.net/~andi
>>Will release tomorrow if there's not another major screwup :)
There are still some strtotime() issues to work out.
echo date("m d Y",strtotime("Jan 14, 2004"));
corre
It compiles fine.
Andi Gutmans wrote:
> Please check new packages at http://snaps.php.net/~andi
> Will release tomorrow if there's not another major screwup :)
>
> Thanks.
> Andi
>
> At 07:15 AM 6/21/2005 -0700, Andi Gutmans wrote:
>
>> OK I'll check into it.
>> Thanks,
>> Andi
>>
>> At 11:47 A
Please check new packages at http://snaps.php.net/~andi
Will release tomorrow if there's not another major screwup :)
Thanks.
Andi
At 07:15 AM 6/21/2005 -0700, Andi Gutmans wrote:
OK I'll check into it.
Thanks,
Andi
At 11:47 AM 6/21/2005 +0200, Derick Rethans wrote:
On Tue, 21 Jun 2005, Sebas
OK I'll check into it.
Thanks,
Andi
At 11:47 AM 6/21/2005 +0200, Derick Rethans wrote:
On Tue, 21 Jun 2005, Sebastian Nohn wrote:
> Andi Gutmans wrote:
>
> > You can reach Beta 2 at http://snaps.php.net/~andi/
> > If there are no surprise show stoppers I'll put it live tomorrow evening.
>
> htt
Hi Andi,
The date extension does not appear to have been tagged and consequently
not part of the release.
Ilia
Andi Gutmans wrote:
Hi,
You can reach Beta 2 at http://snaps.php.net/~andi/
If there are no surprise show stoppers I'll put it live tomorrow evening.
Andi
--
PHP Internals - PH
Thanks. It now compiles, but fails a couple of tests :)
The report: http://mega.ist.utl.pt/~ncpl/php_test_results_20050621_1205.txt
But at least the 'Zend/tests/unset_cv07.phpt' test is borked, because it
expects errors in html, and it doesn't set the 'html_errors=1', and
'docref_root' and 'do
Fixed in CVS.
--Jani
On Tue, 21 Jun 2005, Nuno Lopes wrote:
I still have a problem in the configure script.
With the package you post:
checking for embedded SAPI library support... no
./configure: syntax error at line 9265: `;' unexpected
checking that line, there is a problem indee
On Tue, 21 Jun 2005, Sebastian Nohn wrote:
> Andi Gutmans wrote:
>
> > You can reach Beta 2 at http://snaps.php.net/~andi/
> > If there are no surprise show stoppers I'll put it live tomorrow evening.
>
> http://bugs.php.net/33420
The whole directory ext/date is missing from the tarball.
Deric
I still have a problem in the configure script.
With the package you post:
checking for embedded SAPI library support... no
./configure: syntax error at line 9265: `;' unexpected
checking that line, there is a problem indeed:
header_path=sapi/embed/php_embed.h
for header_file in ; do
Andi Gutmans wrote:
You can reach Beta 2 at http://snaps.php.net/~andi/
If there are no surprise show stoppers I'll put it live tomorrow evening.
http://bugs.php.net/33420
Sebastian
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hi,
You can reach Beta 2 at http://snaps.php.net/~andi/
If there are no surprise show stoppers I'll put it live tomorrow evening.
Andi
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Okay. Ping me about it when you've made progress.
At 04:12 PM 6/17/2005 +0200, Derick Rethans wrote:
On Wed, 15 Jun 2005, Andi Gutmans wrote:
> I'm waiting to finalize the following:
> - Date changes (Waiting for green light from Derick. I still saw some
activity
> today.)
Except for some bu
On Wed, 15 Jun 2005, Andi Gutmans wrote:
> I'm waiting to finalize the following:
> - Date changes (Waiting for green light from Derick. I still saw some activity
> today.)
Except for some bug that keeps most of the tests failing all is set now.
I do think we need to fix this first though - work
At 20:16 16/06/2005, Marcus Boerger wrote:
Hello Zeev,
Thursday, June 16, 2005, 7:12:49 PM, you wrote:
> Marcus,
> If you read what I said in my emails on this topic, it's clear that I know
> that this is the case. As I said, this approach has the side effect of
> creating an empty placeholde
Hello Zeev,
Thursday, June 16, 2005, 7:12:49 PM, you wrote:
> Marcus,
> If you read what I said in my emails on this topic, it's clear that I know
> that this is the case. As I said, this approach has the side effect of
> creating an empty placeholder if the variable to be checked doesn't
> e
Marcus,
If you read what I said in my emails on this topic, it's clear that I know
that this is the case. As I said, this approach has the side effect of
creating an empty placeholder if the variable to be checked doesn't
exist. I also said that I think it would usually make more sense to si
Hello Sebastian,
how does this allow you to check for subscriptions?
Are you going to write a subscription walker? Wouldn't that be the
opposite of fast?
marcus
Tuesday, June 14, 2005, 3:45:33 PM, you wrote:
> Robert Cummings wrote:
>> [...]
>>
>> On that note, how comes there's a $GLOBAL a
Hello Zeev,
though the idea is nice and & does what we want here to a certain level it
still doesn't allow to implement ifsetor() or coalesce() or any other flavor
described here as proved by the following snippet:
[EMAIL PROTECTED] ~ $ php -r 'function ifsetor(&$a, $def=false) { return
isset(
Hi,
Just to give a status update on PHP 5.1 Beta 2:
- PDO Fix (Wez has already given me the green light to go ahead).
I'm waiting to finalize the following:
- Date changes (Waiting for green light from Derick. I still saw some
activity today.)
- Patch to allow internal functions to return refer
On Tue, 2005-06-14 at 09:45, Sebastian Mendel wrote:
> Robert Cummings wrote:
>
> > [...]
> >
> > On that note, how comes there's a $GLOBAL array and not a $LOCAL array
> > for vars declared in the immediate scope :)
>
> you can use get_defined_vars()
>
> http://www.php.net/get_defined_vars
Yo
Great.
Thanks a lot for the improvement.
--
Sven
> At 17:10 14/06/2005, Sven Fuchs wrote:
>> > This implementation of issetor() actually works fine, except it does
>> > pollute the symbol tables with empty variables ($a and $b in this
>> > examples are created, as nulls).
>>
>>What are the conse
There is one case though, which can still not be implemented (probably?) by
users, and that's a coalesce function, since that would require fetching
values by using func_get_args(), which doesn't return references.
So the only way I could imagine implementing such coalesce() function would
be like
At 17:10 14/06/2005, Sven Fuchs wrote:
> This implementation of issetor() actually works fine, except it does
> pollute the symbol tables with empty variables ($a and $b in this
> examples are created, as nulls).
What are the consequences of polluting the symbol tables this way?
Well, it will
Personally, I doubt this is a problem.. I mean, how many ifsetor() variables
are we talking here? You call the function, so therefor the variable could
be set, otherwise you wouldn't be checking for it. In the case it was set,
it would've been in the symbol table anyway.
Ron
"Sven Fuchs" <[EMAIL
Personally, I doubt this is a problem.. I mean, how many ifsetor() variables
are we talking here? You call the function, so therefor the variable could
be set, otherwise you wouldn't be checking for it. In the case it was set,
it would've been in the symbol table anyway.
Ron
"Sven Fuchs" <[EMAIL
> This implementation of issetor() actually works fine, except it does
> pollute the symbol tables with empty variables ($a and $b in this
> examples are created, as nulls).
What are the consequences of polluting the symbol tables this way?
Should this issetor() be considered a "bad practice", pro
Hi Zeev,
You're absolutely right.. How awful of me that I didn't see this coming.
Honestly, what's the point of having an ifsetor() in PHP, when people can
obviously write it themselves? Everybody wants a slighty different
implementation of an ifsetor(), ifnotemptyor(), coalesce(), etc... Why are
Hmm, you're right.. so the reference "&" already takes care of this...
Well, then I don't see the point of the whole ifsetor() discussions...
people can implement this themselves.
Ron
"Sebastian Mendel" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Ron Korving wrote:
>
> >> funct
At 16:54 14/06/2005, Sebastian Mendel wrote:
Ron Korving wrote:
>> function ifsetor(&$var, $default = null) {
>> return isset($var) ? $var : $default;
>> }
>>
>> echo ifsetor($a, 'foo');
>> echo $a, $b;
>> echo ifsetor($a, 'foo');
>> echo isset($a) ? 'is set' : 'not set';
>>
>> expected resu
Ron Korving wrote:
>> function ifsetor(&$var, $default = null) {
>> return isset($var) ? $var : $default;
>> }
>>
>> echo ifsetor($a, 'foo');
>> echo $a, $b;
>> echo ifsetor($a, 'foo');
>> echo isset($a) ? 'is set' : 'not set';
>>
>> expected result:
>>
>> foo
>> Notice: Undefined variable: a
No, ifsetor() is not possible in user land, because it generates notices,
and a php core function ifsetor() would not generate notices. That's really
the way it has to be.
Ron
"Sven Fuchs" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Why isn't is possible in userland? Is there a
Robert Cummings wrote:
> [...]
>
> On that note, how comes there's a $GLOBAL array and not a $LOCAL array
> for vars declared in the immediate scope :)
you can use get_defined_vars()
http://www.php.net/get_defined_vars
--
Sebastian Mendel
www.sebastianmendel.de
www.sf.net/projects/phpdateti
Why isn't is possible in userland? Is there any problem with using
this?
function ifsetor(&$var, $default = null) {
return isset($var) ? $var : $default;
}
echo ifsetor($a, 'foo');
echo $a, $b;
echo ifsetor($a, 'foo');
echo isset($a) ? 'is set' : 'not set';
expected result:
foo
Notice: Und
But how about this..:
Let's not implement functions that do what you want to achieve, but extend
PHP in whatever way necessary that would enable you to write such a function
yourself?
Say for example that prepending @ to function parameters would make it
possible to call the function with an unse
M. Sokolewicz wrote:
>> $x = (isset($ANY_var) ? $ANY_var : 'Default Value');
>> by
>> $x = ifsetor($ANY_var, 'Default Value');
>>
I must say I fully agree; I don't see any use in putting extra functions
in the PHP namespace just because people don't want to type a couple of
extra characters.
i
Robert Cummings wrote:
On Tue, 2005-06-14 at 01:31, Ron Korving wrote:
Jason, you are absolutely right.. this is not about input filtering at all.
It's about replacing:
$x = (isset($ANY_var) ? $ANY_var : 'Default Value');
by
$x = ifsetor($ANY_var, 'Default Value');
So, Robert's solution is no
On Tue, 2005-06-14 at 01:31, Ron Korving wrote:
> Jason, you are absolutely right.. this is not about input filtering at all.
> It's about replacing:
>
> $x = (isset($ANY_var) ? $ANY_var : 'Default Value');
> by
> $x = ifsetor($ANY_var, 'Default Value');
>
> So, Robert's solution is no real solut
Jason, you are absolutely right.. this is not about input filtering at all.
It's about replacing:
$x = (isset($ANY_var) ? $ANY_var : 'Default Value');
by
$x = ifsetor($ANY_var, 'Default Value');
So, Robert's solution is no real solution if you ask me. But again, it would
be best, if there was no
Ondrej and Jason,
Just pondering the proposed coalesce() variants in the context of
Ondrej's scenario I came upon two thoughts.
I forgot to mention the nice single parameter case of a coalesce()
function like this, which would return null if not set:
$x = coalesce($REQUEST['x']);
Also, t
1 - 100 of 512 matches
Mail list logo
