---
> The expected result is the bloc inside the case ($id ===0) is processed.
>
> Actual result:
> ------
> The actual result that it is passed for another case.
>
>
>
>
>
>
> --
> Edit this bug report at https://bugs.php.net/bug.php?id=77845=1
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
> --
regards,
Kalle Sommer Nielsen
ka...@php.net
Den fre. 22. mar. 2019 kl. 15.26 skrev Kalle Sommer Nielsen :
> https://wiki.php.net/rfc/deprecate-and-remove-ext-interbase
Given the feedback, the RFC only targets the ext/interbase extension
to be bundled and moved to PECL.
Behind the scenes, the german firebird community has reached out to
his RFC I recently posted regarding this subject (and the
relevant internals thread):
https://wiki.php.net/rfc/deprecate-and-remove-ext-interbase
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
oting addon for dokuwiki to
have such an option for primary voting polls.
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hi all
Den fre. 22. mar. 2019 kl. 15.26 skrev Kalle Sommer Nielsen :
>
> G'day internals
>
> I'd like to start the discussion for the future of the ext/interbase
> extension:
> https://wiki.php.net/rfc/deprecate-and-remove-ext-interbase
I have updated the RFC to contain
s
preferable, similar to ext/wddx.
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Den søn. 24. mar. 2019 kl. 10.05 skrev Lester Caine :
>
> On 24/03/2019 01:42, Kalle Sommer Nielsen wrote:
> > Besides this, it has further magic behavior if the multiple
> > connections are created with the same credentials as one in the same
> > process, I'm n
Den søn. 24. mar. 2019 kl. 03.11 skrev Lester Caine :
>
> (Neely forgot to fix reply address!)
>
> On 24/03/2019 00:22, Kalle Sommer Nielsen wrote:
> > mysql_connect('localhost', 'user', 'password');
> > mysql_select_db('test'); // The last created connection is im
problems ...
I count 13 open bugs[1] in regards to ext/interbase thats been
reported, there are probably a ton more. Bug#74946 talks about a crash
with a type, leading me to believe that if one type can crash, then
more are very likely too.
[1]
https://bugs.php.net/search.php?cmd=display_type=All
s as
extensions in the Core has. Sources and binaries are still available
with the PECL interface.
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
ot work does not go down well!
Again this is NOT relevant to the thousands of people you are
literally spamming. This stuff belongs on Twitter, your blog or some
other kind of social media, it is NOT relevant to the development of
the PHP runtime, so keep this off the list.
--
regards,
Kalle Somm
lør. 23. mar. 2019 kl. 15.22 skrev Lester Caine :
> On 23/03/2019 12:46, Kalle Sommer Nielsen wrote:
> >> Now to get back to working out why Nikita's patch does not work in
> >> 7.2.16 ...
> > Obviously because the patch was made for PHP 7.3. Hint: If a
> > macro
nts in favor. Take the rest of the evening off the
computer if you cannot handle the reality and issues that is present here
in the ext/interbase debate.
--
regards,
Kalle Sommer Nielsen
ka...@php.net
is
implemented in 7.3 and migrate it or see how other functions who do
similar functionality works and port it.
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
have done was to reply to either me or
Dan in the RFC thread with a one liner: "I mean 'We' as in X", that
would have been it.
Please! Keep these history lessons to your personal blog instead of
internals when there is zero relevance to the topic in question.
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
a repository at PECL, however it is
unlike to retrieve further improvements or fixes from there unless
someone actually steps up to take over it.
We have done what we can to try call for help to keep this extension
for as long as possible, but we can only do so much for so long.
--
regards,
Kall
will put this
into voting on Monday 8th of April, noon EET (which is a good two and
a half weeks away). The intended voting period is set for 2 weeks,
meaning if voting proceeds, the pools will be closed around Monday
22th of April, noon EET.
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP
5533269c8af96c
> >
> > Log:
> > Fixed bug #75113: Added DatePeriod::getRecurrences() method.
>
> Why is new functionality added to PHP 7.2 and PHP 7.3?
Seconded, it should follow the same path as other functionality. We
did not merge the crc32c below 7.4 because of these are r
ixer, right?
> 4. Even if we deprecate `{}`, I don't think we'd be in any hurry to
> remove it, though with an automatic fixer this seems doable, if we
> care to do it at all.
The thing is, I just don't understand the rationale to remove this
feature, what the full gain from doing so is?
aning in different PHP version.
For me personally it is a huge -1, if anything I would like the
string[] syntax decoupled.
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
eneral response to that line of thinking.
I like the feature as it is, and if the syntax is right for it then I
would most likely vote for it if it comes to that state.
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
the purpose of short circuited generators and I might as well just
write it the more verbose way.
I like the idea, just not the syntax because it has the potential
(along with short closures) to be annoying to read in the long run.
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Interna
re important, which I believe too, is the reason for the expression
for using foreach in this context comes from (not only from my PoV).
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Den ons. 6. mar. 2019 kl. 11.03 skrev Nikita Popov :
>
> On Wed, Mar 6, 2019 at 6:20 AM Sebastian Bergmann wrote:
>
> > Am 06.03.2019 um 01:18 schrieb Gabriel Caruso:
> > > I'd like to suggest Peter Kokot for this role.
> >
> > Seconded.
> >
>
> T
before that, that I can remember.
I suggest the OP to start such a process, which can be done by
registering a user on our wiki and following the instructions for
write access to the RFC namespace.
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mai
quot;name" => 'Tom'],
["id" => 2, "name" => 'Fred'],
];
foreach ($data as ["id" => $id, "name" => $name]) {
echo "id: $id, name: $name\n";
}
Having something like:
foreach ($data as (int) ["id" => $id, "
out it as introducing a new keyword is not very
suitable imo.
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Den tir. 5. feb. 2019 kl. 02.22 skrev Kalle Sommer Nielsen :
> I agree with that as long as it is without the PHP Project boundaries,
s/without/within
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: h
by reading parts of this RFC
it does sound like Zeev indeed did build on this. With the 3 current
threads we have going, despite a bit confusing, I do think we have
started to open up the can of worms that is our RFC process and slowly
work our way to see what we can do to improve that.
--
rega
voting power. The
PHP community is large, exceptionally large and while I wish there
were ways was more open for developers to join the "conversation", I
do not see how we can start tackling that, which itself is perhaps a
topic for another thread on its own.
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
t how we deal with things like this.
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
years this year, while the internals is no longer the "closed
gentle mans club" as it was when I joined 11 years ago, it still is
quite distinct from other OSS projects and one of the reasons why I
personally stick around, as I like that spirit the project has, which
is why I'm very protectiv
ng it its own log
file that doesn't grow nearly as much seems like a bad way to solve
this.
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
d, that group is given a single vote. A committee
> can be put together that is in charge of addressing the applications.
Please no committee or more bureaucracy as it just makes everything so
much more political and complicated for no satisfying reason.
--
regards,
Kalle Sommer Nielsen
ka..
e
> can condition the inclusion of JIT based on having it. Let's first agree on
> whether we want it in the first place.
Agreed. Naturally I would contribute in what I can to work on those
parts (Windows).
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
is a must there, imho).
>
> I don't see any problems with including JIT without Windows support.
> Windows runs PHP much slower any way.
Without my usual Windows bias, I do believe it is a considerable fact
like Nikita pointed out as Windows is a first class citizen in terms
of operati
hing else,
> as there are a lot of good ideas in this RFC.
While that makes sense, I do believe it should be sorted at the same
time. This can be solved by secondary votes on how to approach it
within the RFC.
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime
the minor versions of 8 once a year when its the most
logical reason to go to 8.1 from 8.0, and so on until we reach the
point where the next major is considerable.
I think changes like the requiring a patch for RFCs is a very welcomed addition.
--
regards,
Kalle Sommer Nielsen
ka...@php.net
stead of blocking?
I re-opened the issue. As a note, please keep issues like this to the
webmaster list as internals is purely language development.
Thank you!
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
ensitive.
>
> I'm definitely in favor of making float to string casts locale-independent
> in PHP 8.
I'm in the same boat here. I remember we had some interesting
behaviorial differences on a language level too[1] (which seems to
also have maybe resurfaced after reading the newest comments).
[
outweight the unmaintained
library, but its really something that should be discussed for a
future release.
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
ot;trim" in the example given, and if thats all the same, I can
see that many things not utilizing this could be slower for no good
reason (at least in my honest opinion). However I don't know if there
is something sneaky we can do here.
--
regards,
Kalle Sommer Nielsen
ka...@p
ontexts, like in C to avoid the quotation,
however it clashes with constants. A hack you can do in userland could
be something like:
const trim = 'trim';
array_filter($names, trim);
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubs
fail closed and never
> returning false.
> 2) Deprecate the usage of the second pass-by-reference parameter and
> remove in PHP 8.0. Until then, it always sets the value to true.
>
> Do you think this kind of change would warrant an RFC?
It would.
--
regards,
Kalle Sommer Nielsen
ka
ave been a trend in that direction in the
past year or so and I think its way overdue that we begin to remove
crufts like that.
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Greetings hackers
I'm happy to announce that the RFC "Always available hash extension"
have been accepted with a 30-0 vote.
I apologies for the initial poorly written date in the voting
announcement email. Thank you all for voting!
--
regards,
Kalle Sommer Nielsen
ka...@php.ne
weeks from today (and close on 19/09-2018
around noon UTC+1). Since this change impacts a larger set of PHP
itself, the vote required for this to pass is 2/3.
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http
/ext/pdo_sqlite/config.m4#L55-L58>
I don't think there is any paticular reason for bundling it anymore,
at least not from the Windows side of things where we should be easily
able to adapt the build system to link to it instead of building the
bundled version. (Anatol cc'ed)
--
regards,
Kal
n
> seems to be duplicated). We should also have a look at crypt_sha256.c
> and crypt_sha512.c (of ext/standard) which likely duplicate some code
> already available in ext/hash.
Those makes a lot of sense to do, and definitely something we should
if this RFC passes
--
regards,
Kalle Sommer Nie
RFC.
[1] https://wiki.php.net/rfc/permanent_hash_ext
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
for PEAR in paticular, but it seems odd for us
to still rely on something that seems essentially dead.
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
endsOfPHP/pickle
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
;: die() when !$connected;
>
> It seems more clear than $connected or die().
I in fact find that more unreadable as you first got to dig through
the error handling before you actually get to the logic that triggered
it.
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals
to it
to support: "do() or throw new Exception(...);", tho its just a code
style over: "if(!do()){ throw new Exception(...); }"
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
ave a branch to support for years to come as to our current
release policy.
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
SION anyway
(thanks to Peter K.) and the information is still available with echo
(new ReflectionExtension('extensionname'))->getVersion(); and I doubt
there is a massive usage so the impact is very minimal and therefore I
believe its a fair compromise.
--
regards,
Kalle Sommer Nielsen
ka...@php.
Typed Properties RFC as apart of
the next series of PHP personally. On the bright side, it does allow
us more time for a potential PHP8.
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
we should all be
good at that department. I will take care of updating the portion of
the 7.4 RFC to mention this new addition.
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
vember/early December is the way
to go about this.
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Den tor. 5. jul. 2018 kl. 22.51 skrev Kalle Sommer Nielsen :
>
> Den tor. 5. jul. 2018 kl. 22.46 skrev Nikita Popov :
> > Sounds reasonable to me. My only question would be when we would start
> > emitting the deprecation notice. I'm not a fan of deprecating things in the
all I think its a much cleaner migration path
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
e is much better as it doesn't really hurt. We could add
an alias constant instead and provoke an E_DEPRECATED if the old one
is used (given we don't give the filter the same numeric value).
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
t;continue" usage also. This would be a bug most
> likely.)
>
> Then there wouldn't be compatibility issue anymore.
I like the idea of a tool for such, but I think its better to
implement it in some of the static analyzer projects like PHPStan and
the like to catch these.
--
regard
thing larger or controversial in this RFC though.
I took the liberty and added the FILTER_SANITIZE_MAGIC_QUOTES to the
RFC so we may once and for all get rid of magic_quotes.
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe,
mimics the same behavior as pdo_odbc does,
but then again the IBM folks have not been the fastest to update their
extensions, so maybe there there is a new way to do it now but I doubt
it. I don't really have the interest to dig too much into it either.
--
regards,
Kalle Sommer Nielsen
ka..
adding your name as the RFC author.
[1] https://wiki.php.net/rfc/deprecations_php_7_4
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
uce the relevant patches should it be needed
for most of these things.
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
y object.
I agree with the objection, however they are also a major selling
point for a major version which I think is something worth keeping in
mind.
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
tions on how to proceed here?
If thats the case that its basically identical, then a PHP_DEP_FE
should be sufficient for image2wbmp() and a removal in future version,
given its a rarely used function and migration is easy, even 7.4 could
potentially be fine for removal.
--
regards,
Kalle Somme
stoph
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
n people from there too?
Sadly we do not as far as I'm aware of, the best thing we could do is
to add rhsoft or similar to the spam keywords, but even that is easily
bypassable.
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To u
ng?
This comes from the Zend/zend_language_parser.y file in its generated
form, the yyparse name is set to zendparse (through #define yyparse
zendparse)
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
about PHP,
> and we strive for backward compatibility when at all possible. And there
> is no direct gain/need to remove this feature.
>
> Eli
Same thoughts here, -1 on deprecation. I prefer to use backticks over
shell_exec() when writing code that does something simple.
--
regards,
K
On 26 Jan 2018 21.02 <20%2018%2021%2002>, "Anatol Belski"
wrote:
Hi,
> -Original Message-
> From: Thomas Punt [mailto:tp...@hotmail.co.uk]
> Sent: Thursday, January 25, 2018 11:41 PM
> To: PHP internals list
> Subject: [PHP-DEV] Requesting php-src
23)
> 24)
> ...
> ===
> This is output by c
> function:"socket_recvmsg"(/home/work/php/php/ext/sockets/sendrecvmsg.c:214),
You can find the implementation of socket_recvmsg() in the ext/sockets
directory here:
http://git.php.net/?p=php-src.git;a=blob;f=e
admins or someone with
karma to the box, usually this has been restricted to RMs, PHP Group
members and a select few. I'm not sure of the policy anymore for
joining this list.
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubs
be supporting our use of PHP and extensions for a
> while.
>
> %s/world/word/
>
> is the very small change I found so far on that page.
Thanks, fixed!
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
annoying thing to begin the new year with,
that these just can't stop even after a few mails by other readers.
I'm cc'ing Rasmus as I can't think of anyone besides Derick that has
karma to make it happen.
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Developm
existing code.
> I remember a number of cases where I used instanceof on possibly
> non-objects.
>
> if ($x instanceof C) {
> return $x;
> }
> elseif ($x === NULL) {
> ...
> }
>
> All such code would then produce warnings.
>
>
> On 9 December 2017 at 07:35,
Hi
We should just add a warning to the first example, it seems like an
oversight that it was left silent
On 9 Dec 2017 07.29, "Andreas Hennings" wrote:
> The following (https://3v4l.org/A2Tp6) is ok, it simply returns false:
>
> $x = 1;
> $x instanceof \stdClass;
>
SodiumException
> is now an E_ERROR.
>
> I hope we can restore some sanity to this world by reverting that revert...
All in all, E_ERROR should *never* be used by an extension, we should
revert back to using an Exception and re-tag the 7.2.0 release asap
--
regards,
Kalle Sommer Nielse
ctively using the exif extension? Probably
not.
[1] https://gist.github.com/KalleZ/c7ba4f78314c989e27710e4fa14e2f3e
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
is fine with
me, tho I generally tend to use tabs unless the test I copy/pasted had
spaces, I would follow that.
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
n_by=id
[2] https://bugs.php.net/bug.php?id=12802
[3] https://bugs.php.net/random
[4] https://bugs.php.net/search.php?cmd=display=USERNAME
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
ster...rfc-trailing-comma-function-calls#diff-88d4f8d1ae810e0722bf59cf1a739228
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
+1, only note I have is that with the change to config.m4, a relevant
one should maybe also follow for phpize on Windows for config.w32
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
ing to do the work, and work together with the
maintainer of Imagick, then I don't see any showstoppers for why it
can't be included in the php-src through an RFC much like Sodium
recently was added to 7.2
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mai
On 11 Aug 2017 15.38, "Remi Collet" wrote:
Le 11/08/2017 à 15:15, Nikita Popov a écrit :
> I'm wondering if it might be time to remove (i.e. deprecate and move to
> PECL) the wddx extension?
+1
+2
T
> to cover non-release parts of the RM role (such as keeping an eye on
> out-sized files and that people observe merging process, etc...)
I committed some changes which should reduce the exif tests by a
larger margin in a7484beea2711c28f548d4c4e7cc10c5271b7890, I think
this will help make
I'd like to see that gone.
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
ly, writing to them seems more like a hack anyway and should be
avoided
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
support with ODBC, and all
of them had releases within the last few years so I consider them
still supported.
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
e which have a phpinfo()
page[1], and yes bugs.php.net does have pdo_mysql
[1] https://bugs.php.net/admin/?action=phpinfo
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
ng, it's fine" makes it really hard to
> find motivation to contribute anything.
I'm not saying don't change its fine, what I'm saying is that we
shouldn't change the overall arching of the website to be bloated.
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runt
s to implement functionality that
returns records based on criteria, we need that functionality in
multiple places anyway.
I always saw the PHP project as an example to how powerful the
language is by its own, out of the box and I will continue to advocate
for us to continue that way
--
regards,
Kal
s and
> globals. Is this something I can land in PHP-7.2, or is it closed to
> extension ABI changes?
afair ABI can be broken until a branch/release hits RC, after that its
on case by case basis
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Dev
levant links to windows.php.net mirroring, as I can
easily agree with the size amount that the Windows binaries do contain
with all these flavors we produce nowadays.
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http:/
from and in the end you
just want to contribute, you will still continue to push a new bug
tracker though. I wouldn't mind joining in on this as a now senior
contributor for PHP.
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Having to maintain the same
resource in 3 places is odd too, INSTALL, win32/install.txt,
phpdoc/en/install/?
TL;DR if no one really objects, I will turn these into links over the
course of the weekend
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Developmen
uncharged from the days of PHP4.
--
regards,
Kalle Sommer Nielsen
ka...@php.net
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
101 - 200 of 610 matches
Mail list logo