On 1/25/2017 3:52 AM, Michael Wallner wrote:
Hi, I've updated the bug: https://bugs.php.net/bug.php?id=73493
TL;DR
The c-client lib performs a lot of caching; use imap_gc() to clean those
caches from time to time.
Ok, great. Will give that a try.
--
PHP Internals - PHP Runtime Development M
On 1/23/2017 2:45 PM, Michael Wallner wrote:
Just assigned that to me, I'll try to come to it the next few days.
Great, thanks!
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hey guys,
I filed bug 73493 [1] a couple months ago and there's no triage or
visible activity yet. Was hoping to get an update if possible.
I'm forced to download any large INBOX in batches with imap_close() &
imap_open() gymnastics to avoid chewing through 2GB+ of RAM.
thanks!
[1] https:/
On 12/30/2014 2:26 AM, Stanislav Malyshev wrote:
I still haven't achieved a proper understanding of what 5.7 would
actually include (so far the only real BC thing mentioned that it can
warn about is the switch thing, and IMHO making the new minor just
because of that makes little sense, of cours
relies on
this misbehavior. My argument is 'negligible', others say it's
'non-negligible'. And the whole comedy is, no one can actually provide
definitive numbers since nobody will ever know but a tiny portion of all
source code that is out there, so all arguments stem from
e is obviously no way of *ever* asserting that
something is ripe for removal or even deprecation. So this burden of
proof is unmeetable by definition.
--
Leon Sorokin
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
c point of view, but the logic
would be broken from a required-output point of view relative to how it
was operating previously, regardless of whether it was understood or not
when it was written.
--
Leon Sorokin
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit
release. Oddly, 5.4 is a good example of a much larger
incompatibility changelog than the provisional one for 7.0:
http://php.net/manual/en/migration54.incompatible.php
--
Leon Sorokin
On 12/14/2014 6:01 AM, George Bond wrote:
On 14 December 2014 at 08:24, Leon Sorokin wrote:
On 12/14/2014 12:51
re cases where a large
switch/case results in more readable if-elseif chains, long conditional
assignment chains can serve the same purpose, granted you space them
appropriately. I would even go as far as saying that with proper
spacing, they are more readable than the 'if' or 'case
elism via Github issues if such cases are found so they
can be fixed with a 1-year notice.
It's short responses like this and the continued reliance on arguments
posed in a different era/landscape that compel me to reconsider my
continued participation in the PHP community at all.
cheers,
--
change seems like the only time to get this done in PHP.
[1] https://bugs.php.net/bug.php?id=61915
[2] https://wiki.php.net/rfc/isset_ternary
[3] http://news.php.net/php.internals/79584
thanks,
--
Leon Sorokin
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http
11 matches
Mail list logo