[PHP-BUG] Bug #60439 [NEW]: curl_copy_handle segfault when used with CURLOPT_PROGRESSFUNCTION

2011-12-03 Thread pierr...@php.net
From: 
Operating system: Any
PHP version:  5.3.8
Package:  cURL related
Bug Type: Bug
Bug description:curl_copy_handle segfault when used with 
CURLOPT_PROGRESSFUNCTION

Description:

The curl_copy_handle function don't work when used with
CURLOPT_PROGRESSFUNCTION

Test script:
---
http://www.php.net');
curl_setopt($ch, CURLOPT_NOPROGRESS, 0);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
curl_setopt($ch, CURLOPT_PROGRESSFUNCTION, function() { });
$ch2 = curl_copy_handle($ch);
echo curl_exec($ch);
unset($ch);
echo curl_exec($ch2);

Expected result:

No segault

Actual result:
--
Segfault

-- 
Edit bug report at https://bugs.php.net/bug.php?id=60439&edit=1
-- 
Try a snapshot (PHP 5.4):
https://bugs.php.net/fix.php?id=60439&r=trysnapshot54
Try a snapshot (PHP 5.3):
https://bugs.php.net/fix.php?id=60439&r=trysnapshot53
Try a snapshot (trunk):  
https://bugs.php.net/fix.php?id=60439&r=trysnapshottrunk
Fixed in SVN:
https://bugs.php.net/fix.php?id=60439&r=fixed
Fixed in SVN and need be documented: 
https://bugs.php.net/fix.php?id=60439&r=needdocs
Fixed in release:
https://bugs.php.net/fix.php?id=60439&r=alreadyfixed
Need backtrace:  
https://bugs.php.net/fix.php?id=60439&r=needtrace
Need Reproduce Script:   
https://bugs.php.net/fix.php?id=60439&r=needscript
Try newer version:   
https://bugs.php.net/fix.php?id=60439&r=oldversion
Not developer issue: 
https://bugs.php.net/fix.php?id=60439&r=support
Expected behavior:   
https://bugs.php.net/fix.php?id=60439&r=notwrong
Not enough info: 
https://bugs.php.net/fix.php?id=60439&r=notenoughinfo
Submitted twice: 
https://bugs.php.net/fix.php?id=60439&r=submittedtwice
register_globals:
https://bugs.php.net/fix.php?id=60439&r=globals
PHP 4 support discontinued:  
https://bugs.php.net/fix.php?id=60439&r=php4
Daylight Savings:https://bugs.php.net/fix.php?id=60439&r=dst
IIS Stability:   
https://bugs.php.net/fix.php?id=60439&r=isapi
Install GNU Sed: 
https://bugs.php.net/fix.php?id=60439&r=gnused
Floating point limitations:  
https://bugs.php.net/fix.php?id=60439&r=float
No Zend Extensions:  
https://bugs.php.net/fix.php?id=60439&r=nozend
MySQL Configuration Error:   
https://bugs.php.net/fix.php?id=60439&r=mysqlcfg



Bug #60809 [PATCH]: TRAITS - PHPDoc Comment Style Bug

2012-01-19 Thread pierr...@php.net
Edit report at https://bugs.php.net/bug.php?id=60809&edit=1

 ID: 60809
 Patch added by: pierr...@php.net
 Reported by:micronix at gmx dot net
 Summary:TRAITS - PHPDoc Comment Style Bug
 Status: Critical
 Type:   Bug
 Package:*General Issues
 Operating System:   Windows
 PHP Version:5.4.0RC5
 Block user comment: N
 Private report: N

 New Comment:

The following patch has been added/updated:

Patch Name: 60809.diff
Revision:   1327025994
URL:
https://bugs.php.net/patch-display.php?bug=60809&patch=60809.diff&revision=1327025994


Previous Comments:

[2012-01-19 23:49:26] g...@php.net

Micronix was just a bit sloppy with typos etc.
I tested on a trunk from 14th of Jan.:

//doc.php
hello_world;
  }
}


[2012-01-19 23:43:54] s...@php.net

Could you post what's in your doctest.php exactly?


[2012-01-19 18:48:32] g...@php.net

I can confirm that.

smarr:~/svn/trunk$ sapi/cli/php  doctest.php 
[Thu Jan 19 19:45:13 2012]  Script:  'doctest.php'
---
/Users/smarr/Projects/PHP-Traits/svn/trunk/Zend/zend_compile.c(131) : Block 
0x1007c60e8 status:
Beginning:  Cached
Freed (invalid)
Start:  OK
  End:  OK
---


Looks like zend_destroy_property_info thinks it should free something, which 
might 
already have been freed.

Won't have time to look into that before the weekend.
Sorry.


[2012-01-19 18:41:14] micronix at gmx dot net

Description:

Hello,

if you created in an separated file a trait with phpdoc inside. The apache 
server reset the connection immediatly.

Test script:
---
/// Example.php
class Example
   use ExampleTrait;

   public function __construct()
   {
   echo $this->hello_world;
   }
}
/// END OF Example.php

/// ExampleTrait.php
trait ExampleTrait {
/**
 *
 */
public $hello_world = 'hello World ^^';
}
/// END OF ExampleTrait.php

Expected result:

The Apache server can not load the output of the page.
the connection was reset while the page was loading.







