Am 01.01.2018 um 10:21 schrieb Tony Marston:
Any attempt to make typehinting (or type enforcement as it has now
become) is simply adding complications to the language which do not
provide benefits to the greater PHP community, just a minority of poor
coders who want the language to trap the b
Am 31.12.2017 um 11:27 schrieb Tony Marston:
"Michael Morris" wrote in message
news:CAEUnE0e67q2HMX8bmFjy5Mx8GMfxD=dnbswf9csuyntyn8x...@mail.gmail.com...
On Sat, Dec 30, 2017 at 5:37 AM, Lester Caine wrote:
Not being able to vote, many of us have no option to complain about the
way thing
Am 31.12.2017 um 11:24 schrieb Tony Marston:
Some of us are clever enough to write code that doesn't have those types
of bug in the first place. I developed my framework in PHP4 before type
hints even existed, and I developed a large enterprise application with
that framework which is now bei
Am 30.12.2017 um 22:55 schrieb Michael Morris:
On Sat, Dec 30, 2017 at 5:37 AM, Lester Caine wrote:
Not being able to vote, many of us have no option to complain about the
way things are going. Currently there seems to be several styles of PHP
form the nice and simple untyped version I move
Am 30.12.2017 um 18:15 schrieb Sebastian Bergmann:
Am 29.12.2017 um 18:30 schrieb li...@rhsoft.net:
"i don't see a benefit, i don't like it" are no valid reasons to do so
I strongly disagree. If a majority of people do not see the benefit of a
syntax change then the
Am 30.12.2017 um 11:37 schrieb Lester Caine:
On 30/12/17 09:16, Tony Marston wrote:
You are missing the point. If an RFC is so badly written that someone
does not understand it, or understand what benefits it is supposed to
provide, then there is no point in up-voting it
if i don't undrstand
Am 30.12.2017 um 10:16 schrieb Tony Marston:
wrote in message news:f48976dd-589f-e88e-37ba-38096c3a3...@rhsoft.net...
You are missing the point. If an RFC is so badly written that someone
does not understand it, or understand what benefits it is supposed to
provide, then there is no point in
Am 29.12.2017 um 18:29 schrieb Markus Fischer:
On 26.12.17 16:56, Sebastian Bergmann wrote:
Am 26.12.2017 um 16:46 schrieb li...@rhsoft.net:
would you mind to explain this?
"Foo|Bar", "array|string", etc. (still) make no sense to me.
"scalar" makes sense to
Am 29.12.2017 um 18:24 schrieb Fleshgrinder:
On 12/29/2017 6:21 PM, li...@rhsoft.net wrote:
no, when i accept "int|float" i don't get something converted at all and
i can handle the cases different - when it#s silently casted to a float
i have no way to know it was a int at cal
Am 29.12.2017 um 18:13 schrieb Fleshgrinder:
Why exactly is it necessary to support weak mode together with unions
and intersections? It is obviously unclear in many situations what
should happen, so why not simply bail like in strict mode?
is also a good enough way to handle it now as we hav
Am 29.12.2017 um 18:18 schrieb Fleshgrinder:
On 12/29/2017 4:09 PM, li...@rhsoft.net wrote:
Am 29.12.2017 um 13:08 schrieb Fleshgrinder:
What is the use case for `int|float`? I mean, if f is able to process a
`float` than f is able to process an `int` and since `int` is already
automatically
Am 29.12.2017 um 16:37 schrieb Nikita Popov:
Regarding the union type RFCs, from what I remember, one of my personal
issues with it were the complex rules involving scalar type unions in weak
typing mode. It's non-trivial to decide what a value should be casted to if
it does not have the correc
Am 29.12.2017 um 13:08 schrieb Fleshgrinder:
What is the use case for `int|float`? I mean, if f is able to process a
`float` than f is able to process an `int` and since `int` is already
automatically changed to a `float`, well, you're done
just read the mass of bugreports caused by float answ
Am 29.12.2017 um 09:04 schrieb Tony Marston:
wrote in message news:4b55eed1-8656-ff70-e4e9-ad5e40213...@rhsoft.net...
Am 29.12.2017 um 00:21 schrieb Larry Garfield:
Correct. Union types I've always seen presented as offering both
union and
intersection. There are cases where union is great
Am 29.12.2017 um 00:21 schrieb Larry Garfield:
Correct. Union types I've always seen presented as offering both union and
intersection. There are cases where union is great, and where it's kinda
silly. There are cases where intersect is great, and where it's kinda silly.
Most of the anti- a
Am 26.12.2017 um 20:15 schrieb Sara Golemon:
On Tue, Dec 26, 2017 at 10:56 AM, Sebastian Bergmann wrote:
Am 26.12.2017 um 16:46 schrieb li...@rhsoft.net:
would you mind to explain this?
"Foo|Bar", "array|string", etc. (still) make no sense to me.
"scalar" ma
Am 26.12.2017 um 19:18 schrieb Larry Garfield:
On Tuesday, December 26, 2017 9:56:21 AM CST Sebastian Bergmann wrote:
Am 26.12.2017 um 16:46 schrieb li...@rhsoft.net:
would you mind to explain this?
"Foo|Bar", "array|string", etc. (still) make no sense to me.
"
Am 26.12.2017 um 16:56 schrieb Sebastian Bergmann:
Am 26.12.2017 um 16:46 schrieb li...@rhsoft.net:
would you mind to explain this?
"Foo|Bar", "array|string", etc. (still) make no sense to me.
"scalar" makes sense to me although it is but an alias for
"
Am 26.12.2017 um 14:38 schrieb Sebastian Bergmann:
Thank you, Richard, for working on this.
I spent a lot of time this year introducing scalar type declarations into
existing code bases. In quite a few cases I was not able to do so because
the existing code works with parameters that can be of
Am 20.12.2017 um 13:56 schrieb Sebastian Bergmann:
On 12/19/2017 04:34 AM, Michael Moravec wrote:
I'd like to propose and discuss Mixed Typehint RFC for PHP 7.3:
https://wiki.php.net/rfc/mixed-typehint
"mixed" is too unspecific. I understand the reasoning behind wanting
"mixed": to express
Am 19.12.2017 um 21:53 schrieb Fleshgrinder:
On 12/19/2017 8:01 PM, li...@rhsoft.net wrote:
but that's a different thing and both don't collide
It's not a different thing, that's what I try to tell you. They do not
collide, of course not, but having the others is going t
Am 19.12.2017 um 19:19 schrieb Fleshgrinder:
On 12/19/2017 6:43 PM, Andreas Hennings wrote:
The argument, which I support, is that "mixed" would allow to
distinguish against cases of "developer forgot to add a type hint" or
"no type hint due to legacy / BC reasons".
Also, with a "mixed" type h
Am 19.12.2017 um 18:30 schrieb Levi Morrison:
In any case we are straying off-topic: this thread is about `mixed`
which I would vote against. As our type-system stands it provides
almost no value. If our type system ever changes and it suddenly
provides value then it should be proposed at that
Am 19.12.2017 um 04:44 schrieb Michael Morris:
On Mon, Dec 18, 2017 at 10:34 PM, Michael Moravec
wrote:
Hello internals,
I'd like to propose and discuss Mixed Typehint RFC for PHP 7.3:
https://wiki.php.net/rfc/mixed-typehint
The purpose of this RFC is to introduce "mixed" typehint on langu
Am 08.12.2017 um 18:55 schrieb Stephen Reay:
On 8 Dec 2017, at 5:16 pm, li...@rhsoft.net <mailto:li...@rhsoft.net>
wrote:
"Now expressing the same thing in two different ways, with or without
& is confusing, so I think one needs to think about if old syntax
should be de
Am 08.12.2017 um 17:36 schrieb CHU Zhaowei:
On Fri, Dec 8, 2017 06:16 PM, "li...@rhsoft.net" wrote:
>
>and it's much bader to use a not so long existed syntax which was now
>changed to a fatal error - just type "php call-by-reference" in google
>
I kn
Am 08.12.2017 um 05:41 schrieb Stephen Reay:
On 8 Dec 2017, at 08:54, "li...@rhsoft.net" wrote:
Am 08.12.2017 um 01:38 schrieb Björn Larsson:
Den 2017-12-06 kl. 20:49, skrev Nikita Popov:
Hi internals,
I'd like propose optional support for explicitly marking by-ref
Am 08.12.2017 um 01:38 schrieb Björn Larsson:
Den 2017-12-06 kl. 20:49, skrev Nikita Popov:
Hi internals,
I'd like propose optional support for explicitly marking by-reference
argument passing at the call-site, in addition to the declaration-site:
https://wiki.php.net/rfc/explicit_send
Am 06.12.2017 um 20:49 schrieb Nikita Popov:
I'd like propose optional support for explicitly marking by-reference
argument passing at the call-site, in addition to the declaration-site:
https://wiki.php.net/rfc/explicit_send_by_ref
In short, while currently we have
function byRef(&
Am 05.12.2017 um 17:45 schrieb Walter Parker:
Lists, I give you the same advice. I know and use SSL Labs, I been a
subscriber to Ivan's mailing list for years. Older versions of Openssl
had a default list of +ALL, -aNULL, -eNULL as the default list of
ciphers
yes
Before DES was removed in
Am 05.12.2017 um 06:52 schrieb Walter Parker:
On Mon, Dec 4, 2017 at 6:27 PM, li...@rhsoft.net
<mailto:li...@rhsoft.net> mailto:li...@rhsoft.net>>
wrote:
Am 05.12.2017 um 01:19 schrieb Walter Parker:
Oh, I see, this not about the actual change (the protocol
Am 05.12.2017 um 01:19 schrieb Walter Parker:
Oh, I see, this not about the actual change (the protocol version). This
is about when using PHP on the client side, it does not support
all/enough of the modern cipher suite list.
Now that we have identified the problem in question, this should
Am 04.12.2017 um 22:53 schrieb Walter Parker:
On Mon, Dec 4, 2017 at 1:43 PM, Niklas Keller wrote:
and to be clear here:
a client when connecting to a server configured like below has to respect
the cipher order of the server while
https://www.ssllabs.com/ssltest/ exists for years to give dm
-AES256-SHA256:DHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA:AES256-SHA
Am 04.12.2017 um 19:18 schrieb li...@rhsoft.net:
Am 04.12.2017 um 18:36 schrieb Sara Golemon:
On Fri, Dec 1, 2017 at 6:35 PM, li...@rhsoft.net
wrote:
the main question is why does PHP
Am 04.12.2017 um 18:36 schrieb Sara Golemon:
On Fri, Dec 1, 2017 at 6:35 PM, li...@rhsoft.net wrote:
the main question is why does PHP need to to *anything* here instead hand
the TLS handshake completly over to openssl? in that case even PHP5 could
perfer TLS1.2 ciphers against a sevrer that
Am 02.12.2017 um 02:08 schrieb Walter Parker:
Lists, I fail to see how Sara was wrong and you are right.
In the old PHP, it was TLS 1.0
bad enough
In the new PHP. it is TLS 1.2, TLS1.1, TLS1.3
you surely meant 1.0 instead 1.3 here
When TLS1.3 comes out, old PHP will use only TLS1.0. <-
Am 01.12.2017 um 22:49 schrieb Sara Golemon:
On Fri, Dec 1, 2017 at 11:52 AM, li...@rhsoft.net wrote:
yes and since nobody ever sould override the defaults in application code
for obvious reasons that's the problem, you shouldn't mangle with openssl
defaults in general and let open
Am 01.12.2017 um 17:44 schrieb Niklas Keller:
li...@rhsoft.net <mailto:li...@rhsoft.net> <mailto:li...@rhsoft.net>> schrieb am Fr., 1. Dez. 2017, 17:13:
Am 30.11.2017 um 17:41 schrieb Hannes Magnusson:
>> - Improve TLS constants to sane values
>
Am 30.11.2017 um 17:41 schrieb Hannes Magnusson:
- Improve TLS constants to sane values
This worries me a lot. Last time someone thought it was a good idea they
introduced security vulnerability for all apps that used them.
that PHP now instead of ECDHE-RSA-AES128-SHA uses
ECDHE-RSA-AES128
Am 29.11.2017 um 15:37 schrieb Johannes Schlüter:
On Mi, 2017-11-29 at 12:09 +0100, Jan Ehrhardt wrote:
FWIW: I am using the zip's at github, like
https://github.com/php/php-src/archive/php-7.2.0.zip
Contrary to "official" release tarballs those don't contain generated
parsers etc. thus behav
Am 12.11.2017 um 19:25 schrieb Rowan Collins:
On 12/11/2017 09:49, Fleshgrinder wrote:
There is one thing that differs for the const
and the field: a const value must be known at compile time, whereas a
field value does not. An important difference!
class A { abstract public const FOO: in
Am 12.11.2017 um 10:50 schrieb Alice Wonder:
On 11/12/2017 01:38 AM, Tony Marston wrote:
Just because some languages use a corrupt definition of "constant" is no
reason for PHP to do the same. A constant has a value which, once
defined, cannot be changed. It is not logical to define a constant
Am 08.11.2017 um 13:36 schrieb Michael Kliewe:
Am 08.11.2017 um 13:27 schrieb li...@rhsoft.net:
Am 08.11.2017 um 12:59 schrieb Michael Kliewe:
The PHP mailing list software is not configured DMARC compliant. DMARC
means, either SPF or DKIM has to be valid. The PHP mailing list changes
the
Am 08.11.2017 um 12:59 schrieb Michael Kliewe:
The PHP mailing list software is not configured DMARC compliant. DMARC
means, either SPF or DKIM has to be valid. The PHP mailing list changes
the Subject (it adds [PHP-]), that's why the DKIM signature breaks.
SPF breaks, because Gmail and oth
Am 07.11.2017 um 12:53 schrieb Tony Marston:
It should also be obvious to every first year student that if a program
contains code that is rarely or never used then carrying around the
"weight" of that code has a detrimental effect
but you don#t get the basics right: you need to measure if t
Am 07.11.2017 um 11:21 schrieb Tony Marston:
wrote in message news:748869f7-13bb-5bdd-6fec-399a33b79...@rhsoft.net...
Everybody knows that carrying around code which is either rarely used
or not used at all is an overhead
everybody knows that claims without measure the impact are worthless
Am 06.11.2017 um 12:09 schrieb Tony Marston:
wrote in message news:55fb932f-7f61-33eb-1fd9-aa425bc6f...@rhsoft.net...
Am 05.11.2017 um 11:24 schrieb Tony Marston:
wrote in message news:d70cc49d-c397-3f09-d08d-b79b31014...@rhsoft.net...
it depends on the implementation and just beause you say
Am 05.11.2017 um 11:24 schrieb Tony Marston:
wrote in message news:d70cc49d-c397-3f09-d08d-b79b31014...@rhsoft.net...
it depends on the implementation and just beause you say so does not
prove anything and even if you need to measure, optimize and make
decisions based on technical facts - wha
Am 04.11.2017 um 10:18 schrieb Tony Marston:
wrote in message news:941fd347-4a17-78b6-1bd7-4a5519aa7...@rhsoft.net...
Am 03.11.2017 um 11:33 schrieb Tony Marston:
wrote in message news:6643d10b-8703-693c-15c2-da338022e...@rhsoft.net...
Am 02.11.2017 um 10:55 schrieb Tony Marston:
"Kalle S
Am 03.11.2017 um 11:33 schrieb Tony Marston:
wrote in message news:6643d10b-8703-693c-15c2-da338022e...@rhsoft.net...
Am 02.11.2017 um 10:55 schrieb Tony Marston:
"Kalle Sommer Nielsen" wrote in message
I fail to see how it offers "negative benefits to the vast number of
programmers who ar
Am 02.11.2017 um 10:55 schrieb Tony Marston:
"Kalle Sommer Nielsen" wrote in message
I fail to see how it offers "negative benefits to the vast number of
programmers who are happy with the language as it currently exists", I
If it's put into the language then it affects 100% of the users, b
Am 27.10.2017 um 12:54 schrieb Niklas Keller:
pleae don't break code like this which is a useful case for access
directly a array field returned from a function and so makes this to
a one-liner without check the result
public function GetMaxSort(): int
{
return (int)my
Am 27.10.2017 um 11:49 schrieb Filippo Tessarotto:
Hi, I would like to propose an RFC to raise an E_NOTICE when a variable
"initialized" to null is casted to other types:
$foo = null;
var_dump($foo['bar']);
var_dump($foo . 'bar');
var_dump($foo + 2);
var_dump($foo & 2);
// At the time being,
Am 25.10.2017 um 21:38 schrieb Aidan Woods:
To throw something else on the heap of things that need fixing in the mail
servers:
I occasionally get emails from the mailing list bot warning I'll be
auto-unsubscribed because messages it is sending to me are are bouncing.
(It sends me back the boun
Am 24.10.2017 um 06:07 schrieb Kalle Sommer Nielsen:
Dear Internals
I have in the past few days been working on, and I continue to work on
cleaning up our bug tracker. We are close to 5000 open bugs[1], while
about 1500 of those are FR requests, some opened as far back as
2001[2]
but why do
Am 12.10.2017 um 17:16 schrieb Johannes Schlüter:
On Do, 2017-10-12 at 14:55 +0300, Reinis Rozitis wrote:
Hello,
is there a reason (technical or historical) why the data coming from
MySQL is always strings?
I've found only one case where the data type is "honored" -
PDO+mysqlnd+emulation off [
Am 12.10.2017 um 14:34 schrieb Reinis Rozitis:
no idea what the state of PDO is
http://blog.ulf-wendel.de/2008/php-new-network-traffic-cpu-and-memory-
savings-with-mysqlnd/
if(mysqli_options($this->conn, MYSQLI_OPT_INT_AND_FLOAT_NATIVE,
Thanks,
as we still partly (forced to) live in th
Am 12.10.2017 um 13:55 schrieb Reinis Rozitis:
is there a reason (technical or historical) why the data coming from MySQL is
always strings?
I've found only one case where the data type is "honored" -
PDO+mysqlnd+emulation off [1]
not entirely true, our database-layer acts directly with mys
Am 10.10.2017 um 18:41 schrieb Niklas Keller:
2017-10-10 17:10 GMT+02:00 li...@rhsoft.net <mailto:li...@rhsoft.net>
mailto:li...@rhsoft.net>>:
Am 10.10.2017 um 16:57 schrieb Christoph M. Becker:
On 10.10.2017 at 15:41, Sebastian Bergmann wrote:
I con
Am 10.10.2017 um 16:57 schrieb Christoph M. Becker:
On 10.10.2017 at 15:41, Sebastian Bergmann wrote:
I consider this a serious bug that leads to unexpected, confusing problems
such as
https://github.com/sebastianbergmann/phpunit/issues/2796#issuecomment-335180273.
I understand Nikita's point
Am 10.10.2017 um 15:41 schrieb Sebastian Bergmann:
https://bugs.php.net/bug.php?id=75345 is about the fact that strict type
declarations are not enforced when a function or method is invoked via the
Reflection API.
There is a pull request that addresses this (as well as
https://bugs.php.net/bu
Am 25.09.2017 um 11:41 schrieb Tony Marston:
The fact that some people write "do_something" or "do_Something" or
"Do_Something" or even "DO_SOMETHING" and it points to a single function
because of case insensitivity does NOT cause a genuine problem - except
in the minds of a few nit-picking,
Am 24.09.2017 um 11:36 schrieb Tony Marston:
wrote in message news:caba6370-7531-7c51-3900-434611d00...@rhsoft.net...
Am 22.09.2017 um 10:21 schrieb Tony Marston:
wrote in message news:064eafcb-e42f-cfeb-76f1-e2c5aec0e...@rhsoft.net...
Am 19.09.2017 um 11:24 schrieb Tony Marston:
If the sing
Am 22.09.2017 um 10:21 schrieb Tony Marston:
wrote in message news:064eafcb-e42f-cfeb-76f1-e2c5aec0e...@rhsoft.net...
Am 19.09.2017 um 11:24 schrieb Tony Marston:
If the single character "ß" represents two "s" characters joined
together, then the uppercase equivalent should also be a single
Am 21.09.2017 um 16:52 schrieb Sara Golemon:
On Thu, Sep 21, 2017 at 10:47 AM, li...@rhsoft.net wrote:
Am 21.09.2017 um 16:36 schrieb Remi Collet:
Le 21/09/2017 à 16:12, li...@rhsoft.net a écrit :
curent 7.1 HEAD - guys sleep() can't replace usleep(1) becaus eit's a
million ti
Am 21.09.2017 um 16:36 schrieb Remi Collet:
Le 21/09/2017 à 16:12, li...@rhsoft.net a écrit :
curent 7.1 HEAD - guys sleep() can't replace usleep(1) becaus eit's a
million times longer
usleep: warning: usleep(1) is deprecated, and will be removed in near
future!!
usleep: warning: u
curent 7.1 HEAD - guys sleep() can't replace usleep(1) becaus eit's a
million times longer
usleep: warning: usleep(1) is deprecated, and will be removed in near
future!!
usleep: warning: use sleep(1) instead...
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: htt
2017, 19:18 +0200, li...@rhsoft.net , wrote:
Am 20.09.2017 um 19:06 schrieb ilija.tov...@me.com:
Hi everybody!
To my surprise, I noticed today that an array access on a `null`
value returns `null` without any warning whatsoever.
Accessing the property of a `null` value gives you a notice,
Am 20.09.2017 um 19:06 schrieb ilija.tov...@me.com:
Hi everybody!
To my surprise, I noticed today that an array access on a `null` value returns
`null` without any warning whatsoever.
Accessing the property of a `null` value gives you a notice, while calling a
function on that `null` value g
Am 20.09.2017 um 11:30 schrieb Tony Marston:
wrote in message news:098adca8-6897-929d-90e4-cc464f0e2...@rhsoft.net...
Am 19.09.2017 um 11:24 schrieb Tony Marston:
If the single character "ß" represents two "s" characters joined
together, then the uppercase equivalent should also be a sing
Am 19.09.2017 um 11:24 schrieb Tony Marston:
If the single character "ß" represents two "s" characters joined
together, then the uppercase equivalent should also be a single
character which looks like two "S" characters joined together. If it is
not possible to write code which deals with th
Am 16.09.2017 um 13:48 schrieb Marco Pivetta:
"then don't use it" worked great for `register_globals` and
`magic_quotes`. Not saying it is the same here, but you really ought to
have a bit of a mentality adjustment
so when it is not the same why do you mention it?
there is a difference betw
Am 16.09.2017 um 11:36 schrieb Tony Marston:
wrote in message news:bd24d73e-4999-ffd9-ce03-6b7629037...@rhsoft.net...
after i switched every piece of code i write the last 15 years tpo
strict-types, typhe-hints and return-types everywhere while also write
a complete autotest suite you can't t
tures instead cripple things?
As other people have pointed out before
it may not be the best idea to remove it since there’s no good way to
write the equivalent code in PHP. No reason to be rude.
On 16 Sep 2017, 11:42 +0200, li...@rhsoft.net , wrote:
Am 15.09.2017 um 20:27 schrieb Arvids Go
Am 15.09.2017 um 20:27 schrieb Arvids Godjuks:
well, basically, none. Results are from a Q6600 machine and under windows,
so your mileage probably gonna be quite better :)
well, and now implement the EXTR_SKIP in PHP code - that becomes a ugly
piece of code and that only because someone like
Am 15.09.2017 um 19:38 schrieb ilija.tov...@me.com:
I can see your argument. The reasoning behind it is that a function in the
standard library should not encourage unsafe code. Admittedly, since this
function is rarely used
who do you think you are that you can qualify this?
breaking news:
Am 15.09.2017 um 19:20 schrieb ilija.tov...@me.com:
Hi!
The `extract` function takes an associative array and puts it into the local
symbol table.
http://php.net/manual/en/function.extract.php
```
$array = [
‘foo’ => ‘foo’,
‘bar’ => ‘bar’,
];
extract($array);
print $foo; // "foo"
Am 15.09.2017 um 16:58 schrieb Tony Marston:
wrote in message news:5fe274c1-36de-e650-fd2c-bc4f9caf3...@rhsoft.net...
Am 15.09.2017 um 11:25 schrieb Tony Marston:
You are missing a third option - Microsoft languages are
case-preserving. This is where the IDE ensures that every use of a
word
Am 15.09.2017 um 16:38 schrieb Tony Marston:
wrote in message news:8bbcc1fc-0d13-27d4-a04f-0a5ebda4c...@rhsoft.net...
Am 15.09.2017 um 11:12 schrieb Tony Marston:
I am not asking the world to slow down because I am too lazy to
change. I am arguing that case insensitive software has been arou
Am 15.09.2017 um 16:15 schrieb Tony Marston:
Can you show me any language where a single character has multiple
alternatives when switching case?
http://cdn.webfail.com/upl/img/07181c2ca27/post2.jpg
_
german: Sie ist wirklich gut zu Vögeln
english: she is
Am 15.09.2017 um 11:25 schrieb Tony Marston:
You are missing a third option - Microsoft languages are
case-preserving. This is where the IDE ensures that every use of a word
is automatically switched to the case used in its original definition.
This makes it impossible to use the same word wi
Am 15.09.2017 um 11:12 schrieb Tony Marston:
I am not asking the world to slow down because I am too lazy to change.
I am arguing that case insensitive software has been around for many
decades, and for some people to advocate for its removal just because
they don't have the brain power to co
Am 11.09.2017 um 23:49 schrieb Yasuo Ohgaki:
but you still fail to explain why in the world you don#t try to
enhance the existing filter functions instead invent a new beast
leading finally to have the existin filter functions and your
new stuff which share the sa
Am 11.09.2017 um 23:39 schrieb Yasuo Ohgaki:
On Tue, Sep 12, 2017 at 6:35 AM, li...@rhsoft.net
but you still fail to explain why in the world you don#t try to
enhance the existing filter functions instead invent a new beast
leading finally to have the existin filter functions and
Am 11.09.2017 um 23:07 schrieb Yasuo Ohgaki
On Tue, Sep 12, 2017 at 12:22 AM, Stephen Reay
So, you still didn’t actually provide an example. I *guess* you’re talking
about character class validation or something else equally “simple”,
because I can’t imagine what else would be a common enough
Am 10.09.2017 um 22:35 schrieb Rowan Collins:
On 10/09/2017 20:35, li...@rhsoft.net wrote:
with "
strict_types does not currently have any effect on comparisons anywhere,
and nor is it likely ever to do so. It is a very specific option, not a
broad set of behaviours like "use str
Am 10.09.2017 um 21:25 schrieb Ryan Pallas:
On Sep 10, 2017 1:23 PM, "li...@rhsoft.net <mailto:li...@rhsoft.net>"
mailto:li...@rhsoft.net>> wrote:
Am 10.09.2017 um 21:16 schrieb Theodore Brown:
On Sunday, September 10, 2017 12:45 PM Rowan Collins
Am 10.09.2017 um 21:16 schrieb Theodore Brown:
On Sunday, September 10, 2017 12:45 PM Rowan Collins
wrote:
Would it be possible to add an optional `$strict` parameter to
switch? E.g.
```
switch ($i, true) {
I'd very much prefer a "strict switch ($i) { ... }" over a second parameter.
Wha
Am 06.09.2017 um 13:52 schrieb Lester Caine:
The likes of ADOdb datadict are still used as a base for metadata in
projects, but PDO destroyed the standardisation that used to exist by
spawning a number of competing wrappers. https://github.com/ADOdb/ADOdb
has evolved from a private project to b
Am 05.09.2017 um 18:57 schrieb Lester Caine:
But not at the cost of writing different sets of code to play to each
area where checking SHOULD be done. Stick to a single standard method of
defining the metadata and that already exists in the database layer
ok, to make that point clear:
not eve
Am 05.09.2017 um 15:44 schrieb Lester Caine:
On 05/09/17 14:08, li...@rhsoft.net wrote:
the only question as applicaton developer is how you proceed in which cases
* reject the whole request with a error-message
* reset form-fields where you don't expect an array as input
* reset from-f
Am 05.09.2017 um 13:36 schrieb Lester Caine:
On 05/09/17 12:18, Yasuo Ohgaki wrote:
I cannot guess people's thought. I appreciated feedback!
With a decent database layer a lot of the validation you are proposing
is already covered but PDO does not help in this area. Adding another
layer that
or 7.2 got worse - maybe someone tries to get this wrong again
- it's just meant as a warning from somebody which built many
pre-release and HEAD states starting from 2017/02 and just noticed that
things become worser over time
Am 20.08.2017 um 20:01 schrieb li...@rhsoft.net:
i saw exactl
i saw exactly the same "You should recreate aclocal.m4 with macros from
libtool 2.4.6" with the first alpha tarball while all the time HEAD, 7.0
and 7.1 are working fine with the same build-spec
__
that is part of the php.spec - what else should one do to re-
after upgrade the first production server from 7.0.22 to 7.1.8 i have
seen that error twice, likely every time after upgrade said file
is this a known (probably even fixed in trunk) issue in 7.1.x and if not
am i right that this come from opcache?
Sun Aug 20 19:45:38 2017 (3066): Warning Inte
Am 19.08.2017 um 16:28 schrieb Admin NxPoint:
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
with current 7.2 HEAD runnign the tests in context of rpmbuild triggers
the warnings in the global errorlog - frankly there is no point loading
something from the system when with "-n -c" a explicit config which also
speficifes the extension_dir is given "/usr/lib64/php/modules/phar.so"
is not
Am 30.07.2017 um 01:35 schrieb Kalle Sommer Nielsen:
2017-07-29 22:17 GMT+02:00 Stanislav Malyshev :
I've seen scenarios where it is very useful. Sure, you can always build
another layer of indirection and solve it this way, but it's just making
people do more work for no reason. I don't see a
Am 29.07.2017 um 08:47 schrieb Thomas Hruska:
On Fri, Jul 28, 2017 at 11:03 AM, li...@rhsoft.net
wrote:
make POST/GET/SERVER readonly - only when you refactor a 25 line code
base as well as deplyed code which relies on the framework did the right
thing with them previously :-)
Are you
Am 28.07.2017 um 18:21 schrieb Kalle Sommer Nielsen:
2017-07-28 17:11 GMT+02:00 Sara Golemon :
I'm sure there will be many strong opinions on this, but let's move
this to a new thread. :D
1. This would be an 8.0 change as it does represent a significant BC change.
2. We can discuss the possib
1 - 100 of 170 matches
Mail list logo
