2015-12-07 17:11 GMT+02:00 Zeev Suraski :
> > -Original Message-
> > From: Rowan Collins [mailto:rowan.coll...@gmail.com]
> > Sent: Monday, December 07, 2015 4:42 PM
> > To: internals@lists.php.net
> > Subject: Re: [PHP-DEV] Re: PHP 5.6 life cycle
> >
> > Rowan Collins
Hello internals,
In my opinion, right now what dictates the timeframes is Release Process
RFC: https://wiki.php.net/rfc/releaseprocess
It clearly states the rules of how things are done.
If dates for the PHP 5.6 are to be adjusted, than it requires an RFC
process and should be an exception, not
I fully support your effort to get this into the PHP to be part of core
extensions, or at least one of those that keep up with the language
releases.
This is a very good tool to have, and you can actually run it in production
to catch things that may slipped the stating (things happen). And it's
пн, 11 Май 2015, 10:21, Yasuo Ohgaki yohg...@ohgaki.net:
Hi all,
I've never wrote my blog in English, but I wrote one because peice by piece
discussion is not going to anywhere.
http://blog.ohgaki.net/dont-use-php7-type-hint-for-external-data
How many of you think current scalar type hint is
Stop trying to fix clever idiots from shooting themselves in the foot. The
standard result from these actions is to make life a pain for regular or
better programmers while only adding mild speed bumps to those clever
idiots.
Things like a numeric type will only encourage the clever idiots
2015-04-24 12:59 GMT+03:00 Johannes Schlüter johan...@schlueters.de:
On Fri, 2015-04-24 at 09:16 +0300, Arvids Godjuks wrote:
May I question the sanity of the words written in this email? :D (it's a
joke).
The whole point of mysqlnd drivers and other improvements was to cut down
2015-04-24 4:42 GMT+03:00 Benjamin Eberlei kont...@beberlei.de:
On Thu, Apr 23, 2015 at 3:45 PM, Arvids Godjuks arvids.godj...@gmail.com
wrote:
PDO is everywhere. Doctrine? Based on PDO.
You can use mysqli, oci8 or sqlsrv for example without problems in
Doctrine.
Exposing some
2015-04-23 17:02 GMT+03:00 Pierre Joye pierre@gmail.com:
On Apr 23, 2015 8:45 PM, Arvids Godjuks arvids.godj...@gmail.com
wrote:
My view is that this really needs a good discussion and regardless of the
desicions made - resource allocation to move it forward.
Whatever the intent
2015-04-23 15:56 GMT+03:00 Lester Caine les...@lsces.co.uk:
On 23/04/15 13:46, Amazon.co.uk wrote:
We are writing to confirm that we are processing your refund in the
amount of £4.89 for your
Order 204-2374256-3787503.
Curious phishing attempt ... seems to have forgotten the aim? Or was
чт, 23 Апр 2015, 13:00, Lester Caine les...@lsces.co.uk:
On 23/04/15 06:50, christopher jones wrote:
Yes, we do recommend using OCI8 over PDO_OCI. This is partly due to
some inherent design and performance weaknesses of the overall PDO
architecture.
So, lets not mark PDO_OCI as dead just
My view is that this really needs a good discussion and regardless of the
desicions made - resource allocation to move it forward.
Whatever the intent was originally for the PDO and and regardless of what
the docs say about it, as Christoph has linked and quoted, the reality is
PDO is everywhere.
C'mon guys, vote didn't pass, it's time to do something about it and not
start conspiracy theories (or I will loose hope for humanity completely). I
happened to have a job-free next week, i've been saying for a long time now
that this has to be tackled differently and even layed down some thoughts
2015-03-15 20:55 GMT+02:00 Levi Morrison le...@php.net:
What we need, is a MANAGER! To manage the Type Hint development. And one
that is not doing real development on PHP core, but someone with
understanding.
You are basically saying we should hand development of a critical
language
пт, 13 Мар 2015, 23:01, Philip Sturgeon pjsturg...@gmail.com:
Pavel,
On Fri, Mar 13, 2015 at 3:38 PM, Pavel Kouřil pajou...@gmail.com wrote:
On Fri, Mar 13, 2015 at 4:45 PM, Anthony Ferrara ircmax...@gmail.com
wrote:
But for today, I firmly believe that the Dual-Mode proposal is the
, 2015 at 12:02 AM, Arvids Godjuks arvids.godj...@gmail.com
wrote:
пт, 13 Мар 2015, 23:01, Philip Sturgeon pjsturg...@gmail.com:
Pavel,
On Fri, Mar 13, 2015 at 3:38 PM, Pavel Kouřil pajou...@gmail.com
wrote:
On Fri, Mar 13, 2015 at 4:45 PM, Anthony Ferrara ircmax...@gmail.com
wrote
on. It is going to
affect the projects. And that is a bad thing. Look past the damn typehint
RFC's and just try to asses the big picture. Right now it's a tunnel vision
for many on the list.
сб, 14 Мар 2015, 1:29, Arvids Godjuks arvids.godj...@gmail.com:
Opcode caches just cache the compiled code - you still
2015-03-12 11:23 GMT+02:00 Zeev Suraski z...@zend.com:
-Original Message-
From: Bob Weinand [mailto:bobw...@hotmail.com]
Sent: Thursday, March 12, 2015 12:46 AM
To: Pierre Joye
Cc: PHP internals
Subject: Re: [PHP-DEV] [RFC] Basic Scalar Types
Correct. It's just for the
2015-03-12 4:08 GMT+02:00 Lester Caine les...@lsces.co.uk:
On 11/03/15 22:44, Yasuo Ohgaki wrote:
Having namespace for internals would bring much flexibility for API
changes, both
OO and procedural API. I may try my best to have consensus.
I think you also like to have OO style API for
2015-03-12 11:41 GMT+02:00 Lester Caine les...@lsces.co.uk:
On 12/03/15 09:21, Arvids Godjuks wrote:
Basically this.
Yasuo asked me some time ago how do I see the new interface, and to be
frank, I do not see a new procedural api interface at all. We have one
now, and adding a new
2015-03-05 22:20 GMT+02:00 Yasuo Ohgaki yohg...@ohgaki.net:
Hi Arvids,
On Thu, Mar 5, 2015 at 9:32 PM, Arvids Godjuks arvids.godj...@gmail.com
wrote:
2015-03-05 13:49 GMT+02:00 Pierre Joye pierre@gmail.com:
I will say it again a last time, in my opinion only a clean API;
object
2015-03-05 13:49 GMT+02:00 Pierre Joye pierre@gmail.com:
I will say it again a last time, in my opinion only a clean API;
object-like or real object as long as performance is not affected is
the only way I could see to actually solve this problem.
Changing the names, argument order
2015-02-19 17:14 GMT+02:00 Pierre Joye pierre@gmail.com:
On Thu, Feb 19, 2015 at 7:11 AM, Arvids Godjuks
arvids.godj...@gmail.com wrote:
I think this starts to go the route of putting things into absolute.
Ideal
things tend not to happen/work in the real world to the letter.
Some
2015-02-19 17:41 GMT+02:00 Anthony Ferrara ircmax...@gmail.com:
Arvids,
I meant it in a way that no other RFC has failed so many times or had so
much misunderstanding or divide.
No scalar type proposal has made it through a vote. So none of them
have technically failed (all except the
2015-02-19 16:51 GMT+02:00 Pierre Joye pierre@gmail.com:
On Thu, Feb 19, 2015 at 6:33 AM, Zeev Suraski z...@zend.com wrote:
-Original Message-
From: Pierre Joye [mailto:pierre@gmail.com]
Sent: Thursday, February 19, 2015 4:09 PM
To: Zeev Suraski
Cc: Anthony Ferrara; PHP
2015-02-16 17:26 GMT+02:00 Daniel Lowrey rdlow...@php.net:
On Mon, Feb 16, 2015 at 10:19 AM, Zeev Suraski z...@zend.com wrote:
-Original Message-
From: rdlow...@gmail.com [mailto:rdlow...@gmail.com] On Behalf Of
Daniel Lowrey
Sent: Monday, February 16, 2015 5:13 PM
To:
2015-02-16 18:42 GMT+02:00 François Laupretre franc...@php.net:
Hi,
De : Arvids Godjuks [mailto:arvids.godj...@gmail.com]
The 0.1 RFC version was mentioned a lot as a good compromise by many
people
and had major support.
Maybe someone competent could pick it up, make necessary
Might I remind everyone that time is not on our side here - feature freeze
is looming and actual work has to be done.
The part you must understand is: Strict type hints are possible if someone
cares to implement them with a next RFC. Be our guest. Right now we need to
sort out the basic stuff -
The 0.1 RFC version was mentioned a lot as a good compromise by many people
and had major support.
Maybe someone competent could pick it up, make necessary adjustments that
where required and let people vote on it? Start with small steps - get the
weak type hints into the language first, see how
I actually have a question, that Ferenc touched on, but it never got any
discussion.
How, actually, the declare will work with concatenated PHP files? It's
quite a common practice to put the files into packages, that require
minimal amounts of includes for performance reasons.
Declare is required
2015-02-02 11:12 GMT+02:00 Dmitry Stogov dmi...@zend.com:
hi,
could you please write down few use cases, when strict scalar type hints
are really useful.
Thanks. Dmitry.
Hello Dmitry,
At the moment, being a user-land dev for a little bit more than 10 years, I
just don't see the usage for
2015-01-21 19:21 GMT+02:00 Tony Marston tonymars...@hotmail.com:
Kristopher wrote in message news:CAF9U7z_BLDusnq7c0mVToxyJpqOpa+
tmatgqrb7yqeips11...@mail.gmail.com...
On Wed, Jan 21, 2015 at 9:50 AM, Tony Marston tonymars...@hotmail.com
wrote:
You are totally missing the point. It is
2015-01-22 15:22 GMT+02:00 Arvids Godjuks arvids.godj...@gmail.com:
2015-01-21 19:21 GMT+02:00 Tony Marston tonymars...@hotmail.com:
Kristopher wrote in message news:CAF9U7z_BLDusnq7c0mVToxyJpqOpa+
tmatgqrb7yqeips11...@mail.gmail.com...
On Wed, Jan 21, 2015 at 9:50 AM, Tony Marston
On
15
Jan
2015,
at
0:33, Andrea Faulds a...@ajf.me:
Hi Marcio,
On 14 Jan 2015, at 18:52, Marcio Almada marcio.w...@gmail.com wrote:
We still have a BC break but now we also have code with **mutant**
behavior that might become buggy (do unexpected things) if a `declare` is
used. As a
2015-01-14 16:00 GMT+02:00 Pavel Kouřil pajou...@gmail.com:
Hello,
personally, as a language user, I really dislike the idea of both
options for scalar type hinting to be the part of the language.
Especially since you would have to declare the strict typing in each
file (if you are going by
Hello internals.
I'm firmly against removing the function keyword. PHP is a dynamic
language, that means that even using the latest most functional IDE's out
there, finding the implementation is not always few clicks away (PhpStorm's
Find Usages) and you need to do a search in the project. And
04 окт. 2014 г. 1:03 пользователь Kalle Sommer Nielsen ka...@php.net
написал:
Hi
2014-10-03 22:00 GMT+02:00 Arvids Godjuks arvids.godj...@gmail.com:
Hello internals.
I'm firmly against removing the function keyword. PHP is a dynamic
language, that means that even using the latest most
2014-09-01 17:12 GMT+03:00 Lester Caine les...@lsces.co.uk:
On 01/09/14 13:44, Pierre Joye wrote:
A quick ping about some anaylise done by the PVS team:
http://www.viva64.com/en/b/0277/
The ones listed are all valid so far. We will fix some of them in the
next days but feel free to
Just implement and show it working, then i'd say the guys will react.
28 авг. 2014 г. 18:24 пользователь Derick Rethans der...@php.net
написал:
On Fri, 22 Aug 2014, Derick Rethans wrote:
On Fri, 22 Aug 2014, Anatol Belski wrote:
as there are many data type changes, here's an idea on how
I have a thought about the spec.
I work on Yii framework and the team building it has a great policy - if
your changes to the code require changes to the documentation - you are
required to update the docs. No docs changes - no merge.
The most up to date documentation I have ever seen.
Maybe for
Hello!
As a user land developer I do think that over thinking this is going to end
up in disaster.
We already have quite good implementation for the array and object hints,
they do their job and do it good. No need to change those at all - leave
them as is - no need to add magic with casts and
2014-07-14 14:19 GMT+03:00 Alain Williams a...@phcomp.co.uk:
On Mon, Jul 14, 2014 at 01:09:42PM +0300, Arvids Godjuks wrote:
PHP does not need a type hinting system forces you to first make a
No one is 'forcing' anything. You use it where it is appropriate; that
does not
mean everywhere
2014-07-14 15:41 GMT+03:00 Rowan Collins rowan.coll...@gmail.com:
Arvids Godjuks wrote (on 14/07/2014):
We already have quite good implementation for the array and object hints,
they do their job and do it good. No need to change those at all - leave
them as is - no need to add magic
Hello everyone.
I just want to point out one thing about all that internals stuff and
remind about a good idea that has been surfacing a few times through the
years, but now I think it can actually get traction because of recent
problems.
It is based on the fact that there are too many people
2013/9/11 Johannes Schlüter johan...@schlueters.de
On Wed, 2013-09-11 at 13:59 +0300, Arvids Godjuks wrote:
It is based on the fact that there are too many people writing to
internals
and mailing lists are not actually manageable at this level. I stopped
following all the stuff around
2013/9/11 Johannes Schlüter johan...@schlueters.de
On Wed, 2013-09-11 at 16:26 +0300, Arvids Godjuks wrote:
P.S. While I was writing this, 4 people posted. Only Patrick Schaaf
posted usefull information. If this would be a forum - those 3 posts
should be marked as off topic and hidden
2013/9/11 Lester Caine les...@lsces.co.uk
Arvids Godjuks wrote:
P.S. While I was writing this, 4 people posted. Only Patrick Schaaf posted
usefull information. If this would be a forum - those 3 posts should be
marked as off topic and hidden by default.
But who decides what is off topic
2013/9/11 Terence Copestake terence.copest...@gmail.com
In less than 10 posts, this thread descended into people bashing each
other. Perhaps that's telling of something.
I won't comment on the point about forums or anything else, but a concern
brought up repeatedly both here and in various
2013/4/10 Dmitry Stogov dmi...@zend.com
Hi,
Recently, I've found that OPcache optimizer misses a lot of abilities,
because it handles only one op_array at once. So it definitely can't
perform any inter-function optimizations (e.g. inlining).
Actually, it was not very difficult to switch to
2013/4/10 Florin Patan florinpa...@gmail.com
On Wed, Apr 10, 2013 at 4:07 PM, Arvids Godjuks arvids.godj...@gmail.com
wrote:
2013/4/10 Dmitry Stogov dmi...@zend.com
Hi,
Recently, I've found that OPcache optimizer misses a lot of abilities,
because it handles only one op_array
2013/4/10 Zeev Suraski z...@zend.com
-Original Message-
From: Arvids Godjuks [mailto:arvids.godj...@gmail.com]
Sent: Wednesday, April 10, 2013 4:08 PM
To: PHP Internals
Subject: Re: [PHP-DEV] OPcache optimizer improvement in PHP-5.5?
2013/4/10 Dmitry Stogov dmi...@zend.com
Hello, didn't read the whole thread, just a few messages at the start. But
because I'm replying to the starting message, it's not relevant :)
In principle, as a user-land developer, I agree with the motion. It's too
much fancy new shiny stuff lately and no actual improvement on the old
stuff that
I also don't like the RFC proposed syntax. I have to say that I don't
really like those short magic-like syntax things in in other languages too.
If you work with them on the day-to-day basis and tools are built around
those concepts - it's one thing. In PHP syntax is mostly self-explanatory
and
Hello internals.
I'm actually using proctitle extension and it's very handy because we run
like 10+ daemons written in PHP that we manage. Without it we would be lost
:) But the actual awareness of the proctitle PECL extension is very low.
Also it does not work on windows.
I'm all over the idea
I have to agree with Lester.
It seems that there is a conspiracy to push annotations into PHP :D No,
really, it's like goons decided that PHP needs annotations no matter what
and just flooded the mailing list.
I think: The line must be drawn here, this far, no further! © Star Trek
Before adding
2013/1/11 Clint Priest cpri...@zerocue.com
Even so, C++ is not the only object oriented language out there.
-Clint
I could not resist the urge to suggest D as an option :) Sorry for this
troll attempt.
Well, there is Quercus out there in the wild, they did it. Sure a total
rewrite
Hello internals.
Sometimes I wonder if people even read the stuff that is written here. I
understand that this thread got long, but it's not that bad - most messages
are short and readable, easy to follow.
As with APOCALYPSE WILL HAPPEN style claims, that we see here, I just
don't understand your
2012/11/13 Anthony Ferrara ircmax...@gmail.com
There's one important thing that I think you all are missing here. You keep
bringing up that we should just use the normal deprecation process. The
problem is that the deprecation process was never designed for a feature
like this.
Look at what
Hello all!
Julien this weekend was at the conference in Riga and we talked with him
exactly about this, how it could be handled and stuff.
The bottom line of our discussion was that I expressed the opinion that
things should really start to move as of 5.5 - postponing it will not make
any
Hello internals!
After reading the discussion for some time and thinking through what has
been written, I came to the conclusion that something like legacy namespace
witch is enabled by default is required. Why? Because some projects are big
and you usually migrate them in chunks. So that way you
There are alternative opcode cachers besides APC. For example xcache, for
me, just works when APC is still catching up.
I remember someone writing about APC that it is overly compex internally
and due to that hard to keep up with the changes in the PHP, maybe that is
not the case now.
But looking
APC.
03.07.2012 15:17 пользователь Pierre Joye pierre@gmail.com написал:
hi,
On Tue, Jul 3, 2012 at 5:12 PM, Arvids Godjuks arvids.godj...@gmail.com
wrote:
There are alternative opcode cachers besides APC. For example xcache, for
me, just works when APC is still catching up.
I remember
, 2012 at 5:12 PM, Arvids Godjuks arvids.godj...@gmail.com
wrote:
There are alternative opcode cachers besides APC. For example xcache,
for
me, just works when APC is still catching up.
I remember someone writing about APC that it is overly compex internally
and due to that hard to keep up
:49 AM, Arvids Godjuks wrote:
One one side it's good to know i'm not wrong, on the other hand it's sad
in this case.
Sure about one thing - xcache is worth looking at and may be a better
choise than APC and has better potential.
One thing sure - I haven't heard anyone complaining about
Hello.
I personally think that using PASSWORD_DEFAULT for algorythm by default is
a bad idea. This should be defined by user in the code. Even worse if it is
defined by .ini setting - deploy to a remote server and realize that there
is a different .ini default that messes up everything. Lessons
one.
Thank you :-)
27.06.2012 14:16 пользователь Anthony Ferrara ircmax...@gmail.com
написал:
Arvids,
On Wed, Jun 27, 2012 at 9:23 AM, Arvids Godjuks
arvids.godj...@gmail.com wrote:
Hello.
I personally think that using PASSWORD_DEFAULT for algorythm by default
is a
bad idea. This should
I would definetly like that a lot to be the case. bcrypt is kind'a cryptic
and information about cryptography on the internet is not so informative
and are not in abundance.
Hello internals,
I should voice my opinion that such things like comparing two strings
starting with numbers and that they resolve to actual integer/float for
comparation is bad, really bad. That just defies the logic and yealds
absolutly unexpected results. I pride myself that i know the
native language and I have
been learning the British variant of it, so it's more formal that
American English :)
2012/5/7 Kris Craig kris.cr...@gmail.com
On Mon, May 7, 2012 at 12:28 AM, Arvids Godjuks
arvids.godj...@gmail.comwrote:
Hello internals,
I should voice my opinion
As far as I read there is no difference from the previous RFC - it
says essentially the same.
The ?php tag, contained within one of these files, tells the webserver
to, in essence, “switch to PHP mode” and start parsing the data as PHP code.
When the ? tag is reached, the webserver “switches
In past years such switches where deprecated and removed (in 5.3 most of
them, in 5.4 finally all that stuff is gone for good). So any solution,
involving a switch that modifies how code is executed will hit a wall of
resistance. It's the lesson that was learned the hard way.
So it may be the
Because you can write a function name, say, in Cyrilic and it will just
work.
20 апреля 2012 г. 16:47 пользователь Nikita Popov nikita@googlemail.com
написал:
On Fri, Apr 20, 2012 at 12:20 PM, C.Koy can5...@gmail.com wrote:
Hi,
This post is about bug #18556
I have to agree with Richard as a user-land developer. It looks nice, but
knowing how people can twist things I don't think I would like this feature
get implemented. It just add stuff that is crazy to debug.
Consider someone adds a property and initializes a user-land object. That
object has
I personally would vote for the default keyword if I want to skip the
param rather than just doing it with , - the keyword approach is much more
readable and error prone.
What happened with the proposal/RFC for expanding include/require with
additional optional second param to allow for developers to define in place
if he want's a pure PHP file to be included or a template file with direct
HTML output?
I like that proposal and take it over any other, because it
16 апреля 2012 г. 2:52 пользователь Kris Craig kris.cr...@gmail.comнаписал:
On Sun, Apr 15, 2012 at 2:30 PM, Arvids Godjuks
arvids.godj...@gmail.comwrote:
I posted the bellow text in other thread, but i should have it post here,
so i'm reposting it to this thread.
Well, it's time for me
related stuff.
16 апреля 2012 г. 11:09 пользователь Kris Craig kris.cr...@gmail.comнаписал:
On Mon, Apr 16, 2012 at 12:57 AM, Arvids Godjuks arvids.godj...@gmail.com
wrote:
16 апреля 2012 г. 2:52 пользователь Kris Craig kris.cr...@gmail.comнаписал:
On Sun, Apr 15, 2012 at 2:30 PM, Arvids
16 апреля 2012 г. 11:24 пользователь Ferenc Kovacs tyr...@gmail.comнаписал:
On Mon, Apr 16, 2012 at 9:46 AM, Arvids Godjuks
arvids.godj...@gmail.comwrote:
What happened with the proposal/RFC for expanding include/require with
additional optional second param to allow for developers
16 апреля 2012 г. 16:09 пользователь Tom Boutell t...@punkave.com написал:
These tools already strip ?php tags, they would need minimal changes to
support rolling in a .phpp file unmodified. Unless I am missing something?
Sent from my iPhone
On Apr 15, 2012, at 5:30 PM, Arvids Godjuks
16 апреля 2012 г. 11:05 пользователь Kris Craig kris.cr...@gmail.comнаписал:
Arvids,
On Mon, Apr 16, 2012 at 12:46 AM, Arvids Godjuks arvids.godj...@gmail.com
wrote:
What happened with the proposal/RFC for expanding include/require with
additional optional second param to allow
16 апреля 2012 г. 22:02 пользователь Kris Craig kris.cr...@gmail.comнаписал:
On Mon, Apr 16, 2012 at 10:31 AM, Rick WIdmer vch...@developersdesk.com
wrote:
On 4/16/2012 3:31 AM, Arvids Godjuks wrote:
That's sad really, to be honest.
I wonder if people even use this:
echo include
Well, it's time for me to remind about the techique many use (and some
frameworks provide it out of the box) - the application file concatination
to speed up file loading.
Yii framework provides a Yiilite.php file for this, that includes mostly
used core classes in one big file.that loads much
I posted the bellow text in other thread, but i should have it post here,
so i'm reposting it to this thread.
Well, it's time for me to remind about the techique many use (and some
frameworks provide it out of the box) - the application file concatination
to speed up file loading.
Yii framework
, but it's a serious proposal
for people who persist better security. IMHO.
Regards,
--
Yasuo Ohgaki
yohg...@ohgaki.net
On Sun, Apr 8, 2012 at 5:34 PM, Yasuo Ohgaki yohg...@ohgaki.net wrote:
Hi,
2012/4/9 Arvids Godjuks arvids.godj...@gmail.com:
8 апреля 2012 г. 8:16
8 апреля 2012 г. 8:16 пользователь Yasuo Ohgaki yohg...@ohgaki.netнаписал:
2012/4/8 Ángel González keis...@gmail.com:
On 07/04/12 22:48, Yasuo Ohgaki wrote:
Hi,
The only valid reason for removing ?php from PHP script would be
security.
Since the null byte detection for fopen,
I should point out that returning false on param parsing failure on the
language level is one thing (not to mention it's not ok to do that in the
first place by my taste), but forcing that behavior on the user-land level
is kind'a too much.
Consider how the code will become much more complicated
What is consistent and exists on the internal language layer
not necessarily good for the user-land. I'm kind'a surprised no one
thought
of that.
As I said I can live with the throwing notices and warnings (and not
E_RECOVERABLE_ERROR as I personally wanted), but returning false even
I think that the null issue is not an issue. Strictly speaking if you
want null or an int - leave out the type hint and use generic argument that
will accept anything.
I think it's over-engineering to try and push a special treatment for the
null. If function/method argument accepts anything but a
2012/3/12 Lazare Inepologlou linep...@gmail.com
I'm not sure about you, but I don't wanna see that kind of thing
eventually making it's way into the language
Me neither. All I am saying is that, since int|null is already here from
the back door, I think it should be properly supported.
Overall good job. I would prefer it a little stricter like people already
mention, but it's a step forward definitively with witch I'm totally fine
to live with.
Hi Simon!
2012/3/8 Simon Schick simonsimc...@googlemail.com:
Hi Arvids,
I pretty much like this idea as it's more strict. Let me say something
to the questions you pointed out here.
2012/3/7 Arvids Godjuks arvids.godj...@gmail.com:
I realize that with scalars it's not that straight forward
Type hints are meant to
filter input from external sources
Correction, it should read like this:
Type hints are _not_ meant to filter input from external sources
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
2012/3/8 John Crenshaw johncrens...@priacta.com:
From: Arvids Godjuks [mailto:arvids.godj...@gmail.com]
I like that. What should we do if this appears? As it's now - just
throw an Catchable fatal error and let the script blow-up? I would
go this far.
I think Catchable fatal error should
2012/3/8 John Crenshaw johncrens...@priacta.com:
From: Arvids Godjuks [mailto:arvids.godj...@gmail.com]
That's why I described the rules when type juggling comes into play.
If you send a string number, it is converted from string to number by the
type hint. If you send a string of characters
Alan Knowles
You should consider the fact that some E_STRICT stuff can one day
become E_WARNING or E_FATAL. For example calling a static method
dynamically - I would bet that someday this thing will be moved to be
a run-time fatal error and fix those if I make a mistake of doing
that.
Or not
I, for one, decided not to participate in the discussions any more
because they always change to something different in a few hours of
discussion. I'm surprised how people tend to complicate the feature
into something weird and ugly. I now understand why core team just
ignores some discussions.
I
Secure code is not about the instrument, it's about how you write it.
Insecure spagetti code can be written in any language.
Combining different things into one big RFC is not a good idea. It's
hard to develop and test the work it it's in one big chunk.
Decomposition makes it much easier. Type hinting has to have it's own
RFC.
Besides - someone can be willing to do type hinting patch and don't
want to do the
Guys, you probably are too deep into the discussion that you haven't
noticed an elephant Zeev has put into the room. When the RFC procces was
put in place there was a rule outlined - if core devs decide to reject,
it's rejected. And as Zeev said last time core dev team decided that there
will be
Kris i have a question for you - who will implement a test patch? Previous
tries failed not because no one wanted, but because it was damn hard and
tricky. And ofcourse there was resistance against strict type hinting. Mine
included. I doubt any of the last timeinvolved will be willing to do that
Please.read my emails carefuly. What i said is last time the work has been
done, and two different patches have been developed and iterated. But
dificulties in implementation and strong resistance from the devs and
comunity got it killed. I actually had a post on our biggest russian
speaking IT
101 - 200 of 305 matches
Mail list logo