-- 
Edit this bug report at https://bugs.php.net/bug.php?id=60809&edit=1


Bug #60809 [PATCH]: TRAITS - PHPDoc Comment Style Bug

2012-01-19 Thread pierr...@php.net
Edit report at https://bugs.php.net/bug.php?id=60809&edit=1

 ID: 60809
 Patch added by: pierr...@php.net
 Reported by:micronix at gmx dot net
 Summary:TRAITS - PHPDoc Comment Style Bug
 Status: Critical
 Type:   Bug
 Package:*General Issues
 Operating System:   Windows
 PHP Version:5.4.0RC5
 Assigned To:pierrick
 Block user comment: N
 Private report: N

 New Comment:

The following patch has been added/updated:

Patch Name: bug60809.phpt
Revision:   1327027197
URL:
https://bugs.php.net/patch-display.php?bug=60809&patch=bug60809.phpt&revision=1327027197


Previous Comments:

[2012-01-20 02:32:52] larue...@php.net

ah, you are right, ingore my noise :)


[2012-01-20 02:28:53] pierr...@php.net

I can do it like that yes. I'll just have to declare the variable inside the 
loop 
to make sure the doc_comment is reinitialized and NULL if no doc_comment is 
there.


[2012-01-20 02:26:32] larue...@php.net

pierrick, I suggest doing like:
char *doccomment = NULL;

if () {
   doccomment = estrndup();
}

thanks :)


[2012-01-20 02:26:31] larue...@php.net

pierrick, I suggest doing like:
char *doccomment = NULL;

if () {
   doccomment = estrndup();
}

thanks :)


[2012-01-20 02:21:52] pierr...@php.net

Problem is because zend_do_traits_property_binding use zend_declare_property_ex 
without doing a estrndup of the doc_comment. I attached a patch please Stas or 
dsp confirm that I can commit it :)




The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at

https://bugs.php.net/bug.php?id=60809


-- 
Edit this bug report at https://bugs.php.net/bug.php?id=60809&edit=1


Req #61602 [PATCH]: Allow access to name of constant used as default value

2012-04-02 Thread pierr...@php.net
Edit report at https://bugs.php.net/bug.php?id=61602&edit=1

 ID: 61602
 Patch added by: pierr...@php.net
 Reported by:sebast...@php.net
 Summary:Allow access to name of constant used as default
 value
 Status: Open
 Type:   Feature/Change Request
 Package:Reflection related
 Operating System:   Irrelevant
 PHP Version:5.4Git-2012-04-02 (Git)
 Block user comment: N
 Private report: N

 New Comment:

The following patch has been added/updated:

Patch Name: getDefaultValueConstantName.diff
Revision:   1333412604
URL:
https://bugs.php.net/patch-display.php?bug=61602&patch=getDefaultValueConstantName.diff&revision=1333412604


Previous Comments:

[2012-04-02 14:34:44] der...@php.net

It's definitely possible, I've just added something like this to VLD: 
https://github.com/derickr/vld/commit/f22862bfa8620780906f0e692f929a543264b5f8


[2012-04-02 14:14:16] sebast...@php.net

Description:

When a constant is used for the default value of an optional parameter, the 
Reflection API (tries to) resolve(s) the constant to its value and then returns 
it as the default value.

In addition, I would like to have two additional methods in ReflectionParameter 
that expose 1) whether or not a default value "is a" constant and 2) the name 
of the constant.

In the example below, I am using temporary names ("defaultValueIsConstant" and 
"getDefaultValueConstantName") for these two methods because I cannot think of 
sensible method names right now.

Test script:
---
getParameters();

foreach ($p as $_p) {
var_dump($_p->getDefaultValue());

if ($_p->defaultValueIsConstant()) {
var_dump($_p->getDefaultValueConstantName());
}
}

Expected result:

string(3) "..."
string(9) "self::bar"

Actual result:
--
string(3) "..."






-- 
Edit this bug report at https://bugs.php.net/bug.php?id=61602&edit=1


Bug #51094 [PATCH]: parse_ini_file() with INI_SCANNER_RAW cuts a value that includes a semi-colon

2012-06-06 Thread pierr...@php.net
Edit report at https://bugs.php.net/bug.php?id=51094&edit=1

 ID: 51094
 Patch added by: pierr...@php.net
 Reported by:viaujoc at videotron dot ca
 Summary:parse_ini_file() with INI_SCANNER_RAW cuts a value
 that includes a semi-colon
 Status: Open
 Type:   Bug
 Package:Filesystem function related
 PHP Version:*
 Block user comment: N
 Private report: N

 New Comment:

The following patch has been added/updated:

Patch Name: bug51094.diff
Revision:   1339002022
URL:
https://bugs.php.net/patch-display.php?bug=51094&patch=bug51094.diff&revision=1339002022


Previous Comments:

[2011-09-25 10:27:16] paj...@php.net

It is clearly a parsing error as the ; is part of a quoted string.

It also works with php.ini so it may be possible to get that work with other 
ini 
as well (while the code is different...)


[2010-02-20 20:00:14] viaujoc at videotron dot ca

This change in the behavior of parse_ini_file() is not documented in either the 
documentation page for the function or the "Backward Incompatible Changes" from 
"Migrating from PHP 5.2.x to PHP 5.3.x".

