1 Jan 2012 04:49
1 Jan 2012 05:19
Re: [PHP-DEV] PHP Wiki Down?
Florian Anderiasch <ml <at> anderiasch.de>
2012-01-01 04:19:14 GMT
2012-01-01 04:19:14 GMT
On 01.01.2012 04:49, Clint M Priest wrote: > Looks like wiki.php.net is down... I'm getting an nginx gateway timeout. Works for me, now. Related: Did the monitoring url change or is it still down? Are there any efforts to bring munin back? Unrelatedly, happy new year :) Florian -- -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
2 Jan 2012 11:21
Re: [PHP-DEV] PHP Wiki Down?
Martin Jansen <martin <at> divbyzero.net>
2012-01-02 10:21:54 GMT
2012-01-02 10:21:54 GMT
On 01.01.12 05:19, Florian Anderiasch wrote: > Did the monitoring url change or is it still down? > Are there any efforts to bring munin back? The move to a new machine is underway but go stalled by recent downtimes of another important server. Here's hoping to get it done by the end of the week. - Martin -- -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
2 Jan 2012 12:44
Re: [PHP-DEV] commit rights for ext/pdo folder
Matteo Beccati <php <at> beccati.com>
2012-01-02 11:44:50 GMT
2012-01-02 11:44:50 GMT
On 31/12/2011 11:56, marius adrian popa wrote: > There are some tests that needs to be skiped for firebird driver > > I have made the changes in test but i can't commit them I've committed the fix, although someone else will need to jump in and grant you karma ;) Happy holidays! Cheers -- Matteo Beccati Development & Consulting - http://www.beccati.com/ -- -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
2 Jan 2012 21:10
Re: [PHP-DEV] Quick missing NEWS entry questions
Stas Malyshev <smalyshev <at> sugarcrm.com>
2012-01-02 20:10:43 GMT
2012-01-02 20:10:43 GMT
Hi! > My question is, should I go back and edit NEWS to put my change in? It > would go under "PHP 5.4.0 Alpha 1" Generally, each substantial change should be in the NEWS under the version in which it appeared (for 5.4, all pre-release versions will be consolidated on release). > And if I do put it in, do I put it in both trunk and branches/PHP_5_4 ? No, only 5.4 as it's the first version it appeared in (in trunk, it's not NEWS anymore). > Also, everyone is using first names only in NEWS but Andrew is not unique > in the file, should I use my full name, full, first name + initial? I'd advise the full name. First name only is usually used by people who are frequent committers so it is known who exactly that is. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227 -- -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
2 Jan 2012 22:33
[PHP-DEV] stream_get_meta_data is missing filters
<mtdowling <at> gmail.com>
2012-01-02 21:33:12 GMT
2012-01-02 21:33:12 GMT
The docs state that the return value of the stream_get_meta_data function
will contain a 'filters' key which contains an array of filters registered
on a stream. I noticed that the 'filters' array wasn't being returned, so I
took a look at the source. It looks like this is a known issue because
the 'filters' code is commented out (in 5.3 trunk and 5.4):
#if 0 /* TODO: needs updating for new filter API */
if (stream->filterhead) {
php_stream_filter *filter;
MAKE_STD_ZVAL(newval);
array_init(newval);
for (filter = stream->filterhead; filter != NULL; filter = filter->next) {
add_next_index_string(newval, (char *)filter->fops->label, 1);
}
add_assoc_zval(return_value, "filters", newval);
}
#endif
Does anyone know the status on updating this method for the new filter API?
I don't see an open bug report, so I'd be happy to open one if needed.
Thanks,
Michael
3 Jan 2012 06:59
[PHP-DEV] SessionHandler class return values
Drak <drak <at> zikula.org>
2012-01-03 05:59:47 GMT
2012-01-03 05:59:47 GMT
I think something is wrong with the SessionHandler class and I dont know if it requires a bug report. According to the documentation at http://www.php.net/manual/en/class.sessionhandler.php the various methods return 0 for success and 1 for failure which is kind of backwards since 0 would normally be evaluated as false and 1 as true. This is in direct contradiction with the current expected behaviour of session_set_save_handler() http://www.php.net/manual/en/function.session-set-save-handler.php which expects true or false return values except for the read handler which should always return a string. What's the deal here? I think the return values really should be true and false for this class, as expected by session_set_save_handler() Regards, Drak
3 Jan 2012 15:02
[PHP-DEV] Re: Return Type Hinting for Methods RFC
Will Fitch <will.fitch <at> gmail.com>
2012-01-03 14:02:05 GMT
2012-01-03 14:02:05 GMT
On Monday, January 2, 2012, JS wrote:
> I think the proposed syntax will create a lot of code readability issues.
> Have you considered an alternate syntax:
>
What readability issues? The proposed syntax matches that of C# and Java.
The idea is to use a syntax already familiar to most developers.
>
> public function ($a, $b) returns nullable ClassName {
>
> }
> Or any other variation that puts the return type after the function name
> /paramter list. Some advantages:
>
> 1) The function keyword is dealt with gracefully
>
The function keyword is already being discussed as being removed for
methods. See https://wiki.php.net/rfc/optional-t-function
>
> 2) I imagine it would be easier for the parser
>
Your proposed alternative would create an additional token "returns" and
add the additional step to check *after* the method/function has been
declared. The syntax in the RFC just replaces an existing token, making
(Continue reading)
3 Jan 2012 18:03
Re: [PHP-DEV] Return Type Hinting for Methods RFC
Matthew Weier O'Phinney <weierophinney <at> php.net>
2012-01-03 17:03:59 GMT
2012-01-03 17:03:59 GMT
On 2011-12-22, Rasmus Lerdorf <rasmus <at> lerdorf.com> wrote:
> On 12/22/2011 10:51 AM, Sebastian Bergmann wrote:
> > Am 22.12.2011 19:41, schrieb Rasmus Lerdorf:
> > > This is not a step forward. If the author of age_check() really
> > > doesn't want to accept type-juggled arguments, then it is easy
> > > enough to do a strict type check in the function itself. This puts
> > > the effort in the correct place and doesn't encourage this type of
> > > coding.
> >
> > Putting such code into the "correct" place does not change the
> > problem that you and Stas describe
> >
> > function age_check($age)
> > {
> > if (!is_int($age)) {
> > throw new InvalidArgumentException;
> > }
> > }
> >
> > With the above code, the caller needs to cast and the writer of the
> > age_check() function has to copy/paste/adapt these checks to all
> > the correct places ...
> >
> > I am not advocating type hints for scalars, I am just saying that
> > this argument is not really a good one against it.
>
> But people don't really write code like this in PHP.
Um, I do. Often.
(Continue reading)
3 Jan 2012 18:17
[PHP-DEV] Re: Status update: Git Migration
Matthew Weier O'Phinney <weierophinney <at> php.net>
2012-01-03 17:17:33 GMT
2012-01-03 17:17:33 GMT
On 2011-12-29, David Soria Parra <dsp <at> php.net> wrote: > here is a short update on the current status of the > git migration. Thanks for all the ground work you're doing making this happen! > - php-src will be migrated after PHP 5.4 final > Stas wants to have PHP 5.4 final out before we migrate > the repository to not have problems with the release. > Expect the php-src migration in 14-21 days after 5.4 final. > > - http://git.php.net is up and running > We setup the server. Thanks to gwynne, derick, conf, mgdm, druid > helping me with that. > > - old git mirrors are down > the old server was shut down. mirrors have not been setup so far. > > - systems/ and web/ are going to be migrated in the next days > systems is already migrated and commits to the systems/ directory > in SVN is disabled. We are slowly migrating the cronjobs on the boxes. > web will follow right after systems is done. > > - playground > Feel free to play around with the playground.git repository at > http://git.php.net. Please note that the push url is different > from the unathorized pull url. THis will be fixed soon (hopefully). > Everyone with an SVN account should be able to push to that > repository. >(Continue reading)
RSS Feed