This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Archive 1 | ← | Archive 5 | Archive 6 | Archive 7 | Archive 8 |
This article has the potential to be very in-depth and informative but it reads like a technical discussion amongst php experts. It is very difficult to understand what PHP by reading the article as the article focusses too much on the guys who developed it, the release history and so on.
It would be nice to have a few simpler paragraphs explaining what it does, how it does it and with a few basic examples of use in a web browser. As it is right now, we dive straight into functions and comparisons with other programming languages. —Preceding unsigned comment added by 84.231.11.146 ( talk) 06:49, 15 January 2011 (UTC)
I've uploaded an audio recording of this article for the Spoken Wikipedia project. Please let me know if I made any mistakes (especially with pronouncing names :-P ). Thanks. -- Mangst ( talk) 01:42, 1 February 2011 (UTC)
the article implies that Zeev and Andi changed the PHP acronym to PHP: Hypertext Preprocessor, which obviously isn't true, it was decided via a community vote: http://blog.roshambo.org/how-the-php-acronym-was-reborn/ http://web.archive.org/web/20000815063125/il.php.net/vote_listing.php3 — Preceding unsigned comment added by Tyra3l ( talk • contribs) 10:10, 16 June 2011 (UTC)
PHP_Data_Objects redirects to this page, but PDO is mentioned nowhere on this site. Birchhunter ( talk) 23:04, 9 July 2011 (UTC)
mod_php redirects here but it's only mentioned once in passing. 66.187.233.202 ( talk) 02:32, 13 August 2011 (UTC)
I find it pretty incredible that erroneous security data is posted on this article and the reference source is just someone's personal page. Even so, the data posted on this page doesn't even match the data in the article. Being that PHP is a real threat to other corporate backed languages (that themselves have huge security problems) , it is obvious to any reader that this whole section is just someones sour grapes. — Preceding unsigned comment added by 20.142.112.36 ( talk) 17:17, 30 August 2011 (UTC)
If you read carefully the referenced web page (which is a personal page), (
http://www.coelho.net/php_cve.html) the author got these numbers
by typing PHP into the vulnerabilities website and then he COUNTED THE HITS. Wow. How is that the basis for ANY statistic? It is exactly
the same as typing in "(something) sucks" into google, changing the (something) and repeating and then drawing a conclusion. The author on the website
actually disclaims his method for being construed as anything legitimate on his personal page:
One can query the database for keywords (e.g. PHP) and dates. It is a little bit crude: * there may be PHP-related vulnerabilities without the PHP keyword in them (say a bug in the PCRE library may affect PHP) * some vulnerabilities may have the keyword without being directly related to PHP (a description may contain a reference to a PHP web page). * a vulnerability report may indicate many vulnerabilities or they may be scattered into several reports.
How this is somehow a reference for the FUD that was then placed on this page is beyond me. This is the reason I removed the paragraph as it was, beyond any doubt, fud. — Preceding unsigned comment added by 20.142.112.36 ( talk) 17:35, 30 August 2011 (UTC)
Hello My name is Artur Polanski and I represent Software Press company. We are creating a new version of popular magazine PHP Solution (English version), which will be available online and we are looking for authors who could provide us with some interesting articles concerning PHP5. I believe your expertise in this matter might be invaluable to our readers and maybe you could share your knowledge with us. Shall anyone be interested in such cooperation please contact me: artur.polanski@software.com.pl Best regards,
Artur Polanski. — Preceding unsigned comment added by 83.7.80.254 ( talk) 12:36, 9 January 2012 (UTC)
{{Requested edit}}
In
PHP#Release_history, For release 5.4.0 could we mention the new Built-in web server
[1]? Thanks.
Eclipsed
(talk)
(COI Declaration)
16:14, 2 March 2012 (UTC)
Done That seems fine. Thanks! — Jess· Δ ♥ 07:01, 26 March 2012 (UTC)
PHP is often criticised for lack of solid language design and other shortcomings; see, for instance, at http://phpsadness.com/ and http://me.veekun.com/blog/2012/04/09/php-a-fractal-of-bad-design/
I think there should be a section on these criticisms, but I'm not sure I can write that in the proper NPOV tone myself. — Preceding unsigned comment added by Yoe ( talk • contribs) 21:11, 13 May 2012 (UTC)
I added a criticism section, because of the wide-spread criticisms of PHP. There are market share statistics that show that many small companies tend to prefer PHP and LAMP development over Java or .NET simply because the technology is free. 202.232.200.82 ( talk) 02:51, 13 June 2012 (UTC)
CAUTION: I've used php extensivly (expert level) and I can tell you from painful experience that php has some serious/fatal bugs. when I tried to get the bugs fixed i found that the developer community was badly dysfunctional, there is much fighting between them, there are developers who complain about the poor quality of the code, there are developers who have even forked the project... but there were not any developers who were actually interested/willing to fix these terrible bugs. The result is that we had to abandon our project at huge cost because the bugs were so fundamental they could not be worked around. I shudder when I see ecommerce programs written in php, the math functions of php cannot be trusted. You have been warned.
97.126.103.236 (
talk)
02:00, 18 November 2012 (UTC)
There is no general topic of "PHP Extensions" in Wikipedia. There are web discussions of including functions written in C so the code cannot be examined. The inclusion of a discussion from an internals point of view would clarify whether existing extensions are simple functions or whether the core of PHP can be overloaded to include new functionality. Jbottoms76 ( talk) 20:51, 5 June 2012 (UTC)
Under "Visibility of properties and methods", it is stated that when a member is marked as protected, access is limited to inherited classes (and the class itself). This is incorrect: a protected member is also accessible from its superclasses. From the manual:
"Members declared protected can be accessed only within the class itself and by inherited and parent classes"
2001:980:4910:1:8147:4345:ED7B:E1DE ( talk) 07:56, 10 August 2012 (UTC)
This entry reads really badly. It goes into unnecessary detail about some aspects of php--complete with obtuse coding examples--while not spending much time talking about what php is and what makes it different than other languages. Also why does anyone need to know such a complete release history of php? To enjoy and gain knowledge from this article the reader would need advanced computer knowledge and already have a very strong interest in php. SciutoAlex ( talk) 17:52, 10 August 2012 (UTC)
It's an article on a programming language, well in keeping with the Perl, Python (programming language) and Ruby_(programming_language) articles. It may even be a little basic; more code examples would be useful. If one does not have 'advanced' computer knowledge and a very strong interest in PHP, then one has no need of reading farther than the first sentence. — Preceding unsigned comment added by 24.89.139.58 ( talk) 18:53, 26 December 2012 (UTC)
The article claims, the initial version was developed in C, and then claims, that was re-implemented in C. That is wrong. The initial version was written in Perl (these were the "Personal Homepage Tools") and the 2nd version was re-implemented in C. See also the german Wikipedia. Yes, PHP started out as a bunch of Perl scripts. LinguistManiac ( talk) 08:36, 8 March 2013 (UTC)
Hi. The current version of this article has a "Release history" section sorted by minor version instead of using release date. It seems wrong to me to have a history section not sorted chronologically. -- MZMcBride ( talk) 04:43, 14 April 2013 (UTC)
The existence of PHP virtual machine runtime environments (e.g. HipHopVM, Parrot) is not mentioned. The implementations section would be a good place to mention these approaches. Hopscotch23 ( talk) 17:03, 22 February 2014 (UTC)
About all the flaws alleged to be in PHP? Turkeyphan t 02:41, 21 May 2013 (UTC)
How does one pronounce "PHP" in spoken English? Since SQL is often rendered as "sequel", I personally advocate for pronouncing PHP as "fap"; and consequently refer to PHP conferences as circle-jerks. However, most people regard this as silly and sound out Pee Aych Pee My Sequel when they read "PHP/MySQL". — Preceding unsigned comment added by VoodooKobra ( talk • contribs) 15:53, 14 April 2014 (UTC)
Up to May 8th, we've had a reasonably state single sentence summary in the Lede "PHP code is interpreted by a web server with a PHP processor module, which generates the resulting web page: PHP commands can be embedded directly into an HTML source document rather than calling an external file to process data. ", which was then ping-ponged around by Ngyikp and Erinaedu and the result wasn't grammatically correct. I proposed a middle course to try to avoid an edit war starting, and in fact without realising it pretty much reinstated the original (except the addition of usually "PHP code is usually ...").
Now OMPIRE has "fixed" this mess by replacing this by changing this to "PHP code is usually executed within the address space of a web server with a PHP interpreter embedded as a module. The server then sends PHP's output to its client.". Unfortunately, this summary isn't true:
My suggestion is that the original wording -- albeit looser -- wasn't inaccurate and is therefore a better lede summary. Can anyone propose a better -- and still accurate -- alternative? -- TerryE ( talk)
The article states "In 2013, 9% of all vulnerabilities listed by the National Vulnerability Database were linked to PHP;[129] historically, about 30% of all vulnerabilities listed since 1996 in this database are linked to PHP."
Although the writer distiguishes between programmer based error and flaws in the language core the implication remains that PHP as a langauge is the cause of web security vulnerabilities.
However, as it stands, the statisitc is meaningless and highly misleading unless we know what the relative percentage of sites on the web use PHP versus those using other scripting language. If 90% of websites (to pick a number out of the air) use PHP then no one should be surprised (it is less than noteworthy) that historically 30% of all vulnerabilities are linked to PHP. For this stat to have relevance we need to know:
1. What is the distribution of scripting languages on internet web sites. 2. What is the distribution of vulnerabilities for each language. 2. More difficult but important: are any of the identified vulnerabilites somehow inherent in the language or are we talking about the failure of programmers to write secure code? — Preceding unsigned comment added by 205.207.78.4 ( talk) 17:02, 24 March 2014 (UTC)
A proper search for Core PHP Vulnerabilities since 1999 can be viewed by using the Advanced search in NVD: http://web.nvd.nist.gov/view/vuln/search-results?adv_search=true&cves=on&cpe_vendor=cpe%3a%2f%3aphp&cpe_product=cpe%3a%2f%3aphp%3aphp&pub_date_start_month=0&pub_date_start_year=1999&cve_id= 72.21.198.64 ( talk) 19:03, 27 June 2014 (UTC)
Maybe I'm a bit unclear, but the current name of PHP is (PHP: Hypertext Preprocessor). Shouldn't his be in bold at the beginning at the article instead of in the middle? CarnivorousBunny talk • contribs 14:09, 20 April 2014 (UTC)
has anyone else noticed that the hello world code doesn't work properly? Both Firefox and Chrome return:
Hello World
'; ?>
I'm not knowledgeable enough about PHP to fix even this error properly. -- Kwixtartpahtee ( talk) 23:05, 22 June 2014 (UTC)
helloworld.php
). Then type php -S localhost:8888
to start a server. Open your browser and go to localhost:8888/helloworld.php
and the code will then work.
Let99 (
talk)
06:24, 10 November 2014 (UTC)PHP always had variadic functions, at least since PHP4 days, with func_num_args() / func_get_arg() / func_get_args() / ... ( https://php.net/manual/en/function.func-num-args.php / https://php.net/manual/en/function.func-get-arg.php / https://php.net/manual/en/function.func-get-args.php ) Divinity76 ( talk) 10:50, 7 January 2015 (UTC)
when i use this connection to connect to the database it brigs me errors mysql_connect("localhost","root",""); mysql_select_db("pass"); — Preceding unsigned comment added by 197.232.26.250 ( talk) 06:19, 22 April 2015 (UTC)
Does anyone want to help modernize and expand the PHP syntax and semantics page? It's really bad at the moment. Let99 ( talk) 06:21, 10 November 2014 (UTC)
This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Archive 1 | ← | Archive 5 | Archive 6 | Archive 7 | Archive 8 |
This article has the potential to be very in-depth and informative but it reads like a technical discussion amongst php experts. It is very difficult to understand what PHP by reading the article as the article focusses too much on the guys who developed it, the release history and so on.
It would be nice to have a few simpler paragraphs explaining what it does, how it does it and with a few basic examples of use in a web browser. As it is right now, we dive straight into functions and comparisons with other programming languages. —Preceding unsigned comment added by 84.231.11.146 ( talk) 06:49, 15 January 2011 (UTC)
I've uploaded an audio recording of this article for the Spoken Wikipedia project. Please let me know if I made any mistakes (especially with pronouncing names :-P ). Thanks. -- Mangst ( talk) 01:42, 1 February 2011 (UTC)
the article implies that Zeev and Andi changed the PHP acronym to PHP: Hypertext Preprocessor, which obviously isn't true, it was decided via a community vote: http://blog.roshambo.org/how-the-php-acronym-was-reborn/ http://web.archive.org/web/20000815063125/il.php.net/vote_listing.php3 — Preceding unsigned comment added by Tyra3l ( talk • contribs) 10:10, 16 June 2011 (UTC)
PHP_Data_Objects redirects to this page, but PDO is mentioned nowhere on this site. Birchhunter ( talk) 23:04, 9 July 2011 (UTC)
mod_php redirects here but it's only mentioned once in passing. 66.187.233.202 ( talk) 02:32, 13 August 2011 (UTC)
I find it pretty incredible that erroneous security data is posted on this article and the reference source is just someone's personal page. Even so, the data posted on this page doesn't even match the data in the article. Being that PHP is a real threat to other corporate backed languages (that themselves have huge security problems) , it is obvious to any reader that this whole section is just someones sour grapes. — Preceding unsigned comment added by 20.142.112.36 ( talk) 17:17, 30 August 2011 (UTC)
If you read carefully the referenced web page (which is a personal page), (
http://www.coelho.net/php_cve.html) the author got these numbers
by typing PHP into the vulnerabilities website and then he COUNTED THE HITS. Wow. How is that the basis for ANY statistic? It is exactly
the same as typing in "(something) sucks" into google, changing the (something) and repeating and then drawing a conclusion. The author on the website
actually disclaims his method for being construed as anything legitimate on his personal page:
One can query the database for keywords (e.g. PHP) and dates. It is a little bit crude: * there may be PHP-related vulnerabilities without the PHP keyword in them (say a bug in the PCRE library may affect PHP) * some vulnerabilities may have the keyword without being directly related to PHP (a description may contain a reference to a PHP web page). * a vulnerability report may indicate many vulnerabilities or they may be scattered into several reports.
How this is somehow a reference for the FUD that was then placed on this page is beyond me. This is the reason I removed the paragraph as it was, beyond any doubt, fud. — Preceding unsigned comment added by 20.142.112.36 ( talk) 17:35, 30 August 2011 (UTC)
Hello My name is Artur Polanski and I represent Software Press company. We are creating a new version of popular magazine PHP Solution (English version), which will be available online and we are looking for authors who could provide us with some interesting articles concerning PHP5. I believe your expertise in this matter might be invaluable to our readers and maybe you could share your knowledge with us. Shall anyone be interested in such cooperation please contact me: artur.polanski@software.com.pl Best regards,
Artur Polanski. — Preceding unsigned comment added by 83.7.80.254 ( talk) 12:36, 9 January 2012 (UTC)
{{Requested edit}}
In
PHP#Release_history, For release 5.4.0 could we mention the new Built-in web server
[1]? Thanks.
Eclipsed
(talk)
(COI Declaration)
16:14, 2 March 2012 (UTC)
Done That seems fine. Thanks! — Jess· Δ ♥ 07:01, 26 March 2012 (UTC)
PHP is often criticised for lack of solid language design and other shortcomings; see, for instance, at http://phpsadness.com/ and http://me.veekun.com/blog/2012/04/09/php-a-fractal-of-bad-design/
I think there should be a section on these criticisms, but I'm not sure I can write that in the proper NPOV tone myself. — Preceding unsigned comment added by Yoe ( talk • contribs) 21:11, 13 May 2012 (UTC)
I added a criticism section, because of the wide-spread criticisms of PHP. There are market share statistics that show that many small companies tend to prefer PHP and LAMP development over Java or .NET simply because the technology is free. 202.232.200.82 ( talk) 02:51, 13 June 2012 (UTC)
CAUTION: I've used php extensivly (expert level) and I can tell you from painful experience that php has some serious/fatal bugs. when I tried to get the bugs fixed i found that the developer community was badly dysfunctional, there is much fighting between them, there are developers who complain about the poor quality of the code, there are developers who have even forked the project... but there were not any developers who were actually interested/willing to fix these terrible bugs. The result is that we had to abandon our project at huge cost because the bugs were so fundamental they could not be worked around. I shudder when I see ecommerce programs written in php, the math functions of php cannot be trusted. You have been warned.
97.126.103.236 (
talk)
02:00, 18 November 2012 (UTC)
There is no general topic of "PHP Extensions" in Wikipedia. There are web discussions of including functions written in C so the code cannot be examined. The inclusion of a discussion from an internals point of view would clarify whether existing extensions are simple functions or whether the core of PHP can be overloaded to include new functionality. Jbottoms76 ( talk) 20:51, 5 June 2012 (UTC)
Under "Visibility of properties and methods", it is stated that when a member is marked as protected, access is limited to inherited classes (and the class itself). This is incorrect: a protected member is also accessible from its superclasses. From the manual:
"Members declared protected can be accessed only within the class itself and by inherited and parent classes"
2001:980:4910:1:8147:4345:ED7B:E1DE ( talk) 07:56, 10 August 2012 (UTC)
This entry reads really badly. It goes into unnecessary detail about some aspects of php--complete with obtuse coding examples--while not spending much time talking about what php is and what makes it different than other languages. Also why does anyone need to know such a complete release history of php? To enjoy and gain knowledge from this article the reader would need advanced computer knowledge and already have a very strong interest in php. SciutoAlex ( talk) 17:52, 10 August 2012 (UTC)
It's an article on a programming language, well in keeping with the Perl, Python (programming language) and Ruby_(programming_language) articles. It may even be a little basic; more code examples would be useful. If one does not have 'advanced' computer knowledge and a very strong interest in PHP, then one has no need of reading farther than the first sentence. — Preceding unsigned comment added by 24.89.139.58 ( talk) 18:53, 26 December 2012 (UTC)
The article claims, the initial version was developed in C, and then claims, that was re-implemented in C. That is wrong. The initial version was written in Perl (these were the "Personal Homepage Tools") and the 2nd version was re-implemented in C. See also the german Wikipedia. Yes, PHP started out as a bunch of Perl scripts. LinguistManiac ( talk) 08:36, 8 March 2013 (UTC)
Hi. The current version of this article has a "Release history" section sorted by minor version instead of using release date. It seems wrong to me to have a history section not sorted chronologically. -- MZMcBride ( talk) 04:43, 14 April 2013 (UTC)
The existence of PHP virtual machine runtime environments (e.g. HipHopVM, Parrot) is not mentioned. The implementations section would be a good place to mention these approaches. Hopscotch23 ( talk) 17:03, 22 February 2014 (UTC)
About all the flaws alleged to be in PHP? Turkeyphan t 02:41, 21 May 2013 (UTC)
How does one pronounce "PHP" in spoken English? Since SQL is often rendered as "sequel", I personally advocate for pronouncing PHP as "fap"; and consequently refer to PHP conferences as circle-jerks. However, most people regard this as silly and sound out Pee Aych Pee My Sequel when they read "PHP/MySQL". — Preceding unsigned comment added by VoodooKobra ( talk • contribs) 15:53, 14 April 2014 (UTC)
Up to May 8th, we've had a reasonably state single sentence summary in the Lede "PHP code is interpreted by a web server with a PHP processor module, which generates the resulting web page: PHP commands can be embedded directly into an HTML source document rather than calling an external file to process data. ", which was then ping-ponged around by Ngyikp and Erinaedu and the result wasn't grammatically correct. I proposed a middle course to try to avoid an edit war starting, and in fact without realising it pretty much reinstated the original (except the addition of usually "PHP code is usually ...").
Now OMPIRE has "fixed" this mess by replacing this by changing this to "PHP code is usually executed within the address space of a web server with a PHP interpreter embedded as a module. The server then sends PHP's output to its client.". Unfortunately, this summary isn't true:
My suggestion is that the original wording -- albeit looser -- wasn't inaccurate and is therefore a better lede summary. Can anyone propose a better -- and still accurate -- alternative? -- TerryE ( talk)
The article states "In 2013, 9% of all vulnerabilities listed by the National Vulnerability Database were linked to PHP;[129] historically, about 30% of all vulnerabilities listed since 1996 in this database are linked to PHP."
Although the writer distiguishes between programmer based error and flaws in the language core the implication remains that PHP as a langauge is the cause of web security vulnerabilities.
However, as it stands, the statisitc is meaningless and highly misleading unless we know what the relative percentage of sites on the web use PHP versus those using other scripting language. If 90% of websites (to pick a number out of the air) use PHP then no one should be surprised (it is less than noteworthy) that historically 30% of all vulnerabilities are linked to PHP. For this stat to have relevance we need to know:
1. What is the distribution of scripting languages on internet web sites. 2. What is the distribution of vulnerabilities for each language. 2. More difficult but important: are any of the identified vulnerabilites somehow inherent in the language or are we talking about the failure of programmers to write secure code? — Preceding unsigned comment added by 205.207.78.4 ( talk) 17:02, 24 March 2014 (UTC)
A proper search for Core PHP Vulnerabilities since 1999 can be viewed by using the Advanced search in NVD: http://web.nvd.nist.gov/view/vuln/search-results?adv_search=true&cves=on&cpe_vendor=cpe%3a%2f%3aphp&cpe_product=cpe%3a%2f%3aphp%3aphp&pub_date_start_month=0&pub_date_start_year=1999&cve_id= 72.21.198.64 ( talk) 19:03, 27 June 2014 (UTC)
Maybe I'm a bit unclear, but the current name of PHP is (PHP: Hypertext Preprocessor). Shouldn't his be in bold at the beginning at the article instead of in the middle? CarnivorousBunny talk • contribs 14:09, 20 April 2014 (UTC)
has anyone else noticed that the hello world code doesn't work properly? Both Firefox and Chrome return:
Hello World
'; ?>
I'm not knowledgeable enough about PHP to fix even this error properly. -- Kwixtartpahtee ( talk) 23:05, 22 June 2014 (UTC)
helloworld.php
). Then type php -S localhost:8888
to start a server. Open your browser and go to localhost:8888/helloworld.php
and the code will then work.
Let99 (
talk)
06:24, 10 November 2014 (UTC)PHP always had variadic functions, at least since PHP4 days, with func_num_args() / func_get_arg() / func_get_args() / ... ( https://php.net/manual/en/function.func-num-args.php / https://php.net/manual/en/function.func-get-arg.php / https://php.net/manual/en/function.func-get-args.php ) Divinity76 ( talk) 10:50, 7 January 2015 (UTC)
when i use this connection to connect to the database it brigs me errors mysql_connect("localhost","root",""); mysql_select_db("pass"); — Preceding unsigned comment added by 197.232.26.250 ( talk) 06:19, 22 April 2015 (UTC)
Does anyone want to help modernize and expand the PHP syntax and semantics page? It's really bad at the moment. Let99 ( talk) 06:21, 10 November 2014 (UTC)