I also hope that the updated documentation promised in bug #47703 will be 
published soon.


[2010-02-20 10:54:50] j...@php.net

1. There is no such thing as raw scanning in PHP 5.2
2. This is exactly how it's supposed to work. The ; is still comment even in 
the raw mode. All other chars are considered just chars.
3. In PHP 5.3 the backslash inside double quotes is considered escape char. No 
bug here either. Use single quotes instead.


[2010-02-19 22:10:16] viaujoc at videotron dot ca

Description:

When using parse_ini_file() function with $scanner_mode=INI_SCANNER_RAW, any 
semi-colon (;) in the value is seen as the end of the value, even if it is 
enclosed in quotes.

The behavior of parse_ini_file() in PHP 5.3 with either $scanner_mode at RAW or 
NORMAL cannot reproduce the  behavior of PHP 5.2.

Reproduce code:
---
test.ini:
[TheSection]
MyKey="my;value\$"

example.php:


Expected result:

array(1) {
  ["TheSection"]=>
  array(1) {
["MyKey"]=>
string(10) "my;value\$"
  }
}

Actual result:
--
In PHP 5.2 (without the $scanner_mode parameter in parse_ini_file()):
array(1) {
  ["TheSection"]=>
  array(1) {
["MyKey"]=>
string(10) "my;value\$"
  }
}
(the value is returned exactly as it appears in test.ini)

In PHP 5.3 (with $scanner_mode=INI_SCANNER_RAW):
array(1) {
  ["TheSection"]=>
  array(1) {
["MyKey"]=>
string(3) ""my"
  }
}
(notice that everything after the semi-colon has been truncated and the quote 
as the first character of the string)

In PHP 5.3 (with $scanner_mode=INI_SCANNER_NORMAL):
array(1) {
  ["TheSection"]=>
  array(1) {
["MyKey"]=>
string(9) "my;value$"
  }
}
(notice the missing backslash (\) between the "e" and "$")






-- 
Edit this bug report at https://bugs.php.net/bug.php?id=51094&edit=1


Bug #51094 [PATCH]: parse_ini_file() with INI_SCANNER_RAW cuts a value that includes a semi-colon

2012-06-07 Thread pierr...@php.net
Edit report at https://bugs.php.net/bug.php?id=51094&edit=1

 ID: 51094
 Patch added by: pierr...@php.net
 Reported by:viaujoc at videotron dot ca
 Summary:parse_ini_file() with INI_SCANNER_RAW cuts a value
 that includes a semi-colon
 Status: Assigned
 Type:   Bug
 Package:Filesystem function related
 PHP Version:*
 Assigned To:pierrick
 Block user comment: N
 Private report: N

 New Comment:

The following patch has been added/updated:

Patch Name: bug51094.diff
Revision:   1339075946
URL:
https://bugs.php.net/patch-display.php?bug=51094&patch=bug51094.diff&revision=1339075946


Previous Comments:

[2012-06-06 17:06:30] pierr...@php.net

I'll soon have one last look to make sure this patch doesn't introduce any 
problem before committing it. But if someone else want to review it, any 
comments 
will be welcome.


[2012-06-06 17:00:22] pierr...@php.net

The following patch has been added/updated:

Patch Name: bug51094.diff
Revision:   1339002022
URL:
https://bugs.php.net/patch-display.php?bug=51094&patch=bug51094.diff&revision=1339002022


[2011-09-25 10:27:16] paj...@php.net

It is clearly a parsing error as the ; is part of a quoted string.

It also works with php.ini so it may be possible to get that work with other 
ini 
as well (while the code is different...)


[2010-02-20 20:00:14] viaujoc at videotron dot ca

This change in the behavior of parse_ini_file() is not documented in either the 
documentation page for the function or the "Backward Incompatible Changes" from 
"Migrating from PHP 5.2.x to PHP 5.3.x".

I also hope that the updated documentation promised in bug #47703 will be 
published soon.


[2010-02-20 10:54:50] j...@php.net

1. There is no such thing as raw scanning in PHP 5.2
2. This is exactly how it's supposed to work. The ; is still comment even in 
the raw mode. All other chars are considered just chars.
3. In PHP 5.3 the backslash inside double quotes is considered escape char. No 
bug here either. Use single quotes instead.




The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at

https://bugs.php.net/bug.php?id=51094


-- 
Edit this bug report at https://bugs.php.net/bug.php?id=51094&edit=1


Bug #54804 [PATCH]: __halt_compiler and imported namespaces

2011-05-19 Thread pierr...@php.net
Edit report at http://bugs.php.net/bug.php?id=54804&edit=1

 ID: 54804
 Patch added by: pierr...@php.net
 Reported by:vrai at moechofe dot com
 Summary:__halt_compiler and imported namespaces
 Status: Open
 Type:   Bug
 Package:Compile Failure
 Operating System:   Ubuntu 11.01 2.6.38-8-generic
 PHP Version:5.3.6
 Block user comment: N
 Private report: N

 New Comment:

The following patch has been added/updated:

Patch Name: bug_54804
Revision:   1305801994
URL:   
http://bugs.php.net/patch-display.php?bug=54804&patch=bug_54804&revision=1305801994


Previous Comments:

[2011-05-18 09:58:15] vrai at moechofe dot com

Description:

