PHP 4 Bug Database summary - http://bugs.php.net
Num Status Summary (774 total including feature requests)
===[*General Issues]==
26223 Assigned Error message makes PHP crash (in some special cases)
27372 Verified parse error loadin
PHP 4 Bug Database summary - http://bugs.php.net
Num Status Summary (756 total including feature requests)
===[*General Issues]==
26223 Assigned Error message makes PHP crash (in some special cases)
27372 Verified parse error loadin
PHP 4 Bug Database summary - http://bugs.php.net
Num Status Summary (752 total including feature requests)
===[*General Issues]==
26223 Feedback Error message makes PHP crash (in some special cases)
27372 Verified parse error loadin
Hi! This is the ezmlm program. I'm managing the
internals@lists.php.net mailing list.
I'm working for my owner, who can be reached
at internals-ow...@lists.php.net.
To confirm that you would like
arch...@mail-archive.com
added to the internals mailing list, please send
an empt
Hi! This is the ezmlm program. I'm managing the
internals@lists.php.net mailing list.
I'm working for my owner, who can be reached
at internals-ow...@lists.php.net.
To confirm that you would like
arch...@mail-archive.com
added to the internals mailing list, please send
an empt
Hi! This is the ezmlm program. I'm managing the
internals@lists.php.net mailing list.
I'm working for my owner, who can be reached
at internals-ow...@lists.php.net.
Acknowledgment: I have added the address
arch...@mail-archive.com
to the internals mailing list.
Welcome to
2 correct
and replace Example 1 with it.
Is relying on warnings being converted to exceptions by error handler is
equivalent to checking return value with regards to the set of error
conditions covered? If this guarantee is already there, please point to
me to the relevant documentation page.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
ready (and particularly the renaming of the
> PHP_SDK_VC environment variable to PHP_SDK_VS). You may have to adapt
> custom tooling accordingly, though.
>
> Thanks,
> Christoph
>
> [1] <https://windows.php.net/>
>
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hello,
I hope this is the appropriate mailing list, please redirect me to better
please if required.
I am currently rewriting our PHP extension from PHP5 to PHP7.
To call PHP methods from our C/C++ code we use slightly modified
zend_call_method from Zend/zend_interfaces.c (to use more argumen
ov
Sent: Wednesday, January 8, 2020 4:06 PM
To: mdole...@noctuint.cz
Cc: PHP internals
Subject: Re: [PHP-DEV] zend_call_method with arguments passed by reference
On Wed, Jan 8, 2020 at 3:59 PM mdolezal.noctuint.cz via internals <
internals@lists.php.net> wrote:
> Hello,
>
> I h
al Message-
From: Nikita Popov
Sent: Thursday, January 9, 2020 1:17 PM
To: mdole...@noctuint.cz
Cc: PHP internals
Subject: Re: [PHP-DEV] zend_call_method with arguments passed by reference
On Wed, Jan 8, 2020 at 4:18 PM wrote:
> Thank you for your answer Nikita.
> Can you please give
On Monday 10 April 2023 14:17:04 (+02:00), G. P. B. wrote:
> Hello Internals,
>
> Dan and I would like to propose a new core autoloading mechanism [...]
>
> The existing SPL autoloading functions would become aliases to the new
Core
> ones and will continue to work with
areas for
improvement of PHP, e.g. like a roadmap/wishlist for 9.0?
Regards //Björn L
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
FC's that was rejected and maybe these can be brought to
life again for 9.0 to bring added value besides completely new features.
E.g. one of my favourites was the Pipe operator RFC.
Regards //Björn L
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
ld be considered as well.
Thanks and have a great day.
On Wed, Apr 12, 2023 at 2:53 PM Alex Wells wrote:
>
> Hey.
>
> PHP currently uses internals@lists.php.net for communication. That includes
> mostly RFCs (or their votings, or their pre-discussion) and sometimes
> questions abou
Den 2023-04-13 kl. 10:38, skrev Mikhail Galanin via internals:
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 cle
problem:
/** @param callable(int $x, int $y): int $c */
function takeTwo(callable $c);
takeTwo(fn ($x, $y) => $x + $y);
3. And another reason they failed: callables are going to want
generic types pretty commonly. Think array_filter, array_map, etc.
So, I think these brain dump RFCs are all focusing on the wrong problems.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
On Thu, Apr 20, 2023 at 9:57 PM Deleu wrote:
>
>
>
> On Thu, Apr 20, 2023 at 8:23 PM Levi Morrison via internals
> wrote:
>>
>> I'm going to stop here. Two big things:
>>
>> 1. I think reducing verbosity can be left for the future. We don'
lves,
with some bad downsides if "the wrong people" get in there. You know,
the power-hungry egotistical kind of people.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
PHP 8.3 release management
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
be array or callable object) as those are not
supported by ini_get()/in_set().
-- hakre
p.s. thank you for creating this RFC and taking care.
[1]: https://www.php.net/manual/en/function.assert.php
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
why we couldn't allow `new class() extends $someClass` in
the future to specifically allow them to do this. I mean, I'm not
going to lobby for it, I'm just pointing out that is more aligned and
consistent with other parts of the language, than to simply make it
final by default.
Ch
...
fwrite($tempHandle, "hello world\n");
rewind($tempHandle);
$result = file_put_contents($destinationPath, $tempHandle);
fclose($tempHandle);
Why move the temporary file when it is already a temporary file, right?
-- hakre
--
PHP Internals - PHP Runtime Development Mailing L
e first
place, do it. If not, don't create it, as otherwise you have the copy
already and this prevents you from learning if the file transaction really
needs it to become robust or it is just extra I/O for nothing (and perhaps
introduces places to error you actually don't want to
ing out the RFC
> karma would need your Wiki name.
>
> Best regards
> Tim Düsterhus
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: https://www.php.net/unsub.php
>
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
be consecutive.
>
> In any case, I think a utility function such as `array_group` will be widely
> useful.
>
> Please find attached a patch with a proposed implementation. Curious about
> your feedback.
>
> Best,
>
> Boro Sitnikovski
>
I'm sorry if one of the many replies already mentioned this, but there
was a failed RFC for `array_group`:
https://wiki.php.net/rfc/array_column_results_grouping. Note that I
voted against it for technical reasons (the signature was just awful,
we can do better), but I am not against the idea of adding such helper
functions in principle.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
y I managed to create a working implementation for this feature which
> would make it possible to properly modify readonly properties
> while simplifying how we write "wither" methods:
> https://wiki.php.net/rfc/clone_with
>
> Regards,
> Máté Kocsis
I apologize if this has been
improve it if something is
done, but it's not much of a problem.
The problem is when there's a wildly different signature, or if args
change the return type structure, etc. So in this case, the problem is
really:
public function __construct(string $isostr, int $options = 0) {}
Which can't really be unified with the others very well.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
Hello, PHP Internals,
I am moving my RFC for interface default methods to discussion:
https://wiki.php.net/rfc/interface-default-methods.
This can be a useful tool for a few reasons:
1. It can make implementing an interface easier when certain methods
can be implemented by other methods in the
f
> what can happen once the RFC would be accepted.
Juliette, it's in the RFC under the second bullet point here:
https://wiki.php.net/rfc/interface-default-methods#backward_incompatible_changes.
Is there something specific you'd like added there?
--
PHP Internals - PHP Runtime De
I have added a brief section in RFC impact that code analysis tools
will need to be updated. This is implicitly true for many language
features, but I see no harm in calling it out in the RFC, so I have
done so. Thank you for the feedback.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
rue, then absent
further evidence, I would say to allow it.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
On Fri, Jun 16, 2023 at 11:51 AM Deleu wrote:
>
>
> On Thu, Jun 15, 2023 at 12:48 AM Levi Morrison via internals
> wrote:
>>
>> Hello, PHP Internals,
>>
>> I am moving my RFC for interface default methods to discussion:
>> https://wiki.php.net/rfc/inte
On Sat, Jun 17, 2023 at 4:10 PM David Gebler wrote:
>
> On Thu, Jun 15, 2023 at 4:48 AM Levi Morrison via internals
> wrote:
>>
>>
>> I am moving my RFC for interface default methods to discussion:
>> https://wiki.php.net/rfc/interface-default-methods.
>
Good morning, all!
This is a friendly reminder from your RMs that the PHP 8.3 feature
freeze is in ~4 weeks on July 18th [1]. Alpha1 is already out and Alpha2
is scheduled this Thursday.
All new features and RFCs need to be discussed with voting polls closed
on or before July 18th for inclus
t is
code that has been working flawlessly for 9 years, so it's only work and
no benefit. Given that deprecations are piling up for 8.x track I think
one should be a bit cautious when approaching the next major version.
r//Björn L
--
PHP Internals - PHP Runtime Development Mailing List
To un
;s one more topic that
needs to go in there, tentatively called 'default cancelling':
```php
interface Interface1 { function m1() { /* ... */ } }
interface Interface2 extends Interface1 {
function m1(); // may or may not change signature
}
```
For various reasons which I'll put in the RFC, this will "cancel" the
default, meaning any class which implements Interface2 instead of
Interface1 will not receive that default.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
On Wed, Jun 28, 2023 at 10:09 AM G. P. B. wrote:
>
> Hello internals,
>
> I'm opening the vote for the
> Deprecate remains of string evaluated code assertions RFC:
> https://wiki.php.net/rfc/assert-string-eval-cleanup
>
> It will last for two weeks and end on Wednes
depth
> discussion. This is probably going to bite in the longer term.
>
> Best regards
> Tim Düsterhus
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: https://www.php.net/unsub.php
>
I suppose different people will think different thi
is point it's not an ego-hit. But that's not a
> process everyone has gone through.
>
> In short, I suspect at least much of the pushback is "that is weird and not
> normal, according to the normal I first learned, so it must be a bad idea,"
> and people just stop there.
>
> (If you voted no and the above description doesn't apply to you, please do
> explain what your alternate reasoning is, because RFC authors desperately
> need more feedback than we get right now.)
>
> --Larry Garfield
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: https://www.php.net/unsub.php
, create new or would it be better to start with a RFC?
Links:
[1] https://github.com/php/php-src/pull/950
[2] https://linux.die.net/man/3/freopen
Thanks
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
cipated in the
discussion and the voting.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
hange
attributes to non default values, this is not a programming question
I have.
I hope you don't mind the attention to detail.
Best
-- hakre
[1]:
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/NumberFormat/NumberFormat#roundingmode
--
PHP Internals - P
On Thursday 03 August 2023 21:07:35 (+02:00), Tim Düsterhus wrote:
> Hi
>
> On 8/3/23 20:55, Hans Krentel via internals wrote:
> > Feedback from actual ICU caretakers would be good though, because me
> > is entirely from a users perspective, also I know how to change
ne, but in hindsight of output
formatting - obviously the totally other side - the current default is
surprising, too.
But it is certainly the safer path to not change it.
For now, I've already learned a lot more and should take some time to
look into this. E.g. understanding why this
ture. It
> will be unexpected for users if their code completely fails to work on
> Windows, because the suffix is ignored.
>
> For that reason I voted "no".
>
> Best regards
> Tim Düsterhus
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To
Thanks for the proposal Niels,
I’ve dealt with my own grief working through issues in DOMDocument and wanting
it to work but finding it inadequate.
> HTML5
This would be a great starting point; I would love it if we took the
opportunity to fix named character reference decoding, as PHP has (to
he.ni...@gmail.com>> wrote:
>>>
>>> I'm opening the discussion for my RFC "DOM HTML5 parsing and serialization
>>> support".
>>> https://wiki.php.net/rfc/domdocument_html5_parser
>>> <https://wiki.php.net/rfc/domdocument_html5_parser>
>>>
>>> Kind regards
>>> Niels
>
Impressive proposal. It will be nice to have. Did you consider any tricks for
text encoding, such as converting non-utf8 documents into utf8 first before
parsing? Was wondering if we did that if we could lean on `iconv` and save the
extra data in the library, if that’s important enough.
Cheers,
Dennis Snell
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
Den 2023-09-11 kl. 11:28, skrev Dmitry Stogov:
Hi internals,
I'm glad to present a new JIT engine that is going to be used in the next
major PHP version. Now it's a real optimizing compiler with Intermediate
Representation similar to Java HotSpot server compiler.
It makes a base
eferences.
Kindly,
Dennis Snell
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
is recommendation. Perhaps someone has time to investigate
this? Anyway, it's "future work."
I have voted for 11, but will not be hurt in any way if 12 wins.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
` is more appropriate, that they aren’t supplying HTML
documents with in-band text encoding information, and so there’s a chance that
de-emphasizing the parameter may be technically more accurate and practically
less helpful.
Love seeing all the continued work on this!
Thank you so much for yo
> Just chiming in here to say that while we don't offer a createFragment() in
> this proposal, it's possible to parse fragments by passing the
> LIBXML_HTML_NOIMPLIED option. Alternatively, in the future I plan to offer
> innerHTML which you could use then in conjunction with
> createDocumentFr
On Thu, Oct 5, 2023 at 1:52 PM Dmitry Stogov wrote:
>
> Hi internals,
>
> The vote on "A new JIT implementation based on IR Framework" RFC is started.
>
> https://wiki.php.net/rfc/jit-ir
>
> Thanks. Dmitry.
>From the RFC:
> The details of the IR fram
:
```php
$value = \array_first($array);
if ($value === null) {
// handle the failure
} else {
// success
}
```
But I fear in practice people will just omit the error checking.
One way around that is to throw an exception. I'm not sure how I feel
about that, but I'll think about it.
-
perfectly fine to use `array_first` or `array_last` with
`$foo`. I think probably you would use `array_key_first` and
`array_key_last` so you also get the key and not just the value, but I
don't see any need to reduce `array_first` and `array_last` to only be
logical or correct with arrays th
begrudgingly) leave empty() and warn against its use, and have
is_empty() as a new thing. Maybe for some future deprecation or
removal?
I also do like the idea that someone else mentioned here about being
able to possibly start to get away from @'ing variables with a
solution like this.
-B.
-
Hi, internals.
> As shown in the following issue, the behavior of `PDO::PARAM_` is
> inconsistent and I would like to fix this.
> https://github.com/php/php-src/issues/12603
I consider the current behavior a bug.
And some of them contain behaviors that are very confusing to users.
tributions are interesting and invaluable. They
are much appreciated.
Best regards
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
elect 1 = true ; -- `ERROR: operator does not exist: integer = boolean`
The conditions for casting and comparison were different.
`PDO_PARAM_INT` still needs to be passed as `unknown` to PostgreSQL.
Thank you!
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https
https://hub.docker.com/_/php
[3]: https://www.youtube.com/watch?v=yq2rq50IMSQ
[4]: https://github.com/advisories/GHSA-jm6m-4632-36hf
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
On Tue, Nov 7, 2023 at 11:46 AM Sebastian Bergmann wrote:
> Am 07.11.2023 um 11:33 schrieb Thomas Chauchefoin via internals:
> > For instance, the official Docker image has it on [2].
>
> "Official" is relative here. That image is maintained by (the) Docker
> (communi
> The migration path is to convert the legacy-encoding PHP files to UTF-8.
Please take a look at the following code.
This is a part of the code that I am actually maintaining in the
latest version of php.
```php
https://www.php.net/unsub.php
1]: https://www.php.net/manual/en/function.mb-strpos.php
[2]: https://www.php.net/manual/de/function.mb-substr.php
[3]: https://www.php.net/manual/de/function.mb-strstr.php
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
that PHP itself MAY
do nothing (or SHOULD NOT do anything).
Regarts.
Kentaro Takeda
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
d bravely pressed on.
>
> The story ends with an ironic twist. Many years later, I became interested in
> mbstring and reimplemented its internals, replacing the libmbfl code with
> fresh new code which ran many times faster. The new code was so much faster
> that in some cases, t
ck
> strings derived from user input using mb_check_encoding() before operating on
> them. Unfortunately, "should" doesn't count for much. Most users will not do
> what they "should".
>
> 5) Amending the documentation to call out these dangers more clearly w
; Please let me know what you think.
>
> --
> Best regards,
> Max Semenik
>
> --6c4879060c12de83--
>
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
> On Dec 9, 2023, at 4:55 PM, Robert Landers wrote:
>
> On Sat, Dec 9, 2023 at 4:32 PM Dennis Snell via internals
> wrote:
>>
>> Max, I love this idea.
>>
>> Would it make sense to flip the design though and add `#[Serializable]` with
>> a new `
maintain consistency, for example `rollbackToSavepoint(string $name)`.
Regards.
Kentaro
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
Hello, how about add json_errors like html_errors and option for injecting
json_errors in response(if response json object(ex. {"success":false}) append
new field(ex. php_error {"success":false,"php_errors":{"stack":...}}))?Thanks.
Hi, i guess need add warning in log if file with extension ".php" not contains
"
I'm sorry, but if you seriously believe doing something that generates a
notice (or warning, or error, ...) is not a bug - you're delusional.
That is the very definition of a bug and notices/warnings/errors etc.
are the mechanism the language uses to report these bugs to the
developer. If doing
.08.19 14:43, Claude Pache wrote:
Le 29 août 2019 à 13:33, Aegir Leet via internals
mailto:internals@lists.php.net>> a écrit :
I'm sorry, but if you seriously believe doing something that generates a
notice (or warning, or error, ...) is not a bug - you're delusional.
No, wh
I am the new PHP Windows lead inside Microsoft. My role is to help develop
security patches for the Windows builds of PHP.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
something from newer versions (which it doesn't
look like we do), anything newer than 7.29 would just cause friction
for people building from source.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
the
quite low bar of contributing a few improvements to our docs or
website. To help expedite the process, I recommend visiting the PHP
chat room on StackOverflow where quite a few people with internals
knowledge (and importantly, can merge contributions) hang out. If you
want to hack on the PHP.net web
should not generally be met with resistance. If
someone has contributed before, we should be happy to have them back.
And all of this doesn't really matter that much; as Nikita pointed out
it is pretty easy to get an account, and most people simply don't care
to vote.
--
PHP Inter
work with
the array_* functions that work without references, in which case I
think we think this RFC is the wrong approach as it is inadequate for
that purpose.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
t the
time the closure is created, not ran. Imagine passing a private method
as a callback; if it was done via `[$obj, 'privatemethod']` then it
will fail at runtime, because the scope it's called in doesn't have
access.
--
PHP Internals - PHP Runtime Development Mailing List
To
nly): @AndrePolykanine
Original message
From: Andreas Heigl
To: internals@lists.php.net
Date created: , 7:31:17 AM
Subject: Moving the documentation to git
Hey Internals and docs-folks
On Monday we finished the first important step of moving the
documentation to
On Thu, Feb 13, 2020 at 2:48 AM Nikita Popov wrote:
>
> Hi internals,
>
> This has been discussed a while ago already, now as a proper proposal:
> https://wiki.php.net/rfc/token_as_object
>
> tl;dr is that it allows you to get token_get_all() output as an array of
> PhpTok
ct's data.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Wed, Feb 26, 2020 at 4:47 AM Nikita Popov wrote:
>
> Hi internals,
>
> Generators currently do not support rewinding -- or rather, only support it
> if the generator is at/before the first yield, in which case rewinding is a
> no-op.
>
> Generators make it real breeze
On Tue, Mar 3, 2020 at 8:01 AM Nikita Popov wrote:
>
> On Fri, Feb 7, 2020 at 11:32 AM Nikita Popov wrote:
>
> > Hi internals,
> >
> > I've sent a mail about this before, but as this turned into a bit of a
> > larger change (also allowing "abstract
certain about this, but
do not like it.
I do appreciate the RFC, but think it needs a bit more work.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
laced on the RFC authors, not the voters.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
ecute();
This is part of my [highest score answer on StackOverflow][1].
Critically, applying the ids array as `...` will handle the
by-reference passing.
I don't think we need to improve the ergonmics of mysqli for this case
specifically, as it's always going to require some dynamic SQL
g
a viable model, but it's
still useful today.
-
There is a tool called pickle that is intended to work on Windows and
Linux. It doesn't seem recently maintained (but probably still in
better shape than pecl). It has too much abstraction for my taste, so
I didn't look at its source a l
or another way to address this space, but it
too has drawbacks; there's inherently no free lunch here, I think.
> * Compound Property Visibility
What is this last one? I searched for "compound" in the article, but
did not get many hits, none of which described what it actually _is
To me, this is almost a good idea. However, I would want regular type
checking, not casts. Importantly, regular type checks would fit well
on allowing array destructuring directly in function signatures, which
would basically be a form of named parameters.
--
PHP Internals - PHP Runtime
require $file;
}
Weird isn't it? Authors are using require instead of include for the
case where failure is tolerated. This is a clear signal to me that
include isn't doing its job. The warning gets in the way.
Any reasons we shouldn't just remove this warning for PHP 8?
--
PHP Inter
space, but this is not it. I don't want perfect to be the enemy of
good either, but I think this still needs more work. Maybe interested
parties (including me) can collaborate off-list somewhere?
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Tue, Mar 31, 2020 at 12:51 PM Ilija Tovilo wrote:
>
> Hi internals
>
> A few days ago I opened the discussion on the switch expression RFC:
> https://wiki.php.net/rfc/switch_expression
>
> There's been a fundamental disagreement on what the switch expression
> s
> > they need to be on their own lines?
>
> Just to say, with descriptive names and type declarations (and now
> union types), even a method with just two or three parameters can need
> to be wrapped to keep lines below 120 characters ;) Maybe the RFC
> could include an exam
orried about variadics having named parameters in them. I
remember encountering code that assumes that `...$a` is a packed
array. Is that assumption always correct today?
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
d be
> very valuable.
>
> Though you have much more experience with internals than I do, I think that
> building a consensus around a bold new vision for PHP collections would be
> a near-Sisyphean task.
>
> Adding a list/vector type would be a much smaller, more easily definable
&
pecial case these 3 types and would probably want to figure out some
way for at least internal classes to have value semantics. Any
contrarian opinions there, especially from main php-src contributors
like Nikita and Dmitry?
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
t; That handles break;
Sadly, it doesn't. That code is valid today:
Which outputs:
1
2
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Tue, Apr 28, 2020 at 6:58 PM Larry Garfield wrote:
>
> On Tue, Apr 28, 2020, at 7:37 PM, Levi Morrison via internals wrote:
> > > One issue that was discussed a few weeks ago, and led to the current
> > > syntax, was too many variations within the switch syntax; of cou
501 - 600 of 839 matches
Mail list logo
