Hi, all
At first, Thanks for all your work put in here, Marcio. It gave me a new
hint for a possible code-failure.
FYI: PhpStorm lately added an inspector for that. Glad to see that move
after I heard that the RFC won't pass.
https://youtrack.jetbrains.com/issue/WI-14692
Bye,
Simon
On Mon, Mar
Hi, Daniel
I'd also set the collation to *utf8_unicode_ci*. Here's a link to the full
diff of the *my.cnf* file I am using on my dev-server:
https://github.com/SimonSimCity/webserver-configuration/blob/master/mysql/patch.diff
Bye
Simon
2012/2/24 Daniel Convissor
> Hi Johannes:
>
> > 1) You sai
Hi,
This does not seem like a good way for me ...
Think about combining many scripts.
It's for example quite usual to use Symfony and parts of Zend Framework
together. Think about what will happen if the one framework uses another
autocast logic ...
Bye
Simon
2012/2/27 Anthony Ferrara
> I fai
Hi, Richard
The development of the unicode-as-default-charset should really be done
within the next release coming after 5.4
I heared somewhere that it's nearly done ...
I would have happily seen it in 5.4 but as this release is late right now
we have to wait ;)
Bye
Simon
p.s. *
http://www.php.n
Hei, Richard
I've looked into the php.ini.* files of PHP 5.4 for windows and saw the
following line in *production*:
error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT
display_errors = On
log_errors = On
and the following line in *development*:
error_reporting = E_ALL
display_errors = Off
log_er
Hi, Dmitri
Great that someone's mentioning it.
I thought about that several times but did not put it in here.
This is a must-have for me. Really useful if you're working with external
resources (streams, database connection etc).
I used a destructor until now for stuff like that but there are som
Hey, Michael
This is by far the best possible way I read in the whole conversation.
I like the way of backwards-compatibility, error-reporting and so on.
This is would be very useful and would not disturb someone's
framework-combination.
This should be written down in a new RFC.
For all who wan
Hi, Arvids
I do understand your arguments ...
For me personally it's mostly to separate between string and numbers. A
string to number transformation is most-likely not without loosing
something ... This is most likely the reason why I want to have a E_STRICT
or E_NOTICE if something like that ha
Hi, John
I personally do not care about weak or strong variables at all ... I only
want what Arvids suggested last time:
> test(1, 2); // 2;
> test("1", 2); // 2
> test("1aaa", 2); // E_NOTICE or E_TYPE and result 2
> test(array(2), 2); // E_RECOVERABLE_ERROR - just like with array type
hint now.
Hi,
We could even combine this with the following RFC:
https://wiki.php.net/rfc/object_cast_magic
If an integer is required and you pass an object, it first checks if this
object is castable to integer ;)
Bye
Simon
2012/2/29 Simon Schick
> Hi, John
>
> I personally do not care abou
x27;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 object_cast_magic one.
>
> And thanks for the support :)
>
> 2012/2/29 Simon S
Hi, all
I just read this post about a vulnerability by loading doctype-declaration
of an xml-string given in a request:
http://www.idontplaydarts.com/2011/02/scanning-the-internal-network-using-simplexml/
Would it be a good point to restrict which urls can be loaded in the
doctype, or is the foll
Hi, Kris
I don't think we have to care about scripts that are written right now if
we're talking about throwing an E_RECOVERABLE_ERROR or E_WARNING because
this feature is completely new. But I like the idea to have all type-hint
failures ending up the same way.
I personally would keep the error-
0 is passed to a
>> bool, I'd say that should be fine without an error. If you were to pass a
>> 2, though (you insolent bastard!), then it would throw the error.
>>
>>
>> I think we're getting pretty close to having enough to write an RFC for
>> this.
Hi, All
Sorry for pulling the old RFCs out. But why is their status is still *in
draft* or something like that? I did not know something about the
6-month-rule.
That's also what I mentioned before with the missing solution ... If you
close an RFC or set it to *accepted*, please also write what has
houghts on the suggestion I made earlier about
> adding "secondary questions" to the voting procedure (please read it before
> commenting), I'd love to hear them! I think that could be very helpful in
> future RFCs, so if there's any interest I'll go ahead and draft one
Hi, Adam
I just get the feeling that this is exactly what we're currently discovered
in some other threads in this mailing-list.
We're now getting more and more closer to what we really want and a good
way to write it the PHP-way.
Please try to get a rough overview over the last messages we wrote
Hi, John
Just to add an idea to yours ..
Do you think it's a compatibility-break if we'd decide to send a E_NOTICE
or E_WARNING if we f.e. try to give a string to a method that just allows
integer for this argument?
No break at all, just a E_NOTICE or E_WARNING as the script can succeed
anyways.
rre conversions not silent
> (BC
> > > break)
> > > 3. Try to find a creative solution to be consistent without changing
> > > anything about the conversion behavior. (I'm not seeing a way to do
> this
> > > one, unless we redefine "consistent".)
&
Hi, all
When will the documentation be ready?
For example you wrote that something has changed to the keywords *continue *and
*break *- but I dont get what and it's not defined in here:
http://www.php.net/manual/en/control-structures.continue.php
Bye
Simon
2012/3/2 Kris Craig
> Lol agreed. I
Hi, Kris
I have to confirm that that's not really what I wanted.
But many people were now talking about type-hint to scalar, but that was
maybe in another thread in this list :)
To get more to the point what were discussing about want:
Why not always (at least try) to transform the data?
In PHP
ve an option to give an object in here that implements all
interfaces that makes an object accessible as an array - for example
ArrayIterator.
Bye
Simon
2012/3/2 Simon Schick
> Hi, Kris
>
> I have to confirm that that's not really what I wanted.
> But many people were now talking abo
Hi, all
It's really hard to make a decision here because you also have to care
about big companies in one way, that have not updated to PHP 5.3 now ...
But instead of that I read some posts from November last year that they
have PHP6 in their control-panel, what is basically PHP 5.4 beta ...
One
Hi, Anthony
At first, thanks for your great work!
As I have to learn C and C++ from scratch it was quite a good help to have
someone like you pushing it forwards.
I like having the casting exactly in the definition of the function, even
if it just saves the 6 characters. You have all information
Hi, Lazare
This is something not obvious, at least for me, and should be handled in
the function itself.
Here it would be better to update the function *add()* that you could also
pass mixed and it will try to generate a *DateInterval *out of that or
whatever.
But that's another RFC.
Type-juggli
Hi, Lazare
In your examples you are accessing an maybe non-existing array-key.
This will raise an E_NOTICE. See the note below this example:
http://php.net/manual/en/language.types.array.php#example-85
Maybe you also want something like that:
isset($x) ? (is_null($x) ? null : (int)$x) : null
But
o the whole proposal.
>
> Lazare INEPOLOGLOU
> Ingénieur Logiciel
>
>
>
> 2012/3/5 Simon Schick
>
>> Hi, Lazare
>>
>> In your examples you are accessing an maybe non-existing array-key.
>> This will raise an E_NOTICE. See the note below this exam
Hi,
It got quite around that because we have some RFCs to this where the
functionality seems to be defined as the people thought it should be.
Otherwise they can raise their hands and write a mail that they want to
update the RFC - but as there's no one doing that, I think we're quite
close to wha
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 :
> I realize that with scalars it's not that straight forward, but
> complicating things by adding an auto-cast syntax and so on is just
> ridiculous.
types.
function foo(int $d = 20) { var_dump($d); }
foo(null); // This should then also fail. Don't care about what's the
default-value.
Bye
Simon
2012/3/8 Simon Schick :
> Hi Arvids,
>
> I pretty much like this idea as it's more strict. Let me say something
> to th
2012/3/8 John Crenshaw :
>
> Conversion the other way is essential. Consider the following URL:
>
> http://example.com?foo=1
>
> In your PHP script $_GET['foo'] === '1' (a string).
>
> In fact, nearly every input to PHP is a string. This is why PHP was designed
> with some seriously robust type ju
Hi,
Yea! I really need that too.
One thing I can provide is my own blog, but it's more stuff about bugs in
systems, ideas I come around and implementation-possibilities. Nothing
really internal.
http://www.simonsimcity.net/
Other interesting blogs (all in german):
http://www.phpgangsta.de/
http:
2012/3/8 Remi Collet
>
> But mhash_001.phpt and mhash_003.phpt should not fail
> (if we want a great PHP with 0 test failed).
>
Hi, all
That's what I would like to have ...
It would be perfect if new versions were not brought out if some tests
still fail.
I read some posts in the past before I
2012/3/8 Sebastian Bergmann :
> Am 08.03.2012 17:05, schrieb Michael Morris:
>> Thoughts?
>
> Sounds pointless/useless to me.
>
> --
> Sebastian Bergmann Co-Founder and Principal Consultant
> http://sebastian-bergmann.de/ http://thePHP.cc/
>
> --
> PHP
2012/3/8 Sebastian Bergmann :
> Am 08.03.2012 17:05, schrieb Michael Morris:
>> Thoughts?
>
> Sounds pointless/useless to me.
>
> --
> Sebastian Bergmann Co-Founder and Principal Consultant
> http://sebastian-bergmann.de/ http://thePHP.cc/
>
> --
> PHP
Hi, all
At first, many thanks to Anthony for writing the code!
2012/3/9 Anthony Ferrara
> fooi(1.5); // int(1)
Here an E_NOTICE would be a minimum as we are modifying the data. I'd
like to see an E_RECOVERABLE_ERROR as well. You should use
float-casting instead if you want to allow this as well
2012/3/9 Lazare Inepologlou
>
> Yes, like that, only better. Since automatic type casting is central in
> PHP, as this is evident after all this discussion, I believe that it
> should
> be better supported. There are two thinks that I would like to see here:
>
> 1. No more magic methods, please.
>
2012/3/9 Lazare Inepologlou
>
> Type casting combined with passing by reference is problematic in many ways.
> Just an example:
>
> fuction foo( string & $buffer) { ... }
> foo( $my_buffer );
>
> Here, $my_buffer has just been declared, so it is null. Should this be an
> error? I don't know! So,
2012/3/10 Pierre Joye
>
> hi Pierrick,
>
> I would rather go with php-next. The amount of changes are not safe
> for a now very stable version in 5.3 and 5.4 (same code base), while
> the code could be nicer as you did it in trunk.
>
> Cheers,
>
> On Sat, Mar 10, 2012 at 5:57 PM, Pierrick Charron
2012/3/10 Reindl Harald :
>
>
> Am 10.03.2012 18:28, schrieb Simon Schick:
>> I'd like to see a new interface for curl in php ... I have no special
>> idea how, but I heard from several people that they pretty much don't
>> like the way curl is implemented in
2012/3/12 Lazare Inepologlou
>
> function set_check_box_state( bool state = false ) { ... }
> set_check_box_state( null ); // null will be converted to false here...
>
> Therefore, this cannot work, unless the default value becomes null, which
> is against the requirements. What I suggest is some
Hi, All
I just came around that talk a couple of days ago ..
http://www.youtube.com/watch?v=R2Cq3CLI6H8
I don't know much about hash-maps and internal php-stuff at all, but they
say that the fix provided in 5.3.9 (and 5.4.0) is more a work-around than a
fix ...
Would it be an option to provide a
2012/3/16 Ángel González
>
> On 16/03/12 18:45, Lütfi Altın wrote:
> > I want to read PHP source and help PHP for further development.
> >
> You don't need a svn account to read the php source. You can just
> download the source from http://php.net/downloads.php#v5 view the
> development version a
Hi, all
Today I read a post around that:
http://nikic.github.com/2012/03/06/Scalar-type-hinting-is-harder-than-you-think
As some of us are leading to the 3rd and some to the 4th or other ways
described in here (I think we can simply exclude the first one ...)
Would it be an option (to get this mo
Hi, All
I just came around that talk a couple of days ago ..
http://www.youtube.com/watch?v=R2Cq3CLI6H8
I don't know much about hash-maps and internal php-stuff at all, but
they say that the fix provided in 5.3.9 (and 5.4.0) is more a
work-around than a fix ...
Would it be an option to provide a
2012/3/18 John Crenshaw :
>
>> 2. Unenforced type hinting:
>
> This almost happened in 5.4, but eventually got pulled. More interestingly,
> the *community* rejected it because it is useless. See the comments at
> http://sebastian-bergmann.de/archives/900-Scalar-Type-Hints-in-PHP-5.3.99.htm
2012/3/18 Simon Schick :
> 2012/3/18 John Crenshaw :
>>
>>> 2. Unenforced type hinting:
>>
>> This almost happened in 5.4, but eventually got pulled. More interestingly,
>> the *community* rejected it because it is useless. See the comments at
>>
2012/3/18 Adam Jon Richardson :
> On Sun, Mar 18, 2012 at 7:12 AM, Simon Schick
> wrote:
>
>>
>> Hi, All
>>
>> Just to add an example why I want a more strictly type-check here as
>> we have in the current type-juggling:
>>
>> http://www.
start from scratch and take
the best of each one.
Do you have time to support this project by giving ideas, writing
code, helping to find good principles, code review or something else?
Bye
Simon
2012/2/19 Simon Schick
>
> Hi, All
>
> I found one RFC in the php-wiki that requ
2012/3/19 David Soria Parra :
> Hi Internals,
>
> The initial migration is done and initial testing was successful.
>
> http://git.php.net/?p=php-src.git;a=summary
> http://github.com/php/php-src
>
> Please note that some branches and tags were renamed to make
> the repository cleaner.
>
> Please
2012/3/19 Kris Craig :
> Hey,
>
> Could we modify the workflow to recommend using the "--no-ff" switch when
> merging in a feature branch? This is by and large the recommended approach
> as it preserves the feature branch's commit history, making it
> *much*easier to sort through complex features
2012/3/19 Kris Craig :
> Simon,
>
> Yes that's a great recommendation and it should definitely be included
> IMHO! However, the merge.ff option is relatively new and is not available
> in many older Git clients that are still in use. So the --no-ff tag will
> still probably be necessary for some
2012/4/11 lijiu zhang :
> Hello everyone:
>
> I am a mater student of Australia National University. I have used PHP for
> several years, I want to join in the PHP development and contribute some
> patch.
> The git account need to User ID and Requested Password, how can I get them?
>
> Sincerely,
>
2012/4/12 Yasuo Ohgaki :
> Hi all,
>
> I think my RFC confused people on this list due to improper descriptions
> and too much information. Sorry for the confusion. I revised the RFC so
> that most important points can be understood at a glance.
>
> https://wiki.php.net/rfc/nophptags
>
> Please rea
Hi, Michael
2012/4/13 Michael Morris
>
> It would not be easy. I lack the skills required. And those who have
> the skills lack the monumental time required. But PHP could do what
> Adobe did with Actionscript. But it would not be easy or painless. It
> probably isn't worth it. But the tools
2012/4/13 Dmitri Snytkine :
> I always wondered why can't we do something like this in php
>
> class MyClass{
>
> private $storage = new ArrayObject();
>
> public function __construct($v){
> // whatever
> }
>
> // rest of class
>
> }
>
> Why can't we create a new object and assign it to property li
2012/4/14 Ralph Schindler :
> Hi all,
>
> There are many different use cases were in code we expect classes names as
> arguments to functions as fully qualified names. We do this in ZF a lot
> with our Service Location and DI components, but also with our code
> reflection API, etc. A more intere
2012/4/16 Ralph Schindler
>
> I am not quite following. There is no functional difference between
> "class", "CLASS", or "Class". The parser is case insensitive with regards
> to keywords, which "class" or T_CLASS is on of. The code snipped I showed
> there was from the .phpt test that I had in
2012/4/16 Ralph Schindler
>
> ... PHP does not invoke the autoloader to determine if the class name
> actually exists as a declaration somewhere, it simply resolves it according
> to some very specific rules (in the case of this patch, carried out by
> zend_resolve_class_name()).
>
> If I am withi
2012/4/17 Nikita Popov
>
> var_dump('123' == '0x7b'); // true
>
> In all other parts of the engine hexadecimal strings are not recognized
> [3]:
>
> var_dump((int) '0x7b'); // int(0)
>
Hi, Nikita
I personally would rather change the type-conversion for strings to integer ...
At least if you forc
2012/4/17 Gustavo Lopes :
>
> I think that would be an error. As was mentioned a few months ago when 0b
> was introduced, no other number format has this behavior. You can't do "123"
> == "0b10" or "123" == "0876". Extending this hexadecimal oddity instead of
> eliminating it is inconsistent with t
2012/4/17 Simon Schick
>
> Hi, Gustavo
>
> That's something I didn't know of ... if we're doing that, it should,
> of course, be also be done for the dual system.
> The only thing I wonder about is the code examples you're giving ...
>
> I would expect
Hi, Everyone
FYI: If you just want to check something before serving a file to the
client, you can also use something called xsendfile.
Apache: https://tn123.org/mod_xsendfile/
lighttpd: It's build in :)
nginx: http://wiki.nginx.org/XSendfile
Idea:
Do what you're doing in your php-script and add
Hi, Anthony
I personally would rename the 2nd parameter to $data as this function is
not only meant for creating secure hashes from passwords.
Bye
Simon
On Thu, Jun 14, 2012 at 4:00 AM, Anthony Ferrara wrote:
> Hello all,
>
> I've written up a quick draft version of an RFC for pull request 105
Hi, Anthony
Some questions coming up in my mind by reading this RFC:
* Will the value of the constant *PASSWORD_DEFAULT* remain unchanged
forever? Otherwise this lib, in my opinion, can cause big problems when
trying to port an existing system to a newer PHP-version.
* Is this a native version of
On Fri, Jul 18, 2014 at 7:02 AM, Theodore Brown wrote:
>> Since I am very much in favour of scalar type hints, I've updated the
>> patch to master and made some minor improvements, and I am re-opening
>> the RFC with the intent to try and get it into PHP 5.7.
>
> First of all, this is my first rep
> My main concern about the RFC the way it stands right now is that the
> current direction involves E_RECOVERABLE_ERROR instead of E_STRICT or E_CAST
> for data loss. This results in both consistency issues with casting as well
> as incompatibility with the dynamic nature of PHP scalars. I know
Hi, all
Inspired by the link http://www.phpinternalsbook.com/, provided by Ferenc
Kovacs in the thread "[PHP-DEV] About PHP NG "document lacking" argument",
I wondered why we don't gather useful links for internal PHP documentation
on the php.net website.
At the time I asked for material to contr
5, 2014 at 1:43 PM, Simon Schick
> wrote:
>
>> Hi, all
>>
>> Inspired by the link http://www.phpinternalsbook.com/, provided by Ferenc
>> Kovacs in the thread "[PHP-DEV] About PHP NG "document lacking" argument",
>> I wondered why we don'
Hi, Andrea
I feel more like Sherif Ramadan. Even so I've quite often been in the same
situation, I don't think it's a good solution to change something like
that, just for the shorthand-operator.
I think, the notice is really valuable when accessing the value and doing
something with it - like my
On Tue, Nov 25, 2014 at 11:42 PM, Nikita Popov wrote:
> On Tue, Nov 25, 2014 at 11:13 PM, Marc Bennewitz wrote:
>
>>
>> Am 25.11.2014 um 22:43 schrieb Levi Morrison:
>>
>> On Tue, Nov 25, 2014 at 2:07 PM, Marc Bennewitz wrote:
>>>
I think it's required to do the type check on runtime (Opti
Hi, all
I'd like to extend the API of php by a method.
Currently it is possible to create a DateInterval ... but if you have two
DateIntervals and want to "combine" them, you need to do it by your own.
I think it'd be a good idea to add a method for that to the DateInterval
class.
http://stacko
http://blog.ircmaxell.com/search/label/PHP%20Source%20Code%20For%20PHP%20Developers%20Series
)
Bye,
Simon
On Fri, Jun 28, 2013 at 7:10 PM, Derick Rethans wrote:
> On Fri, 28 Jun 2013, Simon Schick wrote:
>
> > I'd like to extend the API of php by a method.
>
> Great, let me know i
On Fri, Jun 28, 2013 at 11:20 PM, Derick Rethans wrote:
>
> Hey Simon,
>
> PS, please don't top-reply as per mailinglist guidelines:
> http://us2.php.net/reST/README.MAILINGLIST_RULES
>
> On Fri, 28 Jun 2013, Simon Schick wrote:
> > On Fri, Jun 28, 2013 a
On Sun, Jul 21, 2013 at 6:14 PM, Jakub Zelenka wrote:
> On Tue, Jul 2, 2013 at 8:21 AM, Simon Schick wrote:
>>
>> On Fri, Jun 28, 2013 at 11:20 PM, Derick Rethans wrote:
>> >
>> > Hey Simon,
>> >
>> > PS, please don't top-reply as
On Sat, Sep 7, 2013 at 5:29 AM, Matthew Leverton wrote:
>
> The big difference here is if I accept an options array, I understand
> that the keys are important and would never break backward
> compatibility by changing a parameter name. This isn't a case of "if
> you don't like it, then don't use
On Sat, Sep 7, 2013 at 6:55 PM, Matthew Leverton wrote:
>
> The OCD in me shudders to think about now having to parse through
> people's code like:
>
> substr('length' => 1, 'string' => 'Hello World');
>
Hi, Matthew
Wouldn't this just fail, because one required parameter is omitted?
You can jus
77 matches
Mail list logo