When importing namespace in a script using the __halt_compiler()
function, the imported script must use the same type of declaration
(bracketed namespace or unbracketed namespace).



Test script:
---
a.php



http://bugs.php.net/bug.php?id=54804&edit=1


Bug #54804 [PATCH]: __halt_compiler and imported namespaces

2011-05-19 Thread pierr...@php.net
Edit report at http://bugs.php.net/bug.php?id=54804&edit=1

 ID: 54804
 Patch added by: pierr...@php.net
 Reported by:vrai at moechofe dot com
 Summary:__halt_compiler and imported namespaces
 Status: Assigned
 Type:   Bug
 Package:Compile Failure
 Operating System:   Ubuntu 11.01 2.6.38-8-generic
 PHP Version:5.3.6
 Assigned To:pierrick
 Block user comment: N
 Private report: N

 New Comment:

The following patch has been added/updated:

Patch Name: bug_54804_with_test.diff
Revision:   1305803069
URL:   
http://bugs.php.net/patch-display.php?bug=54804&patch=bug_54804_with_test.diff&revision=1305803069


Previous Comments:

[2011-05-19 12:57:15] paj...@php.net

Can you add a test case please?


[2011-05-19 12:46:34] pierr...@php.net

The following patch has been added/updated:

Patch Name: bug_54804
Revision:   1305801994
URL:   
http://bugs.php.net/patch-display.php?bug=54804&patch=bug_54804&revision=1305801994


[2011-05-18 09:58:15] vrai at moechofe dot com

Description:

When importing namespace in a script using the __halt_compiler()
function, the imported script must use the same type of declaration
(bracketed namespace or unbracketed namespace).



Test script:
---
a.php



http://bugs.php.net/bug.php?id=54804&edit=1


Bug #55086 [PATCH]: Namespace alias does not work inside trait's use block

2011-07-01 Thread pierr...@php.net
Edit report at https://bugs.php.net/bug.php?id=55086&edit=1

 ID: 55086
 Patch added by: pierr...@php.net
 Reported by:andrey dot garbuz at gmail dot com
 Summary:Namespace alias does not work inside trait's use
 block
 Status: Open
 Type:   Bug
 Package:Scripting Engine problem
 Operating System:   Fedora 14
 PHP Version:5.4SVN-2011-06-30 (SVN)
 Block user comment: N
 Private report: N

 New Comment:

The following patch has been added/updated:

Patch Name: bug55086.phpt
Revision:   1309552383
URL:
https://bugs.php.net/patch-display.php?bug=55086&patch=bug55086.phpt&revision=1309552383


Previous Comments:

[2011-06-30 07:47:02] andrey dot garbuz at gmail dot com

Description:

Namespace aliases do not work only inside trait's use block. If provide fully 
qualified namespace then example works fine:
class A {
  use T1, T2 {
\N1\T1::hello insteadof \N1\T2;
  }
}

Test script:
---
hello(), PHP_EOL;

}

Expected result:

hello from t1

Actual result:
--
PHP Fatal error:  Trait 'T1' not found in test_script.php on line 24






-- 
Edit this bug report at https://bugs.php.net/bug.php?id=55086&edit=1


Req #55247 [PATCH]: Parser problem with static calls using string method name

2011-07-26 Thread pierr...@php.net
Edit report at https://bugs.php.net/bug.php?id=55247&edit=1

 ID: 55247
 Patch added by: pierr...@php.net
 Reported by:gehrig at teqneers dot de
 Summary:Parser problem with static calls using string method
 name
 Status: Open
 Type:   Feature/Change Request
 Package:*General Issues
 Operating System:   Darwin 10.8.0
 PHP Version:5.3.6
 Block user comment: N
 Private report: N

 New Comment:

The following patch has been added/updated:

Patch Name: 55247.diff
Revision:   1311742018
URL:
https://bugs.php.net/patch-display.php?bug=55247&patch=55247.diff&revision=1311742018


Previous Comments:

[2011-07-22 18:53:20] fel...@php.net

It isn't supposed to work, so not a bug.

Changed to feature request.


[2011-07-20 05:55:26] gehrig at teqneers dot de

Description:

PHP allows to call instance methods using the {} syntax together with a string 
- 
such as $obj->{'my-method'} for example. This allows developers to call methods 
whose names are not valid PHP method names.

The same does not work with static method calls. 

Test script:
---
method();
$test->$method();
$test->{'method'}();

Test::method();
Test::$method();
Test::{'method'}();


Expected result:

method
method
method
method
method
method

Actual result:
--
PHP Parse error:  syntax error, unexpected '{', expecting T_STRING or 
T_VARIABLE 
or '$' in Untitled.php on line 21






-- 
Edit this bug report at https://bugs.php.net/bug.php?id=55247&edit=1


Bug #50816 [PATCH]: Using class constants in array definition fails (works in PHP_5_2)

2011-07-28 Thread pierr...@php.net
Edit report at https://bugs.php.net/bug.php?id=50816&edit=1

 ID: 50816
 Patch added by: pierr...@php.net
 Reported by:spasic dot dejan at yahoo dot de
 Summary:Using class constants in array definition fails 
 (works in PHP_5_2)
 Status: Verified
 Type:   Bug
 Package:Scripting Engine problem
 Operating System:   *
 PHP Version:5.3, 6
 Block user comment: N
 Private report: N

 New Comment:

