-1 for 5.3
0 for 5.x (if there ever will be one)
+1 for 6.0
On 7.7.2009 2:52 Uhr, Ilia Alshanetsky wrote:
> Last week or so there was a fairly detailed discussion on the internals
> list regarding type hinting based on my original patch. Since then the
> patch has been revised to address the major
On 7-Jul-09, at 8:43 PM, Rasmus Lerdorf wrote:
That doesn't really change the timing, especially since you said you
have been using it for 2 years. Why pick the week after the 5.3
release
to propose it for 5.3? It makes very little sense to me, and I think
consensus is building that we are
Pierre Joye wrote:
> On Wed, Jul 8, 2009 at 1:04 AM, Greg Beaver wrote:
>
>
>> P.S. pecl for windows support is not in pyrus yet, since pecl4win is
>> completely defunct and there's no alternative.
>>
>
> You mean no support in general for binary package right?
>
The support has not been
On Tue, Jul 7, 2009 at 08:52, Ilia Alshanetsky wrote:
> Last week or so there was a fairly detailed discussion on the internals list
> regarding type hinting based on my original patch. Since then the patch has
> been revised to address the major concerns that were identified (breakage of
> binary
This option sets the default value for the timeout, as though you
manually called stream_set_timeout on the stream.
The behavior is equivalent to using select() to wait for up to the
timeout duration prior to a read or write operation.
PHP does not implement "idle" timeouts; that's an application
-1 for 5.x
+1 for 6.0
Otherwise the Perl 6 guys will starting making their own jokes about
being released before PHP 6.
--Wez.
On Mon, Jul 6, 2009 at 8:52 PM, Ilia Alshanetsky wrote:
> I would like to ask all developers to voice their opinions of whether it
> makes sense to add this to 5.3 or to
That doesn't really change the timing, especially since you said you
have been using it for 2 years. Why pick the week after the 5.3 release
to propose it for 5.3? It makes very little sense to me, and I think
consensus is building that we aren't going to add this to 5.3.
I think half the people
-1
However, this is ONLY because I do not feel PHP 5.3 is the place to put
this. However, I do have to agree with Ilia here that PHP 6 is too far away
and it would be nice to have this feature long before then. I would however,
be very for adding something similar to this patch in a PHP 5.4 releas
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/07/2009 02:52 AM, Ilia Alshanetsky wrote:
> Last week or so there was a fairly detailed discussion on the internals
> list regarding type hinting based on my original patch. Since then the
> patch has been revised to address the major concerns t
Andrei,
PHP represents a major change on every aspect of the language, I think
you gotta appreciate it that even if it were to be released today
there would be sometime before it can certified as production ready in
terms of stability and performance. I'd go on a limb and say that PHP6
is
Rasmus,
Well, 5.3 has been in feature lock for quite some time, its not like
its been a week or two since we went from "features in" phase to
"stabilization" phase.
On 7-Jul-09, at 7:14 PM, Rasmus Lerdorf wrote:
Paul Biggar wrote:
- the RFC process has been wilfully ignored (despite mul
All of the identified issues can be resolved and none of them
represent a major challenge to address. However, if there is no
consensus to put this in the near future (which at this point is 5.3),
I have hard time justifying spending further time on this. The
original patch that was posted,
On Wed, Jul 8, 2009 at 1:04 AM, Greg Beaver wrote:
> P.S. pecl for windows support is not in pyrus yet, since pecl4win is
> completely defunct and there's no alternative.
You mean no support in general for binary package right?
Cheers,
--
Pierre
http://blog.thepimp.net | http://www.libgd.org
Paul Biggar wrote:
> - the RFC process has been wilfully ignored (despite multiple requests)
For me it is pretty hard to take a major feature for 5.3 RFC seriously
when it comes a week after we finally get 5.3 out the door.
-Rasmus
--
PHP Internals - PHP Runtime Development Mailing List
To un
2009/7/7 Johannes Schlüter :
> On Mon, 2009-07-06 at 20:52 -0400, Ilia Alshanetsky wrote:
>> Last week or so there was a fairly detailed discussion on the
>> internals list regarding type hinting based on my original patch.
> Having an "old" 5.3 extension with a typehint expecting an array
> arg_
Hi,
Pyrus is within inches of its first alpha release, and as such I want to
run the new features that affect PECL developers and consumers by those
folks who are affected by them.
Pyrus requires PHP 5.3.0 or newer, and is a dramatic leap forward from
the PEAR Installer.
Relevant docs to PECL ar
On Mon, 2009-07-06 at 20:52 -0400, Ilia Alshanetsky wrote:
> Last week or so there was a fairly detailed discussion on the
> internals list regarding type hinting based on my original patch.
> Since then the patch has been revised to address the major concerns
> that were identified (breakage
+1 for HEAD and 5.3
On Tue, Jul 7, 2009 at 1:55 PM, Gwynne Raskind wrote:
> On Jul 7, 2009, at 1:17 PM, Andrei Zmievski wrote:
I would like to ask all developers to voice their opinions of whether it
makes sense to add this to 5.3 or to throw it away (either one is fine
btw).
On Jul 7, 2009, at 1:17 PM, Andrei Zmievski wrote:
I would like to ask all developers to voice their opinions of
whether it makes sense to add this to 5.3 or to throw it away
(either one is fine btw). To keep the process simple & flamewar
free, please restrict yourself to +/- (1/0), next wee
-1 for 5.3.x . We should not add major language features at that stage.
On 2009-07-07, Ilia Alshanetsky wrote:
> Last week or so there was a fairly detailed discussion on the
> internals list regarding type hinting based on my original patch.
> Since then the patch has been revised to address
Ilia Alshanetsky wrote:
PHP 6 is too far off in a practical sense (sorry Andrei) from the time
where I can see myself using it in production or other people benefiting
from this function. The (simpler) variant of provided patch is what is
currently being used on production, if it can go into 5.
Paul Biggar wrote:
> On Tue, Jul 7, 2009 at 6:41 PM, Lukas Kahwe Smith wrote:
>> B) foo($bar);
>> function bar((int) $bar) {}
>>
>> What am I really saying with B)?
>> I don't care what you give me, I am going to use it as an int anyways?
>
> Exactly. Very simple. I would phrase it as "I'll accept
The big issue I saw was that fgetcsv() used PHP_EOL for determining
line endings, but fputcsv() didn't, which on Windows was causing csv
files written by PHP not be able to be read back ( assuming
auto_detect_line_endings is turned off ).
John Mertic
jmer...@gmail.com | http://jmertic.wordpress.co
+1
-- Marcelo Araujo
Hi,
So there is some information about the project in the CVS repository.
Let me first say that the project is not mature enough to run your favorite
app. It is capable of executing some small tests, but not complex apps.
You can use either clang or llvm-gcc to compile the stuff, although the la
+1
2009/7/7 Ryan Panning
> Ilia Alshanetsky wrote:
>
>> Last week or so there was a fairly detailed discussion on the internals
>> list regarding type hinting based on my original patch. Since then the patch
>> has been revised to address the major concerns that were identified
>> (breakage of b
On 7/7/09 1:27 PM, Jani Taskinen wrote:
John Mertic kirjoitti:
Hi All,
Bringing this one back once more; let me know what everyone thinks
about it. If it's safe to commit than if someone could ( or give me
the karma to do so ) that would be great. If not, let me know what
should be done about i
Ilia Alshanetsky wrote:
Last week or so there was a fairly detailed discussion on the internals
list regarding type hinting based on my original patch. Since then the
patch has been revised to address the major concerns that were
identified (breakage of binary compatibility) as well extended wi
On 7-Jul-09, at 1:35 PM, Jeff Griffiths wrote:
On 07/07/09 10:17 AM, Andrei Zmievski wrote:
Andrei Zmievski wrote:
I would like to ask all developers to voice their opinions of
whether
it makes sense to add this to 5.3 or to throw it away (either one
is
fine btw). To keep the process simp
Ilia Alshanetsky wrote:
> Last week or so there was a fairly detailed discussion on the internals
> list regarding type hinting based on my original patch. Since then the
> patch has been revised to address the major concerns that were
> identified (breakage of binary compatibility) as well extende
John Mertic kirjoitti:
Hi All,
Bringing this one back once more; let me know what everyone thinks
about it. If it's safe to commit than if someone could ( or give me
the karma to do so ) that would be great. If not, let me know what
should be done about it instead.
Is \r\n okay on Mac? Is \r o
On 07.07.2009, at 20:04, Paul Biggar wrote:
Of course I am also quite opposed to sticking this into 5.3.
On which grounds? If you don't like the feature, please cast a -1
That adding language syntax sugar anything but a major or minor
release is a bad idea.
And this even if Ilia does mana
On Tue, Jul 7, 2009 at 6:41 PM, Lukas Kahwe Smith wrote:
> B) foo($bar);
> function bar((int) $bar) {}
>
> What am I really saying with B)?
> I don't care what you give me, I am going to use it as an int anyways?
Exactly. Very simple. I would phrase it as "I'll accept anything and
cast it to an in
The bug system today works fine but improvements are being made. I've
gone through the lists and details from past attempts and will list
ideas here. Please do not vote, but if a particular item appears like
a bad idea then please explain. Or, discuss additional (or modified)
ideas that w
Hi All,
Bringing this one back once more; let me know what everyone thinks
about it. If it's safe to commit than if someone could ( or give me
the karma to do so ) that would be great. If not, let me know what
should be done about it instead.
Thanks!
John Mertic
jmer...@gmail.com | http://jmerti
Hi,
I am -1 on the inclusion of cast support. IMHO this part isnt thought
out and was just thrown in to silence those who feel that there is a
use case for non strict type hinting. But in that case I might as well
leave the type cast in the API calling code. The number of characters
saved
On 07/07/09 10:17 AM, Andrei Zmievski wrote:
Andrei Zmievski wrote:
I would like to ask all developers to voice their opinions of whether
it makes sense to add this to 5.3 or to throw it away (either one is
fine btw). To keep the process simple & flamewar free, please
restrict yourself to +/- (1
Andrei Zmievski wrote:
I would like to ask all developers to voice their opinions of whether
it makes sense to add this to 5.3 or to throw it away (either one is
fine btw). To keep the process simple & flamewar free, please restrict
yourself to +/- (1/0), next week monday I'll run a tally of th
Ilia Alshanetsky wrote:
Last week or so there was a fairly detailed discussion on the internals
list regarding type hinting based on my original patch. Since then the
patch has been revised to address the major concerns that were
identified (breakage of binary compatibility) as well extended wi
I would like to take care of http://bugs.php.net/bug.php?id=48695.
I guess, David Soria Parra(dsp) and Pierre Joye has said ok to my request.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On 07/07/09 10:18, Brian A. Seklecki wrote:
If it did use libcurl, dozens of problems over the last few years would
have magically solved themselves (pipe-line'ing, keep-alive, socket
options, PKI, etc.)
Not only this extension but pretty much everything should use curl IMHO,
it is included i
On Tue, Jul 7, 2009 at 3:53 PM, Greg Beaver wrote:
> 2) have 1 syntax, T_*_CAST as in function ((int) $a) {} and have that
> mean strict type hinting.
I dont think this is a good option. Having features dictated by trying
to keep the lexer/parser clean is a bad idea. If the lexer cannot be
fixed,
Greg,
the T_CLASS fix you've suggested in your e-mail to me could work, but
calling a type hint "class" rather then "object" seems a little
awkward to me. Plus to your point and earlier Stas' e-mail the patch
would reserve the a whole bunch of type based keywords, personally I
feel that t
that vote is for anything coming after 5.3.x (be 5.4 or 6.x), did not
see the 5.3 only requirement (which makes no sense).
I'm generally -1 on any major change for 5.3.x.
On Tue, Jul 7, 2009 at 11:42 AM, Pierre Joye wrote:
> +1
>
>
>
>
> --
> Pierre
>
> http://blog.thepimp.net | http://www.libgd.
Sebastian Bergmann schrieb:
> +1
Just to be clear, my vote was for putting this into (PHP_5_3) + 1, not
into PHP 5.3.1.
--
Sebastian BergmannCo-Founder and Principal Consultant
http://sebastian-bergmann.de/ http://thePHP.cc/
--
PHP Internals - P
On 07.07.2009, at 16:15, Stan Vassilev wrote:
+1 if the object type hint is change to use T_CLASS so we don't break
every external package using "Object" as a base class.
http://www.google.com/codesearch?as_q=class\s%2Bobject&btnG=Search
+
Code
&hl
=
en
&as_lang
=
php
&as_license_rest
Christian Schneider wrote:
> Stan Vassilev wrote:
>>> +1 if the object type hint is change to use T_CLASS so we don't break
>>> every external package using "Object" as a base class.
>>> http://www.google.com/codesearch?as_q=class\s%2Bobject&btnG=Search+Code&hl=en&as_lang=php&as_license_restrict=i&
On Tue, Jul 7, 2009 at 3:15 PM, Stan Vassilev wrote:
> I'm really puzzled why a non-essential, and for the past months (years?)
> controversial and always rejected feature such as strict type hints, has
> everyone turning 180 degrees and putting it in a minor release in the course
> of a week.
Bec
+1
On Jul 6, 2009, at 7:52 PM, Ilia Alshanetsky wrote:
Last week or so there was a fairly detailed discussion on the
internals list regarding type hinting based on my original patch.
Since then the patch has been revised to address the major concerns
that were identified (breakage of binar
I would like to ask all developers to voice their opinions of
whether it makes sense to add this to 5.3 or to throw it away
(either one is fine btw). To keep the process simple & flamewar
free, please restrict yourself to +/- (1/0), next week monday I'll
run a tally of the votes and based
Stan Vassilev wrote:
>> +1 if the object type hint is change to use T_CLASS so we don't break
>> every external package using "Object" as a base class.
>> http://www.google.com/codesearch?as_q=class\s%2Bobject&btnG=Search+Code&hl=en&as_lang=php&as_license_restrict=i&as_license=&as_package=&as_filen
-1 for 5.x
+1 for 6.0
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
I would like to ask all developers to voice their opinions of
whether it makes sense to add this to 5.3 or to throw it away
(either one is fine btw).
I don't want to start a long discussion, but IMO this and other major
language changes doen't belong in a point release of 5.3.x (whether
i
Stan Vassilev wrote:
>> +1 if the object type hint is change to use T_CLASS so we don't break
>> every external package using "Object" as a base class.
>>
>> http://www.google.com/codesearch?as_q=class\s%2Bobject&btnG=Search+Code&hl=en&as_lang=php&as_license_restrict=i&as_license=&as_package=&as_fi
On Tue, 2009-07-07 at 15:42 +0200, endrazine wrote:
>
> It is lacking any type of authentication of the payment gateway, which
> is not acceptable.
>
I agree+++.
The problem is that PHP SOAP uses an internal "streams" library instead
of libcurl; the former lacks, the later has, client/server
2009/7/7 Ilia Alshanetsky :
> Last week or so there was a fairly detailed discussion on the internals list
> regarding type hinting based on my original patch. Since then the patch has
> been revised to address the major concerns that were identified (breakage of
> binary compatibility) as well ext
+1 if the object type hint is change to use T_CLASS so we don't break
every external package using "Object" as a base class.
http://www.google.com/codesearch?as_q=class\s%2Bobject&btnG=Search+Code&hl=en&as_lang=php&as_license_restrict=i&as_license=&as_package=&as_filename=&as_case=
Greg
Or thi
Ilia Alshanetsky wrote:
Last week or so there was a fairly detailed discussion on the internals
list regarding type hinting based on my original patch. Since then the
patch has been revised to address the major concerns that were
identified (breakage of binary compatibility) as well extended wi
Ilia Alshanetsky wrote:
[..]
I would like to ask all developers to voice their opinions of whether it
makes sense to add this to 5.3 or to throw it away (either one is fine
btw).
+1
[..]
- Mark
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.n
Greg Beaver wrote:
>> I would like to ask all developers to voice their opinions of whether it
>> makes sense to add this to 5.3 or to throw it away (either one is fine
>> btw). To keep the process simple & flamewar free, please restrict
>> yourself to +/- (1/0), next week monday I'll run a tally o
+1 from me
On Tue, Jul 7, 2009 at 1:52 AM, Ilia Alshanetsky wrote:
> Last week or so there was a fairly detailed discussion on the internals
> list regarding type hinting based on my original patch. Since then the patch
> has been revised to address the major concerns that were identified
> (bre
Ilia Alshanetsky wrote:
> Last week or so there was a fairly detailed discussion on the internals
> list regarding type hinting based on my original patch. Since then the
> patch has been revised to address the major concerns that were
> identified (breakage of binary compatibility) as well extende
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello dear list,
I realise this is probably not the best place to ask this kind of
questions, but after doing my howmeworks on google and php.net, I can't
find a decent solution to a development problem I thought would be
common. If this is strictly o
+1
Rafael Dohms
On Tue, Jul 7, 2009 at 9:44 AM, Richard Quadling
wrote:
> 2009/7/7 Ilia Alshanetsky :
> > Last week or so there was a fairly detailed discussion on the internals
> list
> > regarding type hinting based on my original patch. Since then the patch
> has
> > been revised to address t
2009/7/7 Ilia Alshanetsky :
> Last week or so there was a fairly detailed discussion on the internals list
> regarding type hinting based on my original patch. Since then the patch has
> been revised to address the major concerns that were identified (breakage of
> binary compatibility) as well ext
On 06/07/09 20:52, Ilia Alshanetsky wrote:
The final patch is available here: http://ilia.ws/patch/type_hint_53_v2.txt
The test suit is available here: http://ia.gd/patch/type_hint_tests.tar.bz2
+1
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.n
On 07.07.2009 13:55, Thomas Koch wrote:
> Hi,
>
> are there people who're interested to host semi-official
> GIT-/HG-/BZR-mirrors?
> Doing an initial GIT-SVN sync causes quite a lot of traffic on the subversion
> server and if a douzens people set up there mirrors in the next week, this
> traf
+1
--
Slan,
David
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
+1
Patrick Allaert
---
http://code.google.com/p/peclapm/ - Alternative PHP Monitor
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On 2009-07-07, Thomas Koch wrote:
> Hi,
>
> are there people who're interested to host semi-official
> GIT-/HG-/BZR-mirrors?
> Doing an initial GIT-SVN sync causes quite a lot of traffic on the subversion
> server and if a douzens people set up there mirrors in the next week, this
> traffic is
Hi,
are there people who're interested to host semi-official GIT-/HG-/BZR-mirrors?
Doing an initial GIT-SVN sync causes quite a lot of traffic on the subversion
server and if a douzens people set up there mirrors in the next week, this
traffic is multiplied.
If nobody else will, then I'll surel
On Thu, Jul 2, 2009 at 01:01, Brian A.
Seklecki wrote:
> All:
>
> Perhaps we should clarify the socket tuneables such as:
>
> ; Default timeout for socket based streams (seconds)
> default_socket_timeout = 60
>
> These are slightly ambiguous. e.g., we should clarify connect()
> timeouts v.s. "id
+1
--
Pierre
http://blog.thepimp.net | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Tue, Jul 7, 2009 at 02:52, Ilia Alshanetsky wrote:
> The final patch is available here: http://ilia.ws/patch/type_hint_53_v2.txt
> The test suit is available here: http://ia.gd/patch/type_hint_tests.tar.bz2
+1
-Hannes
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, vi
Ilia Alshanetsky wrote:
> I would like to ask all developers to voice their opinions of whether it
> makes sense to add this to 5.3 or to throw it away (either one is fine
> btw). To keep the process simple & flamewar free, please restrict
> yourself to +/- (1/0), next week monday I'll run a tally
+1
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
+1
Hi all
The time has come that we move to SVN and the switch flipping will be
happening next Friday (July 10th, 2009)!
There will be a total cvs.php.net lockdown as of late Thursday, with
svn.php.net replacing it !
The fire department (which needs more volunteers!) will be working
through the wee
On Mon, 6 Jul 2009, Ilia Alshanetsky wrote:
> Last week or so there was a fairly detailed discussion on the internals list
> regarding type hinting based on my original patch. Since then the patch has
> been revised to address the major concerns that were identified (breakage of
> binary compatibi
79 matches
Mail list logo
