From: [EMAIL PROTECTED]
Operating system: Any
PHP version: Irrelevant
PHP Bug Type: Documentation problem
Bug description: parse_url() may return false not documented
Description:
parse_url() may return false if the url could not be parsed:
resource =
cem Fri Oct 7 04:17:42 2005 EDT
Modified files:
/phpdoc/en/reference/sdo/functions
SDO-DAS-DataFactory-addPropertyToType.xml
Log:
Signature change: optional parameters are now an array of key=value pairs
cem Fri Oct 7 05:43:27 2005 EDT
Added files:
/phpdoc/en/reference/sdo_das_xml/functions
SDO-DAS-XML-Document-getRootDataObject.xml
Removed files:
Hello guys,
I have a problem to mention - due to the fact that Data.BG (hosting the
bg2.php.net mirror) has shaped a great part of the bulgarian peering
providers (the reason for this is the silly war between the bulgarian
piracy content providers, one side of which is Data.BG) - it's almost
Petar Nedyalkov wrote:
Hello guys,
I have a problem to mention - due to the fact that Data.BG (hosting the
bg2.php.net mirror) has shaped a great part of the bulgarian peering
providers (the reason for this is the silly war between the bulgarian
piracy content providers, one side of which
cem Fri Oct 7 07:26:40 2005 EDT
Modified files:
/phpdoc/entitiesglobal.ent
Log:
Add urls for pecl4win
http://cvs.php.net/diff.php/phpdoc/entities/global.ent?r1=1.246r2=1.247ty=u
Index: phpdoc/entities/global.ent
diff -u phpdoc/entities/global.ent:1.246
On Friday 07 October 2005 14:23, Kouber Saparev wrote:
Petar Nedyalkov wrote:
Hello guys,
I have a problem to mention - due to the fact that Data.BG (hosting the
bg2.php.net mirror) has shaped a great part of the bulgarian peering
providers (the reason for this is the silly war between
cem Fri Oct 7 08:25:20 2005 EDT
Modified files:
/phpdoc/en/reference/sdo/functions
SDO-DAS-DataFactory-addPropertyToType.xml
Log:
Add change summary
cem Fri Oct 7 08:26:25 2005 EDT
Modified files:
/phpdoc/en/reference/sdoreference.xml
Log:
Update for 0.5.2 release
http://cvs.php.net/diff.php/phpdoc/en/reference/sdo/reference.xml?r1=1.15r2=1.16ty=u
Index: phpdoc/en/reference/sdo/reference.xml
diff
Hi,
Both of you can visit http://bg.php.net/my and set your prefered mirror,
instead of relying on the automatic redirection system.
BTW I have forwarded your letter to the bg2.php.net maintainer.
Goba
Kouber Saparev wrote:
Petar Nedyalkov wrote:
Hello guys,
I have a problem to mention -
Gabor Hojtsy wrote:
Hi,
Both of you can visit http://bg.php.net/my and set your prefered mirror,
instead of relying on the automatic redirection system.
BTW I have forwarded your letter to the bg2.php.net maintainer.
Goba
Yes,
We just saw what's happening in
Hi,
What is the process for documenting an extension that has moved from PHP
Core to PECL? I look after the ingres PECL extension and want to revise the
documentation with the new stuff that has gone in. Since the original PHP
Core extension was known as ingres_ii and the new extension is just
Hi Grant,
What is the process for documenting an extension that has moved from PHP
Core to PECL? I look after the ingres PECL extension and want to revise the
documentation with the new stuff that has gone in. Since the original PHP
Core extension was known as ingres_ii and the new extension
It depends on how fundamental the changes were. I don't know. If
function names, parameters, etc. drastically changed, then a new
extension documentation should be opened IMHO. Otherwise you can revise
the existing documentation. PECL extensions are documented in the PHP
manual.
There are new
Hi,
It depends on how fundamental the changes were. I don't know. If
function names, parameters, etc. drastically changed, then a new
extension documentation should be opened IMHO. Otherwise you can revise
the existing documentation. PECL extensions are documented in the PHP
manual.
There
It depends on how fundamental the changes were. I don't know. If
function names, parameters, etc. drastically changed, then a new
extension documentation should be opened IMHO. Otherwise you can
revise
the existing documentation. PECL extensions are documented in the
PHP
manual.
There
grantc Fri Oct 7 12:32:06 2005 EDT
Added files:
/phpdoc/en/reference/ingres-ii/functionsingres-cursor.xml
ingres-errno.xml
ingres-error.xml
You should document the availability of these, so that people will not
try to use them in previous versions.
Goba
Grant Croker wrote:
grantcFri Oct 7 12:25:32 2005 EDT
Modified files:
/phpdoc/en/reference/ingres-iiconstants.xml
Log:
Add new
grantc Fri Oct 7 12:59:35 2005 EDT
Modified files:
/phpdoc/en/reference/ingres-ii constants.xml
Log:
Clarified availability of new constants
http://cvs.php.net/diff.php/phpdoc/en/reference/ingres-ii/constants.xml?r1=1.4r2=1.5ty=u
Index:
Grant Croker wrote:
grantc Fri Oct 7 12:32:06 2005 EDT
Added files:
/phpdoc/en/reference/ingres-ii/functions ingres-cursor.xml
ingres-errno.xml
ingres-error.xml
ID: 26902
Updated by: [EMAIL PROTECTED]
Reported By: webmaster at bubbles dot co dot il
-Status: Assigned
+Status: Open
Bug Type: Documentation problem
Operating System: win32
PHP Version: Irrelevant
Assigned To: derick
New
conni Fri Oct 7 20:22:35 2005 EDT
Modified files:
/phpdoc/en/reference/ingres-ii/functionsingres-errsqlstate.xml
ingres-cursor.xml
ingres-errno.xml
Log:
wrong
Hi all
there are build errors in the oci8 and ssh2 functions:
oci.datatypes;
oci8/functions/oci-fetch-all.xml:91:19:E: character data is not
allowed here
oci8/functions/oci-fetch-array.xml:158:19:E: character data is not
allowed here
oci8/functions/oci-fetch-assoc.xml:30:19:E: character data
Grant Croker wrote:
grantc Fri Oct 7 12:59:35 2005 EDT
Modified files:
/phpdoc/en/reference/ingres-ii constants.xml
Log:
Clarified availability of new constants
That's not well-formed.
The document has some needless elements.
It's necessary to correct it
24 matches
Mail list logo