The following patch has been added/updated:

Patch Name: 50816.diff
Revision:   1311900851
URL:
https://bugs.php.net/patch-display.php?bug=50816&patch=50816.diff&revision=1311900851


Previous Comments:

[2010-01-22 13:45:10] j...@php.net

Works as expected in PHP 5.2, fails with 5.3 and above.


[2010-01-21 22:14:08] spasic dot dejan at yahoo dot de

Description:

Some lines of code is worth a thousand words

Reproduce code:
---
class Foo {
  const ONE = 1;
  const TWO = 1;

  public static $mapWithConst = array(self::ONE => 'one', self::TWO => 'two',);

  public static $mapWithoutConst = array(17 => 'one', 17 => 'two',);
}

$mapWithConst = array(1 => 'one', 1 => 'two',);

$mapWithoutConst = array(Foo::ONE => 'one', Foo::TWO => 'two',);

var_dump(Foo::$mapWithConst);
var_dump(Foo::$mapWithoutConst);
var_dump($mapWithConst);
var_dump($mapWithoutConst);


Expected result:

array(1) {
  [1]=>
  string(3) "two"
}
array(1) {
  [17]=>
  string(3) "two"
}
array(1) {
  [1]=>
  string(3) "two"
}
array(1) {
  [1]=>
  string(3) "two"
}


Actual result:
--
array(1) {
  [1]=>
  string(3) "one"   // ???
}
array(1) {
  [17]=>
  string(3) "two"
}
array(1) {
  [1]=>
  string(3) "two"
}
array(1) {
  [1]=>
  string(3) "two"
}







-- 
Edit this bug report at https://bugs.php.net/bug.php?id=50816&edit=1


Bug #50816 [PATCH]: Using class constants in array definition fails (works in PHP_5_2)

2011-07-28 Thread pierr...@php.net
Edit report at https://bugs.php.net/bug.php?id=50816&edit=1

 ID: 50816
 Patch added by: pierr...@php.net
 Reported by:spasic dot dejan at yahoo dot de
 Summary:Using class constants in array definition fails 
 (works in PHP_5_2)
 Status: Verified
 Type:   Bug
 Package:Scripting Engine problem
 Operating System:   *
 PHP Version:5.3, 6
 Block user comment: N
 Private report: N

 New Comment:

The following patch has been added/updated:

Patch Name: 50816-2.diff
Revision:   1311912867
URL:
https://bugs.php.net/patch-display.php?bug=50816&patch=50816-2.diff&revision=1311912867


Previous Comments:

[2011-07-29 00:54:11] pierr...@php.net

The following patch has been added/updated:

Patch Name: 50816.diff
Revision:   1311900851
URL:
https://bugs.php.net/patch-display.php?bug=50816&patch=50816.diff&revision=1311900851


[2010-01-22 13:45:10] j...@php.net

Works as expected in PHP 5.2, fails with 5.3 and above.


[2010-01-21 22:14:08] spasic dot dejan at yahoo dot de

Description:

Some lines of code is worth a thousand words

Reproduce code:
---
class Foo {
  const ONE = 1;
  const TWO = 1;

  public static $mapWithConst = array(self::ONE => 'one', self::TWO => 'two',);

  public static $mapWithoutConst = array(17 => 'one', 17 => 'two',);
}

$mapWithConst = array(1 => 'one', 1 => 'two',);

$mapWithoutConst = array(Foo::ONE => 'one', Foo::TWO => 'two',);

var_dump(Foo::$mapWithConst);
var_dump(Foo::$mapWithoutConst);
var_dump($mapWithConst);
var_dump($mapWithoutConst);


Expected result:

array(1) {
  [1]=>
  string(3) "two"
}
array(1) {
  [17]=>
  string(3) "two"
}
array(1) {
  [1]=>
  string(3) "two"
}
array(1) {
  [1]=>
  string(3) "two"
}


Actual result:
--
array(1) {
  [1]=>
  string(3) "one"   // ???
}
array(1) {
  [17]=>
  string(3) "two"
}
array(1) {
  [1]=>
  string(3) "two"
}
array(1) {
  [1]=>
  string(3) "two"
}







-- 
Edit this bug report at https://bugs.php.net/bug.php?id=50816&edit=1


Bug #50816 [PATCH]: Using class constants in array definition fails (works in PHP_5_2)

2011-07-29 Thread pierr...@php.net
Edit report at https://bugs.php.net/bug.php?id=50816&edit=1

 ID: 50816
 Patch added by: pierr...@php.net
 Reported by:spasic dot dejan at yahoo dot de
 Summary:Using class constants in array definition fails 
 (works in PHP_5_2)
 Status: Verified
 Type:   Bug
 Package:Scripting Engine problem
 Operating System:   *
 PHP Version:5.3, 6
 Block user comment: N
 Private report: N

 New Comment:

The following patch has been added/updated:

Patch Name: 50816-2.diff
Revision:   1311949824
URL:
https://bugs.php.net/patch-display.php?bug=50816&patch=50816-2.diff&revision=1311949824


Previous Comments:

[2011-07-29 04:14:28] pierr...@php.net

The following patch has been added/updated:

Patch Name: 50816-2.diff
Revision:   1311912867
URL:
https://bugs.php.net/patch-display.php?bug=50816&patch=50816-2.diff&revision=1311912867


