Stephen Coakley:
So what should be the desired behavior, in regard to bug #68270? One
possible behavior would be to, if an exception is thrown inside a
finally block, to attach the uncaught exception from the try block via
the addSupressed() method. The last exception is thrown, and the
Hi!
This is already part of the public API: var_dump and debug_zval_dump do
expose object IDs to userland. It's just inefficient to get for more
Debug functions are not the part of public API. If you rely on anything
var_dump is producing for your code to work, you risk your code being
broken
Hi!
I've been pinged many times to add a new spl_object_id() function to PHP,
that would return the internal object handle of an object.
What would be the use of this?
Today, spl_object_hash() partially allows that, but adds many randomness to
the result, which is not very cool to use later
Hi Stas,
thanks for hooking into this thread
However, committing to having specific object ID (e.g. as integer) as
part of public API is pretty big commitment
This is already part of the public API: var_dump and debug_zval_dump do
expose object IDs to userland. It's just inefficient to get
Hi!
Some suspicious use of spl_object_hash() out there...
https://github.com/symfony/symfony/blob/master/src/Symfony/Component/VarDumper/Cloner/VarCloner.php
Not sure what this one does... but calculations with spl_object_hash()
look very suspicious.
Hi!
I'd prefer to add a separate function spl_object_id, which directly returns
the handle. This should supersede spl_object_hash in the long run.
Since in PHP 7 there's no longer a possibility of having different
object stores, as far as I can see, spl_object_id can identify an object
(it
Hi!
It would be awesome if this patch could be applied for php 7.0!
Please don't. This changes the whole meaning of spl_object_hash, and
serves no useful purpose. If you need the id so much, it should be a
separate function. I am still against exposing raw IDs, but if the
consensus is we need
Markus Malkusch:
The try-finally scenario involves only one supressed
exception. I'd like to see a possibility to add more supressed
exceptions
Actually try-finally can already involve several supressed exceptions as
well:
try {
throw new Exception(Exception 1);
} finally {
try {
2015-08-02 14:32 GMT+02:00 Markus Malkusch mar...@malkusch.de:
Dor Tchizik wrote:
Currently, PHP discussions are held on the various mailing lists, managed
by an old mailing list system, without any proper alternative interface
to
follow and respond outside of mailing.
What wrong with
On 2 August 2015 13:54:46 BST, Niklas Keller m...@kelunik.com wrote:
We're discussing issues here, so what's wrong with an issue tracker?
No, we're discussing every aspect of the project, from release management to
personal introductions.
I can see more than one benefit. Probably most
On 02/08/15 13:52, Rowan Collins wrote:
As a final note, while encouraging new users is definitely a good thing, any
project the size of PHP will always have a core set of developers who spend a
lot of time working on and discussing it. If you make those people's lives
difficult, no amount
Hello internals!
I wanted to propose a change to how PHP discussions are made.
Currently, PHP discussions are held on the various mailing lists, managed
by an old mailing list system, without any proper alternative interface to
follow and respond outside of mailing.
The discussion is hidden
On 2 August 2015 13:38:47 BST, Dor Tchizik d...@tchizik.com wrote:
On Sun, Aug 2, 2015 at 3:38 PM Dor Tchizik d...@tchizik.com wrote:
On Sun, Aug 2, 2015 at 3:32 PM Markus Malkusch mar...@malkusch.de
wrote:
What wrong with news://news.php.net/;?
No threads, no searchability, no ability to
Niklas Keller wrote:
2015-08-02 14:32 GMT+02:00 Markus Malkusch mar...@malkusch.de:
What wrong with news://news.php.net/?
That's a joke, right?
No it's not, why should it? You did notice the news:// scheme, did you?
We're discussing issues here, so what's wrong with an issue tracker?
Ok,
Hi Dor.
Am 02.08.2015 um 14:01 schrieb Dor Tchizik d...@tchizik.com:
Hello internals!
I wanted to propose a change to how PHP discussions are made.
Currently, PHP discussions are held on the various mailing lists, managed
by an old mailing list system, without any proper alternative
Hi Niklas
Am 02.08.2015 um 16:26 schrieb Niklas Keller m...@kelunik.com:
2015-08-02 15:29 GMT+02:00 Rowan Collins rowan.coll...@gmail.com:
On 2 August 2015 13:54:46 BST, Niklas Keller m...@kelunik.com wrote:
We're discussing issues here, so what's wrong with an issue tracker?
No, we're
On 2 August 2015 15:26:00 BST, Niklas Keller m...@kelunik.com wrote:
2015-08-02 15:29 GMT+02:00 Rowan Collins rowan.coll...@gmail.com:
On 2 August 2015 13:54:46 BST, Niklas Keller m...@kelunik.com wrote:
We're discussing issues here, so what's wrong with an issue tracker?
No, we're discussing
On 31 Jul 2015, at 17:40, Ronald Chmara rona...@gmail.com wrote:
The RFC and bug report both make an erroneous assumption that unescaped GPC
input is wrong.
Hi Ronabop,
Slightly continuing our discussion, but also replying to your on-list message...
Starting with your examples:
1) Web
Markus Malkusch:
try {
throw new Exception(Exception 1);
} finally {
try {
} finally {
throw new Exception(Exception 3);
}
}
In this case the only place for the suppressed exception 1 can be
exception 3. For consistency and simplicity I'd therefore suggest
Stephen Coakley:
This is the behavior in both Java and C#. Python has a different
approach. Python has two properties that contain previous exceptions:
__context__, which holds implicitly chained exceptions, and __cause__,
which holds explicitly chained exceptions. This system makes a ton of
Dor Tchizik wrote:
malkusch:
What wrong with news://news.php.net/?
No threads, no searchability, no ability to respond.
Try to use any decent newsreader and there you have everything you are
missing.
I do note that we also have a misunderstanding. I am not talking about that
readonly
2015-08-02 15:29 GMT+02:00 Rowan Collins rowan.coll...@gmail.com:
On 2 August 2015 13:54:46 BST, Niklas Keller m...@kelunik.com wrote:
We're discussing issues here, so what's wrong with an issue tracker?
No, we're discussing every aspect of the project, from release management
to personal
Hi Anatol,
- Original Message -
From: Anatol Belski
Sent: Friday, July 31, 2015
Commit:3a66a23679487f4feda699ada109ab2b675e9474
Author:Anatol Belski a...@php.net Fri, 31 Jul 2015 14:02:03
+0200
Parents: 7be9e69eafdb1828d09daecde5cd39112db3f581
Branches: master
On 2 August 2015 15:26:00 BST, Niklas Keller m...@kelunik.com wrote:
How about a tool like Phabricator?
I've never used Phabricator, but it does look like a nice project management
tool. I first heard of it in reference to Wikimedia migrating a whole bunch of
teams to it as a unified tool.
On Fri, 31 Jul 2015, Julien Pauli wrote:
Hi people.
I've been pinged many times to add a new spl_object_id() function to PHP,
that would return the internal object handle of an object.
Today, spl_object_hash() partially allows that, but adds many randomness to
the result, which is not
As I describe below, I agree with Nikita on spl_object_id().
Am 02.08.2015 um 08:52 schrieb Stanislav Malyshev smalys...@gmail.com:
Hi!
Some suspicious use of spl_object_hash() out there...
On 02/08/2015 18:41, Bob Weinand wrote:
Some suspicious use of spl_object_hash() out there...
https://github.com/symfony/symfony/blob/master/src/Symfony/Component/VarDumper/Cloner/VarCloner.php
Not sure what this one does... but calculations with spl_object_hash()
look very suspicious.
On Sun, Aug 2, 2015 at 5:29 PM Andreas Heigl andr...@heigl.org wrote:
Hi Dor.
Am 02.08.2015 um 14:01 schrieb Dor Tchizik d...@tchizik.com:
Hello internals!
I wanted to propose a change to how PHP discussions are made.
Currently, PHP discussions are held on the various mailing
Hi,
2015-08-02 9:01 GMT-03:00 Dor Tchizik d...@tchizik.com:
Hello internals!
I wanted to propose a change to how PHP discussions are made.
Currently, PHP discussions are held on the various mailing lists, managed
by an old mailing list system, without any proper alternative interface to
Am 02.08.2015 um 17:12 schrieb Niklas Keller m...@kelunik.com:
2015-08-02 16:48 GMT+02:00 Andreas Heigl andr...@heigl.org:
Hi Niklas
Am 02.08.2015 um 16:26 schrieb Niklas Keller m...@kelunik.com:
2015-08-02 15:29 GMT+02:00 Rowan Collins rowan.coll...@gmail.com:
On 2 August 2015
Hi all,
- Original Message -
From: Matt Wilmas
Sent: Wednesday, July 08, 2015
Hi Kalle,
- Original Message -
From: Kalle Sommer Nielsen
Sent: Wednesday, July 08, 2015
Hi Matt
2015-07-08 17:00 GMT+02:00 Matt Wilmas php_li...@realplain.com:
Hi all,
- Original Message
On 01/08/2015 01:06, Rowan Collins wrote:
On 1 August 2015 00:36:58 BST, Stanislav Malyshev smalys...@gmail.com wrote:
DEBUG_BACKTRACE_IGNORE_ARGS in a debug_backtrace() call. IIRC the
object of called methods is already excluded (equivalent to masking
out DEBUG_PROVIDE_OBJECT) so what's left
Am 02.08.2015 um 19:09 schrieb Derick Rethans der...@php.net:
On Fri, 31 Jul 2015, Julien Pauli wrote:
Hi people.
I've been pinged many times to add a new spl_object_id() function to PHP,
that would return the internal object handle of an object.
Today, spl_object_hash() partially
Dor Tchizik wrote:
Currently, PHP discussions are held on the various mailing lists, managed
by an old mailing list system, without any proper alternative interface to
follow and respond outside of mailing.
What wrong with news://news.php.net/?
I propose that internals discussion to be
On Sun, Aug 2, 2015 at 3:38 PM Dor Tchizik d...@tchizik.com wrote:
On Sun, Aug 2, 2015 at 3:32 PM Markus Malkusch mar...@malkusch.de wrote:
Dor Tchizik wrote:
Currently, PHP discussions are held on the various mailing lists,
managed
by an old mailing list system, without any proper
On 2 August 2015 13:01:57 BST, Dor Tchizik d...@tchizik.com wrote:
I propose that internals discussion to be moved (eventually entirely)
to a
different medium, where the example I have in mind is GitHub issues
(but
that is up for discussion).
While I think a different medium could be worth
2015-08-02 16:48 GMT+02:00 Andreas Heigl andr...@heigl.org:
Hi Niklas
Am 02.08.2015 um 16:26 schrieb Niklas Keller m...@kelunik.com:
2015-08-02 15:29 GMT+02:00 Rowan Collins rowan.coll...@gmail.com:
On 2 August 2015 13:54:46 BST, Niklas Keller m...@kelunik.com wrote:
We're
On 02/08/15 15:29, Andreas Heigl wrote:
And I'm not sure Whether I want someone messing arround with the language
that powers 80% of the WorldWideWeb who isn't able to get his tools set up
properly. But that's just my 2 arrogant cent.
Nothing arrogant about the comment ... what is more of a
On 02/08/2015 20:00, Dor Tchizik wrote:
The mailinglist might be far from perfect (which some people also say
about PHP so there's a good match) but it is a well established way of
communication in the PHP-community. I strongly believe that it would be
counterproductive to change the way of
On 02 Aug 2015, at 22:03, Niklas Keller m...@kelunik.com wrote:
I remember it being pretty trivial - enter my e-mail address, verify my
e-mail address, skim-read the etiquette doc, start discussing.
I agree with that. Getting RFC karma isn't that hard, at least not if your
mail
On 08/02/2015 03:50 AM, Markus Malkusch wrote:
Stephen Coakley:
So what should be the desired behavior, in regard to bug #68270? One
possible behavior would be to, if an exception is thrown inside a
finally block, to attach the uncaught exception from the try block via
the addSupressed()
On 08/02/2015 07:01 AM, Dor Tchizik wrote:
Hello internals!
I wanted to propose a change to how PHP discussions are made.
Currently, PHP discussions are held on the various mailing lists, managed
by an old mailing list system, without any proper alternative interface to
follow and respond
On 2 August 2015 23:15:12 BST, Stephen Coakley m...@stephencoakley.com wrote:
Heck, Thunderbird is technically a discontinued
product.
O/T, but to my knowledge Thunderbird is not discontinued, it's just changed
management because Mozilla are no longer paying for it. The new management are
On 08/02/2015 05:31 PM, Rowan Collins wrote:
On 2 August 2015 23:15:12 BST, Stephen Coakley m...@stephencoakley.com wrote:
Heck, Thunderbird is technically a discontinued
product.
O/T, but to my knowledge Thunderbird is not discontinued, it's just changed
management because Mozilla are no
This is what I think. The best way to deter the community from making
contributions is to make it hard to contribute. My C/C++ savvy buddy told
me about an awesome feature he wants to see in iojs, I can tell him to go
on GitHub and raise the issue, discussion took place, and he'd submitted a
pull
Step one: Get a proper mail client. In the mail you sent one can't see
what's from you and what you actually just quoted. All is marked as
quote.
E-Mail is great. It is a push service and I as the receiver can handle
as it matches my work flow. Applying custom filters, highlighters, have
a
On Sun, Aug 2, 2015 at 10:05 PM Dor Tchizik d...@tchizik.com wrote:
I already have. iojs (and soon, nodejs), as well as Rust which was
mentioned by someone else.
On Sun, Aug 2, 2015 at 11:04 PM Stig Bakken s...@stigbakken.com wrote:
Are you being serious? Can you provide examples of
On 02/08/2015 21:19, Marcio Almada wrote:
Hi
2015-08-02 16:52 GMT-03:00 Rowan Collins rowan.coll...@gmail.com:
On 02/08/2015 20:10, Marcio Almada wrote:
As you pointed github issues, it's worth noting that Rust internals
already use github to manage RFCs:
On 08/02/2015 08:29 AM, Rowan Collins wrote:
On 2 August 2015 13:54:46 BST, Niklas Keller m...@kelunik.com wrote:
We're discussing issues here, so what's wrong with an issue tracker?
No, we're discussing every aspect of the project, from release management to
personal introductions.
I
On 08/02/2015 08:17 AM, Markus Malkusch wrote:
Niklas Keller wrote:
2015-08-02 14:32 GMT+02:00 Markus Malkusch mar...@malkusch.de:
What wrong with news://news.php.net/?
That's a joke, right?
No it's not, why should it? You did notice the news:// scheme, did you?
We're discussing issues
On 08/02/2015 07:52 AM, Rowan Collins wrote:
On 2 August 2015 13:01:57 BST, Dor Tchizik d...@tchizik.com wrote:
I propose that internals discussion to be moved (eventually entirely)
to a
different medium, where the example I have in mind is GitHub issues
(but
that is up for discussion).
While
On 08/02/2015 05:35 PM, Marcio Almada wrote:
I'm not saying that we should do exactly the same thing. PHP is not
Rust. Rust is not PHP. But at least we could stop pretending our
process shouldn't be improved because the walls it offers supposedly
act as a filter for the one who isn't able to get
On 02/08/2015 20:10, Marcio Almada wrote:
As you pointed github issues, it's worth noting that Rust internals
already use github to manage RFCs:
https://github.com/rust-lang/rfcs/pulls?q=is%3Aopen+is%3Apr+label%3AT-lang
That's interesting. Do you have a link to any documentation on the
On Sun, Aug 2, 2015 at 11:04 PM Stig Bakken s...@stigbakken.com wrote:
Are you being serious? Can you provide examples of projects that have
successfully replaced their developer mailing lists with GitHub issues?
On 02/08/2015 21:05, Dor Tchizik wrote:
I already have. iojs (and soon,
On 08/02/2015 03:34 PM, Rowan Collins wrote:
On Sun, Aug 2, 2015 at 11:04 PM Stig Bakken s...@stigbakken.com wrote:
Are you being serious? Can you provide examples of projects that have
successfully replaced their developer mailing lists with GitHub issues?
On 02/08/2015 21:05, Dor Tchizik
On 08/02/2015 02:35 PM, Johannes Schlüter wrote:
Step one: Get a proper mail client. In the mail you sent one can't see
what's from you and what you actually just quoted. All is marked as
quote.
E-Mail is great. It is a push service and I as the receiver can handle
as it matches my work flow.
Stephen Coakley wrote:
You have to admit, NNTP news is an aging technology
Sadly admited, I didn't touch it since years. Only for you, PHP, I did start
my Knode again. And I am very content with this communication channel. Also
I like the idea that one has a choice.
Anyways, OP was
On Sun, 2015-08-02 at 19:17 +, Dor Tchizik wrote:
Now, I get that the RFC process in PHP is different, but why is it that to
even GET on the mailing list one needs to go through seven hells, only to
be in the discussion (often completely irrelevant to what he's trying to
do) for several
On Sun, Aug 2, 2015 at 2:02 PM Dor Tchizik d...@tchizik.com wrote:
Hello internals!
I wanted to propose a change to how PHP discussions are made.
Currently, PHP discussions are held on the various mailing lists, managed
by an old mailing list system, without any proper alternative interface
I remember it being pretty trivial - enter my e-mail address, verify my
e-mail address, skim-read the etiquette doc, start discussing.
I agree with that. Getting RFC karma isn't that hard, at least not if your
mail doesn't get lost during hot discussions.
If you're not interested in a
I already have. iojs (and soon, nodejs), as well as Rust which was
mentioned by someone else.
On Sun, Aug 2, 2015 at 11:04 PM Stig Bakken s...@stigbakken.com wrote:
On Sun, Aug 2, 2015 at 2:02 PM Dor Tchizik d...@tchizik.com wrote:
Hello internals!
I wanted to propose a change to how PHP
Hi
2015-08-02 16:52 GMT-03:00 Rowan Collins rowan.coll...@gmail.com:
On 02/08/2015 20:10, Marcio Almada wrote:
As you pointed github issues, it's worth noting that Rust internals
already use github to manage RFCs:
https://github.com/rust-lang/rfcs/pulls?q=is%3Aopen+is%3Apr+label%3AT-lang
Hi,
2015-08-02 17:46 GMT-03:00 Rowan Collins rowan.coll...@gmail.com:
On 02/08/2015 21:19, Marcio Almada wrote:
Hi
2015-08-02 16:52 GMT-03:00 Rowan Collins rowan.coll...@gmail.com:
On 02/08/2015 20:10, Marcio Almada wrote:
As you pointed github issues, it's worth noting that Rust
On 08/02/2015 06:40 PM, Lester Caine wrote:
On 02/08/15 23:41, Stephen Coakley wrote:
Thunderbird works great for reading nested replies and past archives,
but replying has about a 50% chance of success for me. Oh well.
I'm up to 24Gb of history over some 20 years and despite attempts by
some
On 03/08/15 00:01, Markus Malkusch wrote:
Anyways, OP was complaining about missing interfaces and features, which is
simply not true. You can communicate through Email, NNTP and if one wants a
webinterface so hardly just wrap one around NNTP. How can it be more
accessible by reducing it to
On 02/08/15 23:41, Stephen Coakley wrote:
Thunderbird works great for reading nested replies and past archives,
but replying has about a 50% chance of success for me. Oh well.
I'm up to 24Gb of history over some 20 years and despite attempts by
some developers to mess it up, Thunderbird does
On 08/02/2015 06:31 PM, Lester Caine wrote:
On 03/08/15 00:01, Markus Malkusch wrote:
Anyways, OP was complaining about missing interfaces and features, which is
simply not true. You can communicate through Email, NNTP and if one wants a
webinterface so hardly just wrap one around NNTP. How can
67 matches
Mail list logo
