Hi there,
I was checking our codebase and realised that we still use the
function proposed by Antony a long time ago [1]. I run through the
comments and feel like I can address the issues discussed back then.
My question is what would be the best way to move forward? Shall I
reopen the PR, create
Hi,
Thank you for the proposal - it echoes somewhere inside me.
Just a little side-view of the problem...
Personally, I will be a fan of Kotlin-style Path API
E.g., the path is an object so we can get path items, and get
sub-path/resolve child nodes.
It appeared to be quite useful in practice.
Hello good people,
Looks like another hot discussion on the list, isn't it?
Just wanted to share my notice about the initial idea.
7 years ago there were people considering NNTP as an option. Nowadays,
it's pretty clear that it isn't the way to go. It doesn't mean that
technology is bad (althoug
ote:
>
> On Mon, Nov 28, 2022 at 4:13 PM Derick Rethans wrote:
>>
>> On Fri, 21 Oct 2022, Mikhail Galanin via internals wrote:
>> > Looking into the future, probably we would like to have this format
>> > configurable, if so it looks easy to do but still I can't
Hello good people,
(really hope I'm writing into the right thread this time).
I updated the patch considering the thoughts from this thread. Thank
you all for being so much responsive and helpful!
Meanwhile, there are two changes:
* Added function `php_format_timestamp' that takes microseconds
ISO8601 but if we have a
consensus here, I'm open to updating the patch. Basically, I'm open to
everything, please share your opinions.
Pull-request: https://github.com/php/php-src/pull/9844
On Fri, Oct 21, 2022 at 11:46 AM Rowan Tommins wrote:
>
> On 21 October 2022 08
Description
Hi there,
I started this thread on GitHub but Christoph (cmb69) suggested this
is the better place to discuss such a thing.
(initial post: https://github.com/php/php-src/issues/9745)
Basically, we have quite a high-loaded environment and we really want
to see timestamps
containing