[2011-07-29 00:54:11] pierr...@php.net

The following patch has been added/updated:

Patch Name: 50816.diff
Revision:   1311900851
URL:
https://bugs.php.net/patch-display.php?bug=50816&patch=50816.diff&revision=1311900851


[2010-01-22 13:45:10] j...@php.net

Works as expected in PHP 5.2, fails with 5.3 and above.


[2010-01-21 22:14:08] spasic dot dejan at yahoo dot de

Description:

Some lines of code is worth a thousand words

Reproduce code:
---
class Foo {
  const ONE = 1;
  const TWO = 1;

  public static $mapWithConst = array(self::ONE => 'one', self::TWO => 'two',);

  public static $mapWithoutConst = array(17 => 'one', 17 => 'two',);
}

$mapWithConst = array(1 => 'one', 1 => 'two',);

$mapWithoutConst = array(Foo::ONE => 'one', Foo::TWO => 'two',);

var_dump(Foo::$mapWithConst);
var_dump(Foo::$mapWithoutConst);
var_dump($mapWithConst);
var_dump($mapWithoutConst);


Expected result:

array(1) {
  [1]=>
  string(3) "two"
}
array(1) {
  [17]=>
  string(3) "two"
}
array(1) {
  [1]=>
  string(3) "two"
}
array(1) {
  [1]=>
  string(3) "two"
}


Actual result:
--
array(1) {
  [1]=>
  string(3) "one"   // ???
}
array(1) {
  [17]=>
  string(3) "two"
}
array(1) {
  [1]=>
  string(3) "two"
}
array(1) {
  [1]=>
  string(3) "two"
}







-- 
Edit this bug report at https://bugs.php.net/bug.php?id=50816&edit=1


[PHP-BUG] Req #60329 [NEW]: New keep_alive option

2011-11-18 Thread pierr...@php.net
From: 
Operating system: 
PHP version:  5.4.0RC1
Package:  SOAP related
Bug Type: Feature/Change Request
Bug description:New keep_alive option

Description:

When using the SoapClient you may sometime have this error :

SoapClient::__doRequest(): send of 776 bytes failed with errno=32 Broken
pipe

The problem is that some servers that you're calling are closing the
connection 
after some time. To fix this problem you need to use the "Connection:
close" 
HTTP Header. The only way to do it currently is to use a stream_context
with the 
1.0 HTTP protocol version :

$socket_context = stream_context_create(
   array('http' => array('protocol_version'  => 1.0))
);
$soapClient = new \SOAPClient($serviceUrl, array('stream_context' => 
$socket_context));

It would be nice to have a new option "keep_alive" that you can disable
like 
this :

$soapClient = new \SOAPClient(ServiceUrl, array('keep_alive' => false));


Test script:
---
$soapClient = new \SOAPClient(ServiceUrl, array('keep_alive' => false));

Expected result:

Request with "Connection: close" header

Actual result:
--
Request with "Connection: Keep-alive" header

-- 
Edit bug report at https://bugs.php.net/bug.php?id=60329&edit=1
-- 
Try a snapshot (PHP 5.4):
https://bugs.php.net/fix.php?id=60329&r=trysnapshot54
Try a snapshot (PHP 5.3):
https://bugs.php.net/fix.php?id=60329&r=trysnapshot53
Try a snapshot (trunk):  
https://bugs.php.net/fix.php?id=60329&r=trysnapshottrunk
Fixed in SVN:
https://bugs.php.net/fix.php?id=60329&r=fixed
Fixed in SVN and need be documented: 
https://bugs.php.net/fix.php?id=60329&r=needdocs
Fixed in release:
https://bugs.php.net/fix.php?id=60329&r=alreadyfixed
Need backtrace:  
https://bugs.php.net/fix.php?id=60329&r=needtrace
Need Reproduce Script:   
https://bugs.php.net/fix.php?id=60329&r=needscript
Try newer version:   
https://bugs.php.net/fix.php?id=60329&r=oldversion
Not developer issue: 
https://bugs.php.net/fix.php?id=60329&r=support
Expected behavior:   
https://bugs.php.net/fix.php?id=60329&r=notwrong
Not enough info: 
https://bugs.php.net/fix.php?id=60329&r=notenoughinfo
Submitted twice: 
https://bugs.php.net/fix.php?id=60329&r=submittedtwice
register_globals:
https://bugs.php.net/fix.php?id=60329&r=globals
PHP 4 support discontinued:  
https://bugs.php.net/fix.php?id=60329&r=php4
Daylight Savings:https://bugs.php.net/fix.php?id=60329&r=dst
IIS Stability:   
https://bugs.php.net/fix.php?id=60329&r=isapi
Install GNU Sed: 
https://bugs.php.net/fix.php?id=60329&r=gnused
Floating point limitations:  
https://bugs.php.net/fix.php?id=60329&r=float
No Zend Extensions:  
https://bugs.php.net/fix.php?id=60329&r=nozend
MySQL Configuration Error:   
https://bugs.php.net/fix.php?id=60329&r=mysqlcfg



[PHP-BUG] Req #60360 [NEW]: Add a phpinfo() somewhere on GCOV

