[PHP-DEV] PHP 8 (or earlier) RFC Proposal
Hi, I would like to know your opinion on an RFC I'm thinking to propose. I don't have the skills to code this into PHP Core so anyone who would like to be involved is welcomed. The RFC would refer to PHP's ability to use either SWAP memory and/or SWAP Files. There are some very interesting things that PHP knows how to do, related to data-processing, filtering, regex and so on, but one of the main blockers is the "memory limit". There are servers or situation where memory can't be extended, but where disk space is available and maybe even fast enough (SSD) to cover that gap. At this moment PHP doesn't know how to use the SWAP memory from linux, and there isn't any way to specify a file that could act as one, similar to an internal PHP SWAP. I would like to propose such a system for implementation in PHP 8 (or even earlier if possible). Waiting for you comments/feedback if I should make an RFC on this. Thank you.
[PHP-DEV] Re: RFC proposal, deprecate String conversion for undefined constants.
Thanks after seeing a PR with the correct wording, I finally understood what I needed to put in that last field. I feel like a robot. Also my wiki username for the internals list is: cminick Thanks for your help! On Tue, Mar 17, 2015 at 5:21 PM, Christoph Becker cmbecke...@gmx.de wrote: Admin Admin wrote: You have to enter the email address of this mailing list into the fourth field of the form. Just gave that a try, no error message. still goes back to the form. Indeed there is a bug with regard to the messages. I have submitted a PR (https://github.com/php/web-wiki/pull/4). -- Christoph M. Becker
[PHP-DEV] RFC proposal, deprecate String conversion for undefined constants.
first of all https://wiki.php.net/start?do=register seems broken, the form submit just returns to the form. Second of all the crux of my proposal. As many of you know PHP will transform undefined constants into strings. Assuming you meant a string in bareword. I think there is a lot of danger here for state corruption and confusing results in code that can come out of this. Undefined constants should result in a fatal error. I propose we have a two step process to have a short deprecation process where we turn this notice: Notice: Use of undefined constant UNDEFINED_CONSTANT - assumed 'UNDEFINED_CONSTANT' in /in/966aq on line 3 INTO E_DEPRECATED adding This behavior will result in a fatal error in the future after which we turn the behavior into a FATAL error. I'll need some help with the patch. I took a look at it once, and since my C skills are abhorant, I found myself scratching my head at all the places that seem to throw the error message above and what each of them did. So if there is anyone that could volunteer and help me with this, that would be awesome!
[PHP-DEV] Re: RFC proposal, deprecate String conversion for undefined constants.
You have to enter the email address of this mailing list into the fourth field of the form. Just gave that a try, no error message. still goes back to the form. On Sun, Mar 15, 2015 at 5:01 PM, Christoph Becker cmbecke...@gmx.de wrote: Admin Admin wrote: first of all https://wiki.php.net/start?do=register seems broken, the form submit just returns to the form. You have to enter the email address of this mailing list into the fourth field of the form. -- Christoph M. Becker
[PHP-DEV] rename T_PAAMAYIM_NEKUDOTAYIM to T_DOUBLE_COLON
WTF is T_PAAMAYIM_NEKUDOTAYIM? This has to be THE most asked question by new php developers when they come across it. Can we please change the token name to T_DOUBLE_COLON so I don't have to hear about it constantly? Those that disagree don't do enough PHP support to know how often it is asked. it's worth it. Chad -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] rename T_PAAMAYIM_NEKUDOTAYIM to T_DOUBLE_COLON
On 10/29/2010 08:11 PM, William A. Rowe Jr. wrote: On 10/29/2010 7:47 PM, admin wrote: WTF is T_PAAMAYIM_NEKUDOTAYIM? This has to be THE most asked question by new php developers when they come across it. Can we please change the token name to T_DOUBLE_COLON so I don't have to hear about it constantly? Those that disagree don't do enough PHP support to know how often it is asked. it's worth it. Is it that hard to at least review the mailing list archives before ranting? At least posters would sound like they have educated themselves on why what came to be, and argue sensibly for changes. obviously the old arguments didn't work, time to start anew. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
