.
This is such a major BC break.
One thing we must do before even considering non required names is to
actually check every major apps, frameworks or libraries. If we can
avoid a date/datetime clash again, that would be awesome ;)
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime
events look better. And expect an open letter soon.
Cheers,
Pierre
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Thu, Feb 19, 2015 at 7:16 AM, Dmitry Stogov dmi...@zend.com wrote:
On Thu, Feb 19, 2015 at 6:00 PM, Pierre Joye pierre@gmail.com wrote:
On Thu, Feb 19, 2015 at 1:09 AM, Joe Watkins pthre...@pthreads.org
wrote:
Morning internals,
The expectations RFC is now in voting phase
On Thu, Feb 19, 2015 at 7:11 AM, Arvids Godjuks
arvids.godj...@gmail.com wrote:
I think this starts to go the route of putting things into absolute. Ideal
things tend not to happen/work in the real world to the letter.
Some things just don't work out by themselves. The Type Hinting RFC's are
On Thu, Feb 19, 2015 at 7:21 AM, Zeev Suraski z...@zend.com wrote:
-Original Message-
From: Pierre Joye [mailto:pierre@gmail.com]
Sent: Thursday, February 19, 2015 4:52 PM
To: Zeev Suraski
Cc: PHP internals
Subject: Re: [PHP-DEV] Using Other Channels (was Scalar Type Declarations
for anything PHP uses, every library, every extension or services
(http or other).
Cheers,
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Thu, Feb 19, 2015 at 6:13 PM, François Laupretre franc...@php.net wrote:
De : Pádraic Brady [mailto:padraic.br...@gmail.com]
As I understand it, Andrea left her RFC free to be reused, reopened
and derived without any specific limitation. It would therefore appear
that it would be possible
,
Thanks you :)
I like it. It is simple and straightforward.
I agree with other that it is easily done using a simple function
(Adam's) but I do not like it much, less clear.
Cheers,
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe
of
PHP, this discussion has nothing to do with that. DB drivers will do
what they have to do to deal with PHP DB types, as they always do.
It would be very good if you could focus on the actual content of a
RFC or discussion instead.
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP
On Thu, Feb 19, 2015 at 7:45 AM, Pierre Joye pierre@gmail.com wrote:
On Thu, Feb 19, 2015 at 7:16 AM, Dmitry Stogov dmi...@zend.com wrote:
On Thu, Feb 19, 2015 at 6:00 PM, Pierre Joye pierre@gmail.com wrote:
On Thu, Feb 19, 2015 at 1:09 AM, Joe Watkins pthre...@pthreads.org
wrote
On Thu, Feb 19, 2015 at 6:33 AM, Zeev Suraski z...@zend.com wrote:
-Original Message-
From: Pierre Joye [mailto:pierre@gmail.com]
Sent: Thursday, February 19, 2015 4:09 PM
To: Zeev Suraski
Cc: Anthony Ferrara; PHP internals
Subject: Re: [PHP-DEV] Using Other Channels (was Scalar
the
concept, this RFC does not have, by far, the quality I would expect
for a RFC being voted on.
Cheers,
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Thu, Feb 19, 2015 at 9:13 AM, Leigh lei...@gmail.com wrote:
On 19 February 2015 at 15:45, Pierre Joye pierre@gmail.com wrote:
Still, no announce for a discussion about this specific RFC. And
really, the content of the RFC is almost empty, pointing to the ML
archive is really
as implementation details), but generally it is the
compromises and way I see as the way to go.
Cheers,
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Tue, Feb 17, 2015 at 7:02 AM, Dennis Birkholz den...@birkholz.biz wrote:
Am 17.02.2015 um 12:30 schrieb Leigh:
And you find taking authority over a library away from the library
author completely acceptable?
If I write an API that works perfectly well in strict mode, why
shouldn't I be
of
the debate, we can focus on the actual specs and implementations. :)
Cheers,
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
of such votes.
My no vote is based on looking at the implementation, the size of the
patch and the destabilizing changes to the extension API weighed against
its benefits.
Too bad.
Cheers,
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
thing. Having bigint support in the engine makes sense regardless of
gmp. Other languages have it and are very happy with that. It is
simply way easier and cleaner to use than relying on an ext (while
Nikita's patch for operators overloading for exts makes things
better).
Cheers,
--
Pierre
where we are
now. Stronger than ever.
Cheers,
Pierre
regarding weak vs. strict vs. both should
know there's no performance impact to be expected from any choice we make.
And it is not about performance, never was and should never be.
Cheers,
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
Could you revive it in a new thread please? :)
On Feb 13, 2015 3:25 PM, Nikita Popov nikita@gmail.com wrote:
On Mon, Oct 6, 2014 at 11:53 PM, Nikita Popov nikita@gmail.com
wrote:
Hi internals!
During the PHP 5.6 development cycle I have proposed an RFC [1] that
suggested the
defining properties.
[0] https://wiki.php.net/rfc/remove_php4_constructors
Regards
Pierre du Plessis
followed by a removal, read: Vote for
deprecation means removal in next. But if it is not the case and we
keep deprecated features forever, then we may just kill the
deprecation flag instead.
Cheers,
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development
, for such huge thing.
Cheers,
Pierre
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
a php problem.
Cheers,
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Feb 10, 2015 12:03 AM, Zeev Suraski z...@zend.com wrote:
-Original Message-
From: Andrea Faulds [mailto:a...@ajf.me]
Sent: Monday, February 09, 2015 12:44 PM
To: Zeev Suraski
Cc: Jordi Boggiano; internals@lists.php.net
Subject: Re: [PHP-DEV] [VOTE] Scalar Type Hints
Hi,
with json.
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
a single declare with the type hint level I want? What will happen
if a library is written for weak type hints ends up in strict type hint
mode? Or the other way around? Isn't it gonna be a mess?
How do you do it for namespaces? This is the same issue.
Cheers,
--
Pierre
@pierrejoye | http
of raising the performance impact
blocker :)
Cheers,
Pierre
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
code can be
strict free if you wish to, or it will be by default. Only issue is
the massive misunderstanding behind the declare(strict) thing.
Cheers,
Pierre
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Mon, Feb 9, 2015 at 3:30 PM, Pavel Kouřil pajou...@gmail.com wrote:
On Mon, Feb 9, 2015 at 9:22 AM, Pierre Joye pierre@gmail.com wrote:
I am not saying I want one or the other (I have voted and now only
focus on solving possible tech issues we may find) but trying to be
fair
On Feb 9, 2015 4:46 PM, Jakub Zelenka bu...@php.net wrote:
On Mon, Feb 9, 2015 at 9:18 AM, Anatol Belski anatol@belski.net
wrote:
Hi,
On Mon, February 9, 2015 07:33, Xinchen Hui wrote:
Hey:
On Mon, Feb 9, 2015 at 1:44 PM, Pierre Joye pierre@gmail.com
wrote:
On Mon
On Feb 9, 2015 6:07 PM, François Laupretre franc...@tekwire.net wrote:
De : Pierre Joye [mailto:pierre@gmail.com]
However, DbC is coming close!
DbC brings much more flexibility, strict/loose constraints,
performance,
security, better documentation and more.
DbC suitable
On Feb 9, 2015 8:52 PM, Sebastian Bergmann sebast...@php.net wrote:
Am 07.02.2015 um 02:08 schrieb Sebastian Bergmann:
After reading your email, Nikita, I deleted my vote (it was no before).
I will review the RFC again, with your arguments (and others) in mind
and maybe I'll come to a
On Feb 10, 2015 1:22 AM, Lars Strojny l...@strojny.net wrote:
Hi Matteo,
sorry for the late response.
On 07 Feb 2015, at 12:46, Matteo Beccati p...@beccati.com wrote:
Maybe it's just me, but I didn't quite understand the point you are
making here. Are you saying that declares are more
On Feb 8, 2015 10:44 PM, Tom Worster f...@thefsb.org wrote:
Hi Yasuo, Pierre,
Thank you both for the updates.
I expect the vote to remove mcrypt can be shifted towards yes if some
campaigning effort is made. I made a start in another thread.
Assuming that mcrypt goes, as it should, we
? Or is there something I'm missing that connects ticks and
encoding, but excludes strict_types?
Both are being done at compile time and modify how a file is compiled.
So no, I do not agree with runtime here, while one directive is
being used at runtime.
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP
like encoding. We may fix as well other
related issues, nothing that does not look fixable.
Cheers,
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Mon, Feb 9, 2015 at 11:10 AM, Xinchen Hui larue...@php.net wrote:
Hey:
On Mon, Feb 9, 2015 at 10:40 AM, Pierre Joye pierre@gmail.com wrote:
hi,
Should we push json_parser.tab.c? Which is generated (re2c), just like
what is done in date or other?
I think we should, and also use
hi,
Should we push json_parser.tab.c? Which is generated (re2c), just like
what is done in date or other?
Cheers,
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
(scalar hinting).
Then we have annotations, which can be used(and is very often used for
contracts) by DbC.
However starting to stop one in favor of another is a strategic mistake.
I left alone the DbC or annotations as phpdoc as we have discussed that to
death already :)
Cheers,
Pierre
of
it, vote no. But this constant attempt to get exactly what you want
and do almost everything possible to get it is getting very counter
productive. Not the first time but hopefully the last.
Cheers,
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development
On Mon, Feb 9, 2015 at 7:47 AM, Andrey Andreev n...@devilix.net wrote:
Hi,
On Mon, Feb 9, 2015 at 2:10 AM, Pierre Joye pierre@gmail.com wrote:
There is a vote, you do not like the RFC or part of
it, vote no. But this constant attempt to get exactly what you want
and do almost everything
On Mon, Feb 9, 2015 at 2:48 PM, Jan Ehrhardt php...@ehrhardt.nl wrote:
Pierre Joye in php.internals (Mon, 9 Feb 2015 09:40:21 +0700):
Should we push json_parser.tab.c? Which is generated (re2c), just like
what is done in date or other?
Yes, you should. I ran into this problem when I tried
On Mon, Feb 9, 2015 at 3:33 AM, Zeev Suraski z...@zend.com wrote:
FWIW, while I think strict types - stricter than even strict languages -
don't belong in PHP, this syntax is clearly a step up from declare(), which
was definitely not intended for this purpose.
I think we get it, you do not
On Feb 7, 2015 5:57 PM, François Laupretre franc...@tekwire.net wrote:
De : Pierre Joye [mailto:pierre@gmail.com]
Not sure it will help. It is really about showing cases for deref,
duplicate, convert, iterate, etc. The zpp, return values or
functions/class/methods declaration
On Feb 7, 2015 5:01 PM, Tony Marston tonymars...@hotmail.com wrote:
Stelian Mocanita wrote in message
news:CAMc0WS6+1Y-5yJW2s=mw+yns6tn8m5ieaxe10mwnlrl0_dz...@mail.gmail.com...
On Fri, Feb 6, 2015 at 12:57 AM, Andi Gutmans a...@zend.com wrote:
The folks who really want all this great
On Feb 7, 2015 6:46 PM, Matteo Beccati p...@beccati.com wrote:
Hi Lars,
On 07/02/2015 04:36, Lars Strojny wrote:
My main concern is that the declare statement is
basically a better behaviour changing ini setting and PHPs history is
paved with those. I very much hope for scalar type
On Feb 8, 2015 12:48 PM, Yasuo Ohgaki yohg...@ohgaki.net wrote:
2. What's going to happen to mcrypt?
I see the vote to excise it did not pass. Does this mean that (i.e.
imply that) PHP's plan is to keep a security lib that hasn't been
maintained for 8 years for the next 5+ years?
Removed.
On Sun, Feb 8, 2015 at 1:43 PM, Yasuo Ohgaki yohg...@ohgaki.net wrote:
Hi Pierre,
On Sun, Feb 8, 2015 at 3:04 PM, Pierre Joye pierre@gmail.com wrote:
On Feb 8, 2015 12:48 PM, Yasuo Ohgaki yohg...@ohgaki.net wrote:
2. What's going to happen to mcrypt?
I see the vote to excise it did
On Feb 8, 2015 10:52 AM, Rasmus Lerdorf ras...@lerdorf.com wrote:
On 02/07/2015 09:51 PM, Andrea Faulds wrote:
tan(1);
echo strstr(test, est, 1);
Banning int-float and float-int is both a pain point and sometimes a
life-saver. It’s annoying that tan(1) doesn’t work. On the other hand,
On Sun, Feb 8, 2015 at 11:33 AM, Pierre Joye pierre@gmail.com wrote:
Yes, the RFC is somewhat inaccurate in that respect. It is per-file in
one sense (like encoding, but unlike ticks, it has no effect on the
including or included files). However, it technically affects the remainder
and
maintain them in parallel until you have no PHP 5 customer anymore.. What do
you think you'll do (or won't do) ?
@Pierre,@Dmitry : you have a better vision than mine on the migration
process. What's your opinion on forcing software developers to maintain two
separate branches ?
From
I'll start the voting phase on *Wednesday (February 11, 2015)* if no new
points that could lead to changes on the RFC arise. So be sure to share
your opinion or suggestion, before that period, if you feel it's necessary.
Please create a new thread to be sure everyone sees it.
--
Pierre
.
Doing so has the big advantage of being self contained and anyone can
contribute easily. It is also easier for someone to actually play with it
than with a diff.
I was thinking about that for a workshop I have to give in April.
Cheers
Pierre
On Sat, Feb 7, 2015 at 9:57 AM, François Laupretre franc...@tekwire.net wrote:
De : Pierre Joye [mailto:pierre@gmail.com]
What do you think about the creation of an example extension covering
almost everything one would do in an extension?
The class, methods or functions do not have
On Fri, Feb 6, 2015 at 10:33 AM, Yasuo Ohgaki yohg...@ohgaki.net wrote:
Hi Pierre,
On Fri, Feb 6, 2015 at 11:13 AM, Pierre Joye pierre@gmail.com wrote:
I am :) Almost all of my clients are ISMS or similar certified.
Marketing ;)
However, back to this exact feature. I am
On Thu, Feb 5, 2015 at 11:44 PM, Dmitry Stogov dmi...@zend.com wrote:
This is just a brainstorming, and we are not going to provide a working
solution tomorrow :)
You have enough time :)
I don't like phpdoc approach because we have to define, parse and compile
new syntax for constraints.
/hack.attributes.php
Exactly, phpdoc is used as annotation (or comments with some similar
syntax) but is definitively not aimed to be annotations.
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net
On Fri, Feb 6, 2015 at 11:14 AM, guilhermebla...@gmail.com
guilhermebla...@gmail.com wrote:
Hi Pierre,
Sorry, but you don't. Proposing a simple syntax is the same as not proposing
it.
We can do whatever syntax is proposed, but we need to discuss on how to
handle inheritance, overriding, etc
On Fri, Feb 6, 2015 at 11:35 AM, Yasuo Ohgaki yohg...@ohgaki.net wrote:
Hi Pierre,
On Fri, Feb 6, 2015 at 1:16 PM, Pierre Joye pierre@gmail.com wrote:
With SElinux, we can restrict access. However, PHP should be able to
read/write
uploaded files. PHP just read and execute them
Annotations in
sync with current internals.
We are, with the simplified syntax we discussed last time (have to dig
the archive)
Cheers,
On Thu, Feb 5, 2015 at 11:00 PM, Pierre Joye pierre@gmail.com wrote:
On Thu, Feb 5, 2015 at 11:36 PM, Dmitry Stogov dmi...@zend.com wrote:
phpdoc
On Fri, Feb 6, 2015 at 11:08 AM, Yasuo Ohgaki yohg...@ohgaki.net wrote:
On Fri, Feb 6, 2015 at 12:40 PM, Pierre Joye pierre@gmail.com wrote:
Even if uploaded files are stored under non web root dir, attackers can
use
path
traversal or even full path with bad code. As long as PHP
On Thu, Feb 5, 2015 at 5:47 PM, Yasuo Ohgaki yohg...@ohgaki.net wrote:
Hi Pierre and all,
On Thu, Feb 5, 2015 at 7:24 PM, Pierre Joye pierre@gmail.com wrote:
I'm proposing *SCRIPT* only inclusion. This can be done by
- allowing ?php only at to top of script
- not allowing
happened in
PHP for decades.
I understand that argument.
However I feel like the fact that it only affects your app (even if
you use a library relying on strictness) if you want to is not clear
for everyone replying here. Is this point clear for you?
--
Pierre
@pierrejoye | http
On Feb 5, 2015 8:54 PM, François Laupretre franc...@tekwire.net wrote:
De : Dmitry Stogov [mailto:dmi...@zend.com]
Yeah, this may work.
The only problem, that it looks not native and defines additional
language for constraints.
I don't talk it's wrong. Both approaches may make sense, but
On Fri, Feb 6, 2015 at 8:25 AM, Yasuo Ohgaki yohg...@ohgaki.net wrote:
Hi Pierre,
On Thu, Feb 5, 2015 at 8:49 PM, Pierre Joye pierre@gmail.com wrote:
PHP is just as safe than the other languages. PHP applicatons maybe
less, maybe more. I tend to see the amount of attacks as a proof
On Fri, Feb 6, 2015 at 6:22 AM, Andi Gutmans a...@zend.com wrote:
I have to say I’m pretty disappointed at the opening of the vote.
We had a pretty good RFC (thank you) for weak type hinting which was aligned
with the spirit of PHP and everyone was able to rally around it.
This has now been
strongly disagree with this as a security improvement. I see
this more as yet another attempt to replace what should be done at the
OS level.
Cheers,
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net
On Feb 6, 2015 9:08 AM, Yasuo Ohgaki yohg...@ohgaki.net wrote:
Hi Pierre,
On Fri, Feb 6, 2015 at 10:39 AM, Pierre Joye pierre@gmail.com wrote:
I do not put high value in this ISO ;-)
I am :) Almost all of my clients are ISMS or similar certified.
Marketing ;)
However, back
On Feb 5, 2015 3:17 PM, Michael Wallner m...@php.net wrote:
Hi Stas!
On 05/02/15 00:43, Stanislav Malyshev wrote:
Hi!
Points explicitely marked for discussion in the RFC itself:
* pecl/propro
Proxies for properties representing state in internal C structs
questions etc), and
you still all good to keep it around for the next decade? Fine. It is
in voting, so let see the results and move on. I however consider this
as an extremely bad decision. But I do not care enough to battle it to
death. Waste of time to argue about that.
--
Pierre
@pierrejoye
On Feb 5, 2015 7:58 AM, Stanislav Malyshev smalys...@gmail.com wrote:
Hi!
Adding another concept, not changing the existing ones. And really,
it's just simplifying what is already present via is_typename()
runtime checks, making our lives a little bit easier.
There's a very big
On Feb 4, 2015 8:17 PM, Michael Wallner m...@php.net wrote:
On 04/02/15 14:06, Pavel Kouřil wrote:
Hello,
as I mentioned already in the other thread - there are currently no
coding standards related to namespace naming in
https://github.com/php/php-src/blob/master/CODING_STANDARDS and
On Feb 4, 2015 6:15 PM, Andrey Andreev n...@devilix.net wrote:
Hi,
On Wed, Feb 4, 2015 at 1:02 PM, Florian Margaine flor...@margaine.com
wrote:
Hi Leigh,
Le 4 févr. 2015 11:50, Leigh lei...@gmail.com a écrit :
What was wrong with:
function x(int $y, string $z) { // strict
the same with echo
file_get_contents($foo);
The history of php magic security issues tell me one thing, we should
leave that to the OS level and reports error the IO layers return,
when it fails.
Cheers,
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development
reasoning. We know both
libraries are dead. ext/Imap is almost not used anymore by any major
tool relying on imap, Which appealing reasons do you have to force us
to have to maintain them for the next decade?
Cheers,
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime
On Feb 4, 2015 1:51 PM, Stanislav Malyshev smalys...@gmail.com wrote:
Hi!
And at list this one living native PHP implementation
https://github.com/horde/horde/tree/master/framework/Imap_Client/ (and
more library links in the older thread link above).
This is part of Horde with 9 listed
been removed long time ago already.
Cheers,
Pierre
On Feb 3, 2015 2:10 PM, Adam Harvey ahar...@php.net wrote:
On 3 February 2015 at 03:11, Anatol Belski anatol@belski.net wrote:
properly after the voting phase the
https://wiki.php.net/rfc/removal_of_dead_sapis_and_exts moves to the
voting. Each item is voted separately. The voting ends
On Feb 4, 2015 2:51 AM, Yasuo Ohgaki yohg...@ohgaki.net wrote:
I added comments to ext/session/mod_files.c for save handler developers.
Please refer to it also.
Please add them (and maybe example migration code) to UPGRADING.INTERNALS
Thanks!
my fault, did not commit the change :D
It should be fine now.
On Wed, Feb 4, 2015 at 3:21 AM, Jakub Zelenka bu...@php.net wrote:
Hello,
On Mon, Feb 2, 2015 at 9:45 AM, Pierre Joye pierre@gmail.com wrote:
found and added, php-src :)
Thanks for your work!
Thanks for adding
it compile for it.
You won't bother but we should? Wondering why you voted against removing it.
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Feb 3, 2015 4:06 PM, Lester Caine les...@lsces.co.uk wrote:
On 03/02/15 08:44, Matteo Beccati wrote:
Marius Adrian Popa has stated to maintain both, and looks like there
several active users who will use that. So going by that, it's not
being
voted on these exts.
I must have missed
:)
It is not about funny but easiness to find it and what it is all about.
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
found and added, php-src :)
Thanks for your work!
On Mon, Feb 2, 2015 at 4:32 PM, Pierre Joye pierre@gmail.com wrote:
what is your handle?
On Mon, Feb 2, 2015 at 12:23 AM, Jakub Zelenka bu...@php.net wrote:
Hello,
I'd like to request src karma to merge recently accepted jsond to master
things (bug fixes, improvements)
in the ext dir.
If someone could grant it to me, that would be really great!
Cheers
Jakub
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Feb 3, 2015 12:31 AM, François Laupretre franc...@tekwire.net wrote:
De : Rasmus Lerdorf [mailto:ras...@lerdorf.com]
Doesn't this imply that path is the one true cache key? There are some
issues with that which we will have to address at some point. For
example, when running fpm
On Feb 3, 2015 11:26 AM, Xinchen Hui larue...@php.net wrote:
Hey:
opcache is disabled by default configure, I am plan to enable it
by default
and also add zend_extension=opcache.so in
php.ini-product/developmement
is there any objections or concerns?
thanks
No problem
want but
never (and never will) manage to agree.
--
Pierre
@pierrejoye | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Jan 31, 2015 9:08 PM, Pavel Kouřil pajou...@gmail.com wrote:
On Sat, Jan 31, 2015 at 1:41 PM, Pierre Joye pierre@gmail.com wrote:
There is zero reason to discuss what has been approved and followed for
years already.
I will simply post the link to our CS as a reminder and ask
On Jan 30, 2015 6:09 PM, Tony Marston tonymars...@hotmail.com wrote:
Pavel Kouril wrote in message
news:cab6yzuzymbaa5i3f9nsvebg2b7yjvo4ryvpy-eac78rsojx...@mail.gmail.com...
On Wed, Jan 28, 2015 at 1:17 PM, Michael Wallner m...@php.net wrote:
Hi,
snip
Hello,
just one observation -
On Jan 31, 2015 5:57 PM, Tony Marston tonymars...@hotmail.com wrote:
Yasuo Ohgaki wrote in message
news:caga2bxzgljrp6i2vdnkdga8dw7nothc9ie17tst40kpbbha...@mail.gmail.com...
Hi Tony,
On Fri, Jan 30, 2015 at 7:08 PM, Tony Marston tonymars...@hotmail.com
wrote:
Pavel Kouril wrote in
On Jan 28, 2015 4:49 PM, Michael Wallner m...@php.net wrote:
On 23/01/15 09:27, Michael Wallner wrote:
On 23 01 2015, at 02:40, Pierre Joye pierre@gmail.com wrote:
On Thu, Jan 22, 2015 at 5:32 PM, Michael Wallner m...@php.net
wrote:
Hi!
Now, that I'm mostly done with porting
how we can help 3rd extensions (and solve the
sapi ones too) developer by providing solutions, standard and tools instead
of talking about a de facto dead cow.
Cheers,
Pierre
On Jan 27, 2015 4:36 PM, Derick Rethans der...@php.net wrote:
On Tue, 27 Jan 2015, Pierre Joye wrote:
On Jan 27, 2015 11:25 AM, Yasuo Ohgaki yohg...@ohgaki.net wrote:
On Tue, Jan 27, 2015 at 12:56 PM, Kalle Sommer Nielsen ka...@php.net
wrote:
I think the warning is fair
On Jan 28, 2015 3:36 AM, Sebastian Bergmann sebast...@php.net wrote:
Am 27.01.2015 um 21:13 schrieb Pierre Joye:
However there is one thing we do need to care, and this is 3rd party
extensions. This is all I care about and why I initiated pickle.
It just that I am not convinced
On Wed, Jan 28, 2015 at 8:10 AM, Jan Ehrhardt php...@ehrhardt.nl wrote:
Sebastian Bergmann in php.internals (Tue, 27 Jan 2015 21:36:49 +0100):
Am 27.01.2015 um 21:13 schrieb Pierre Joye:
However there is one thing we do need to care, and this is 3rd party
extensions. This is all I care about
On Jan 27, 2015 12:03 AM, Ferenc Kovacs tyr...@gmail.com wrote:
On Mon, Jan 26, 2015 at 3:45 PM, Sebastian Bergmann sebast...@php.net
wrote:
Am 26.01.2015 um 13:56 schrieb Lester Caine:
how would YOU propose to replace it?
I am not talking about replacing but removing.
--
PHP
On Jan 27, 2015 12:01 PM, Pierre Joye pierre@gmail.com wrote:
On Jan 27, 2015 2:29 AM, Derick Rethans der...@php.net wrote:
On Mon, 26 Jan 2015, Ferenc Kovacs wrote:
On Mon, Jan 26, 2015 at 3:45 PM, Sebastian Bergmann sebast...@php.net
wrote:
Am 26.01.2015 um 13:56 schrieb
701 - 800 of 4120 matches
Mail list logo