2011-11-22 Thread pierr...@php.net
From: 
Operating system: 
PHP version:  Irrelevant
Package:  Unknown/Other Function
Bug Type: Feature/Change Request
Bug description:Add a phpinfo() somewhere on GCOV

Description:

It would be nice to have a phpinfo() somewhere on the gcov server to know
which 
version of a specific lib is used.


-- 
Edit bug report at https://bugs.php.net/bug.php?id=60360&edit=1
-- 
Try a snapshot (PHP 5.4):
https://bugs.php.net/fix.php?id=60360&r=trysnapshot54
Try a snapshot (PHP 5.3):
https://bugs.php.net/fix.php?id=60360&r=trysnapshot53
Try a snapshot (trunk):  
https://bugs.php.net/fix.php?id=60360&r=trysnapshottrunk
Fixed in SVN:
https://bugs.php.net/fix.php?id=60360&r=fixed
Fixed in SVN and need be documented: 
https://bugs.php.net/fix.php?id=60360&r=needdocs
Fixed in release:
https://bugs.php.net/fix.php?id=60360&r=alreadyfixed
Need backtrace:  
https://bugs.php.net/fix.php?id=60360&r=needtrace
Need Reproduce Script:   
https://bugs.php.net/fix.php?id=60360&r=needscript
Try newer version:   
https://bugs.php.net/fix.php?id=60360&r=oldversion
Not developer issue: 
https://bugs.php.net/fix.php?id=60360&r=support
Expected behavior:   
https://bugs.php.net/fix.php?id=60360&r=notwrong
Not enough info: 
https://bugs.php.net/fix.php?id=60360&r=notenoughinfo
Submitted twice: 
https://bugs.php.net/fix.php?id=60360&r=submittedtwice
register_globals:
https://bugs.php.net/fix.php?id=60360&r=globals
PHP 4 support discontinued:  
https://bugs.php.net/fix.php?id=60360&r=php4
Daylight Savings:https://bugs.php.net/fix.php?id=60360&r=dst
IIS Stability:   
https://bugs.php.net/fix.php?id=60360&r=isapi
Install GNU Sed: 
https://bugs.php.net/fix.php?id=60360&r=gnused
Floating point limitations:  
https://bugs.php.net/fix.php?id=60360&r=float
No Zend Extensions:  
https://bugs.php.net/fix.php?id=60360&r=nozend
MySQL Configuration Error:   
https://bugs.php.net/fix.php?id=60360&r=mysqlcfg



Bug #55540 [PATCH]: no curl_share? nice...

2011-11-22 Thread pierr...@php.net
Edit report at https://bugs.php.net/bug.php?id=55540&edit=1

 ID: 55540
 Patch added by: pierr...@php.net
 Reported by:jorsmal at gmail dot com
 Summary:no curl_share? nice...
 Status: Assigned
 Type:   Bug
 Package:cURL related
 Operating System:   any
 PHP Version:Irrelevant
 Assigned To:pierrick
 Block user comment: N
 Private report: N

 New Comment:

The following patch has been added/updated:

Patch Name: curl_share.diff
Revision:   1322032272
URL:
https://bugs.php.net/patch-display.php?bug=55540&patch=curl_share.diff&revision=1322032272


Previous Comments:

[2011-09-09 00:50:32] ka...@php.net

Well you are most welcome to provide a patch for exposing curl_share(), be 
constructive instead ;-)


[2011-08-30 16:46:16] jorsmal at gmail dot com

Description:

using ubuntu lucid with php 5.3.2.1, but i could be using any os with any php 
version.

php-curl extension does not include curl_share functions?

the goal is for developers to use pecl-http? some developers may just use 
something else than php...







-- 
Edit this bug report at https://bugs.php.net/bug.php?id=55540&edit=1


Bug #63512 [PATCH]: parse_ini_file() with INI_SCANNER_RAW removes quotes from value.

2012-11-14 Thread pierr...@php.net
Edit report at https://bugs.php.net/bug.php?id=63512&edit=1

 ID: 63512
 Patch added by: pierr...@php.net
 Reported by:arjen at react dot com
 Summary:parse_ini_file() with INI_SCANNER_RAW removes quotes
 from value.
 Status: Assigned
 Type:   Bug
 Package:Filesystem function related
 Operating System:   All
 PHP Version:5.3.18
 Assigned To:pierrick
 Block user comment: N
 Private report: N

 New Comment:

The following patch has been added/updated:

Patch Name: 63512-v2.diff
Revision:   1352952773
URL:
https://bugs.php.net/patch-display.php?bug=63512&patch=63512-v2.diff&revision=1352952773


Previous Comments:

[2012-11-14 15:19:00] larue...@php.net

pierrick, do you have time to look at this? thanks :)


[2012-11-14 12:14:29] arjen at react dot com

Warning: expected result and actual result are swapped! :o


[2012-11-14 11:53:41] arjen at react dot com

Description:

An option value containing a constant followed by an quoted string is 
transformed 
in constant string: CONSTANT "string" => CONSTANT string

This is broken since 5.3.15/5.4.5, probably by fixing 
https://bugs.php.net/bug.php?id=51094

See http://3v4l.org/VkQgF

And INI_SCANNER_RAW isn't really raw, as quotes are removed anyway.
For value = "string" I would expect array('value' => '"string"') as result, so 
one can differentiate between value = "CONSTANT" and value = CONSTANT.

