Bug #80200 [Com]: On reply to nikic on https://bugs.php.net/bug.php?id=80199
| From: | rtrtrtrtrt at dfdfdfdf dot dfd | Date: | Wed, 07 Oct 2020 23:55:23 +0000 |
| Subject: | Bug #80200 [Com]: On reply to nikic on https://bugs.php.net/bug.php?id=80199 | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-229468@lists.php.net to get a copy of this message | ||
Edit report at https://bugs.php.net/bug.php?id=80200&edit=1
ID: 80200
Comment by: rtrtrtrtrt at dfdfdfdf dot dfd
Reported by: gilperon at gmail dot com
Summary: On reply to nikic on
https://bugs.php.net/bug.php?id=80199
Status: Not a bug
Type: Bug
Package: *General Issues
Operating System: all
PHP Version: 7.4.11
Block user comment: N
Private report: N
New Comment:
gilperon at gmail dot com: you don't get it!
most of the developers are not paid, that's it, no tmore and not less
compared to other programming languages PHP has envolvd a lot in the past few years *without*
breaking changes, period
Previous Comments:
------------------------------------------------------------------------
[2020-10-07 23:51:06] gilperon at gmail dot com
@girgias@php.net I couldnt care less for people that fork PHP and do it as a hobby. What I do as my
hobby is not your business, and what you do on your spare time, is not my business. I will not be
glad to you that your hobby is A, B or C. As I dont expect at all that you will be glad if my hobby
is forking PHP and solving bugs.
I dont know if you have any idea of what is a hobby, but generally a hobby is something where you
put your time, effort, money... into and expect nothing but happines, inner peace... If you expect
money from a hobby, it's a job. If you expect people praising your name, thanking you for your
hobby, it's not a job, it's selfishness and peacockery.
------------------------------------------------------------------------
[2020-10-07 23:41:54] girgias@php.net
And most people who work on PHP do this actually as a hobby and do not get paid.
So the minimum is to be polite.
------------------------------------------------------------------------
[2020-10-07 19:27:08] gilperon at gmail dot com
nikic@php.net I am sorry for my behaviour but I was pissed of because most of the times I report
something here, I really waste my time. And I work for living, not for hobby. When I come here to
report a bug, I am donating some of my time trying to help the community - I will not get anything
from the bug being fixed or not because I always need a solution immediatly, so I always end up
having to find a workaround the bug.
Just as a side not: I reported this bug on SO at https://stackoverflow.com/questions/64249929/why-using-eval-will-not-release-memory-later-when-using-unset-on-anonymous-f
and a guy name NIGEL REN gave me a nice solution! Instead of evaluating the function code I should
put it inside a file and
require the file.
Amazingly enough, he, me and other guy on that thread realized that PHP does not clear it's
memory footprint on files included/required! That's a pretty big problem, I abuse" the
use of require in lots of my projects and I never knew that using require/include would
not clear RAM! That's pretty terrible and explains a lot why most of the cloud servers I manage
use so much RAM because I use a TON require to keep our codebase organized.
------------------------------------------------------------------------
[2020-10-07 18:38:01] nikic@php.net
Marking your report as a duplicate does not mean that it will not be addressed, only that there is
an existing report tracking this issue already. Having multiple open bugs for the same root cause is
counter-productive, as information gets spread out.
Unfortunately the issue in question is simply not easy to fix. My last attempt at it was https://github.com/php/php-src/pull/5595, which
would address your particular case of eval'd closures, but does not fully generalize to the
case of anonymous classes.
------------------------------------------------------------------------
[2020-10-07 18:35:09] great at gmail dot com
Great!
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
https://bugs.php.net/bug.php?id=80200
--
Edit this bug report at https://bugs.php.net/bug.php?id=80200&edit=1