Test script:
---

  string(3) "123"
  ["constant"]=>
  string(12) "INSTALL_ROOT"
  ["quotedString"]=>
  string(6) "string"
  ["a"]=>
  string(16) "INSTALL_ROOT waa"
  ["b"]=>
  string(12) "INSTALL_ROOT"
  ["c"]=>
  string(16) "waa INSTALL_ROOT"
  ["d"]=>
  string(25) "INSTALL_ROOT INSTALL_ROOT"
}

Actual result:
--
array(7) {
  ["int"]=>
  string(3) "123"
  ["constant"]=>
  string(12) "INSTALL_ROOT"
  ["quotedString"]=>
  string(6) "string"
  ["a"]=>
  string(18) "INSTALL_ROOT "waa""
  ["b"]=>
  string(12) "INSTALL_ROOT"
  ["c"]=>
  string(18) ""waa" INSTALL_ROOT"
  ["d"]=>
  string(27) "INSTALL_ROOT "INSTALL_ROOT""
}

even better:

array(7) {
  ["int"]=>
  string(3) "123"
  ["constant"]=>
  string(12) "INSTALL_ROOT"
  ["quotedString"]=>
  string(6) ""string""
  ["a"]=>
  string(18) "INSTALL_ROOT "waa""
  ["b"]=>
  string(12) "INSTALL_ROOT"
  ["c"]=>
  string(18) ""waa" INSTALL_ROOT"
  ["d"]=>
  string(27) "INSTALL_ROOT "INSTALL_ROOT""
}






-- 
Edit this bug report at https://bugs.php.net/bug.php?id=63512&edit=1


Bug #63512 [PATCH]: parse_ini_file() with INI_SCANNER_RAW removes quotes from value.

2012-11-14 Thread pierr...@php.net
Edit report at https://bugs.php.net/bug.php?id=63512&edit=1

 ID: 63512
 Patch added by: pierr...@php.net
 Reported by:arjen at react dot com
 Summary:parse_ini_file() with INI_SCANNER_RAW removes quotes
 from value.
 Status: Assigned
 Type:   Bug
 Package:Filesystem function related
 Operating System:   All
 PHP Version:5.3.18
 Assigned To:laruence
 Block user comment: N
 Private report: N

 New Comment:

The following patch has been added/updated:

Patch Name: 63512-v3.diff
Revision:   1352954789
URL:
https://bugs.php.net/patch-display.php?bug=63512&patch=63512-v3.diff&revision=1352954789


Previous Comments:

[2012-11-15 04:45:54] pierr...@php.net

I created a patch for this bug (which also fix #62884).

Could you make a quick code review before I commit it ? 

Thanks


[2012-11-15 04:12:53] pierr...@php.net

The following patch has been added/updated:

Patch Name: 63512-v2.diff
Revision:   1352952773
URL:
https://bugs.php.net/patch-display.php?bug=63512&patch=63512-v2.diff&revision=1352952773


[2012-11-14 15:19:00] larue...@php.net

pierrick, do you have time to look at this? thanks :)


[2012-11-14 12:14:29] arjen at react dot com

Warning: expected result and actual result are swapped! :o


[2012-11-14 11:53:41] arjen at react dot com

Description:

An option value containing a constant followed by an quoted string is 
transformed 
in constant string: CONSTANT "string" => CONSTANT string

This is broken since 5.3.15/5.4.5, probably by fixing 
https://bugs.php.net/bug.php?id=51094

See http://3v4l.org/VkQgF

And INI_SCANNER_RAW isn't really raw, as quotes are removed anyway.
For value = "string" I would expect array('value' => '"string"') as result, so 
one can differentiate between value = "CONSTANT" and value = CONSTANT.

Test script:
---

  string(3) "123"
  ["constant"]=>
  string(12) "INSTALL_ROOT"
  ["quotedString"]=>
  string(6) "string"
  ["a"]=>
  string(16) "INSTALL_ROOT waa"
  ["b"]=>
  string(12) "INSTALL_ROOT"
  ["c"]=>
  string(16) "waa INSTALL_ROOT"
  ["d"]=>
  string(25) "INSTALL_ROOT INSTALL_ROOT"
}

Actual result:
--
array(7) {
  ["int"]=>
  string(3) "123"
  ["constant"]=>
  string(12) "INSTALL_ROOT"
  ["quotedString"]=>
  string(6) "string"
  ["a"]=>
  string(18) "INSTALL_ROOT "waa""
  ["b"]=>
  string(12) "INSTALL_ROOT"
  ["c"]=>
  string(18) ""waa" INSTALL_ROOT"
  ["d"]=>
  string(27) "INSTALL_ROOT "INSTALL_ROOT""
}

even better:

array(7) {
  ["int"]=>
  string(3) "123"
  ["constant"]=>
  string(12) "INSTALL_ROOT"
  ["quotedString"]=>
  string(6) ""string""
  ["a"]=>
  string(18) "INSTALL_ROOT "waa""
  ["b"]=>
  string(12) "INSTALL_ROOT"
  ["c"]=>
  string(18) ""waa" INSTALL_ROOT"
  ["d"]=>
  string(27) "INSTALL_ROOT "INSTALL_ROOT""
}






-- 
Edit this bug report at https://bugs.php.net/bug.php?id=63512&edit=1