On 4/28/10 4:45 PM, Sylvain Rabot wrote:
> Hi,
>
> The comment I'm about to make is behind the times, and, now, useless, I
> know, but I can't hold me.
>
> You chose for the namespace feature, a great feature besides, the
> backslash ?? really ?? Come on guys, among all the possibilities, you
> h
Lukas Kahwe Smith wrote:
> Finally optionally include in your vote if would like to see this feature
> added to 5.3.2 or if it should wait for the next minor/major version update
> instead.
+0 on version to include this in, sorry I forgot to include that in my vote.
Greg
--
PHP Internals - PH
Lukas Kahwe Smith wrote:
> So there are three approaches listed in the RFC:
> 1) http://wiki.php.net/rfc/autoload_include#proposal
> add a new alternative to include, which works the same except that for
> missing files it returns null and on success it returns the file location
> (unless the fil
Kalle Sommer Nielsen wrote:
> But what is every ones input on the matter of attempting to boost
> PHP6's development? I'm willing to give my part in whatever I can to
> help getting up on the feet to get this ball rolling.
Hi,
As someone who has successfully ported a rather complex extension (ph
Lukas Kahwe Smith wrote:
>
> On 11.11.2009, at 11:44, Mikko Koppanen wrote:
>
>> On Wed, Nov 11, 2009 at 10:00 AM, Lukas Kahwe Smith
>> wrote:
>>>
>>> On 11.11.2009, at 01:50, Greg Beaver wrote:
>>>
>>>> if (can_include($file)) {
>&
Stanislav Malyshev wrote:
> Hi!
>
>> A good point. Fortunately, most streams do store the filename in the
>> stream struct, so this would still probably be possible in the majority
>> of cases. If not available, the original requested filename is used
>> (the one from the fopen call), so opcode c
Stanislav Malyshev wrote:
> Hi!
>
>>> This would break security distinction between file ops and include ops,
>>> when URLs are allowed for open but not include.
>
> Additional thing - it probably would be a problem for bytecode caches,
> since they'd have to:
> a. watch all file opens, in case som
Stanislav Malyshev wrote:
> Hi!
>
>> Alternatively include() could be extended to allow resources, so the
>> above would turn info
>>
>> if ($fp = @fopen($file, 'r', true)) {
>> include($fp);
>> fclose($fp);
>> }
>
> This would break security distinction between file ops and include ops,
Derick Rethans wrote:
> And the suggestion? Yet another ini setting (some even advocate making
> it INI_SYSTEM, which is obviously totally wacko)... This idea is an
> ostrich method.
Derick,
I'm only trying to suggest ways of fixing problems, calling them
"obviously wacko" is useless. I don't g
Ilia Alshanetsky wrote:
>
> On 24-Aug-09, at 6:54 PM, Greg Beaver wrote:
>>
>> 2) as long as the patch does not break any backwards compatibility
>> (error logging still works as it always did independent of error_mask,
>> user error handlers still get the same stu
Stanislav Malyshev wrote:
> Hi!
>
> I've implemented a patch that allows to "mask" certain types of errors -
> i.e. make PHP engine completely ignore them. Now even if the error is
> not reported, it passes full cycle through message string creation, all
> allocations on the way, etc. even though
Lothar Scholz wrote:
> Hello Stanislav,
>
> Monday, August 17, 2009, 9:46:19 AM, you wrote:
>
> SM> Hi!
>
>>> A buggy implementation should solve as reference? Damn'd fucking
>>> college boys. This was an acceptable development method for PHP3.
>
> SM> So, you came to PHP developers list to cal
Ben Scholzen 'DASPRiD' wrote:
>
> I tested libxml_use_internal_errors() with XMLReader now, and it doesn't
> really work as intended. When calling $reader->read(), and reaching an
> invalid node, there is in fact the error stored in libxml_get_errors(),
> but PHP additionally still throws a "parse
Hi,
I just committed an enhancement to pyrus designed for PHP extension
authors (pecl and core), details in this commit:
http://svn.php.net/viewvc/pear2/Pyrus_Developer/trunk/src/Pyrus/Developer/PackageFile/Commands.php?r1=286823&r2=286822&pathrev=286823
Basically, it's a single command that mir
Antony Dovgal wrote:
> On 01.08.2009 03:46, Greg Beaver wrote:
>
>> Hi,
>>
>> Finally found the problem in run-tests crashing, turns out it had
>> nothing to do with the zend engine. Now we can run tests in PHP 6
>> without random crashes.
>>
Hi,
Finally found the problem in run-tests crashing, turns out it had
nothing to do with the zend engine. Now we can run tests in PHP 6
without random crashes.
Greg
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hi,
After quite a while of trying, I've tracked down the problem that is
causing occasional segfaults in run-tests.php in PHP 6.
Basically, here's what happens:
on line 1652, we call system_with_timeout() to run the test, passing in
a CV ($cmd) containing the command line to execute to run the t
Hi,
I've fixed almost all of the issues with ext/phar in PHP 6, including
the re-generation of phar.phar, and so I re-enabled it in php-src/trunk.
I need a little help with a couple of the failing tests.
phar_oo_009.phpt fails because SPL's CSV iteration does not return the
last element on a lin
Hi,
In PHP 6, is there a reason all of the keys in $_SERVER are binary
except for PHP_SELF, which is unicode?
Thanks,
Greg
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hi,
README.UNICODE still talks about the unicode semantics switch, it
probably needs updating.
Greg
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Johannes Schlüter wrote:
> On Fri, 2009-07-24 at 15:00 -0400, Gwynne Raskind wrote:
>> And I'm happy to announce that this is now fixed; creation of tags is
>> now allowed. This comes alongside a bit of an overhaul of the entire
>> set of hook scripts. See http://news.php.net/php.cvs/59765 if y
Matteo Beccati wrote:
> Lukas Kahwe Smith wrote:
>
>> On 17.07.2009, at 03:04, Johannes Schlüter wrote:
>>
>>
>>> On Thu, 2009-07-16 at 18:20 -0500, Greg Beaver wrote:
>>>
>>>> I'd like to consider instead using svn:externa
Johannes Schlüter wrote:
> On Thu, 2009-07-16 at 18:20 -0500, Greg Beaver wrote:
>
>> I'd like to consider instead using svn:externals to pull in PEAR stuff
>> directly from a STABLE branch from somewhere in the pear/ hierarchy.
>> This would allow us over at
Pierre Joye wrote:
> hi,
>
> On Fri, Jul 17, 2009 at 1:20 AM, Greg Beaver wrote:
>
>> Hi,
>>
>> I'd like to start a discussion on php-src/pear and how we can manage it
>> better for PHP 5.3, and to discuss the future of PEAR in PHP.
>>
>> Fi
Hi,
I'd like to start a discussion on php-src/pear and how we can manage it
better for PHP 5.3, and to discuss the future of PEAR in PHP.
First, take note that both internals@ and pear-dev@ are copied on this
email.
For some background, currently the pear components are dynamically added
to a ch
Rasmus Lerdorf wrote:
> One of the benefits of svn is that we can do cross-branch commit pretty
> easily now and thus avoid multiple similar commits with annoying MFH/MFB
> commit log messages that are hard to track.
>
> Please don't attempt to check out all of php/php-src or pecl. I made
> the m
Stanislav Malyshev wrote:
> Hi!
>
>> 2) use cast syntax
>>
>> function (int $integerObject) {}
>> function ((int) $actualInteger) {}
>>
>> The tradeoff here is an intellectual one: (int) means something
>> different in a method signature than what it means in regular PHP code.
>
> Actually, it mean
Hi,
It is important to realize that the sole question here is what kind of
type hinting to implement. Any technical problems can be resolved with
some trade-offs.
There are a couple of approaches that come to mind.
1) make all type hints slightly slower (double lexing, once as T_STRING,
and the
Hannes Magnusson wrote:
> On Thu, Jul 9, 2009 at 04:50, Greg Beaver wrote:
>
>> The disadvantages are obvious: everyone has to have an account and give
>> their email address to report a bug. The advantages are also obvious:
>>
>
> I *hate* when I am requi
Richard Lynch wrote:
> On Tue, July 7, 2009 12:54 pm, Philip Olson wrote:
>> - Reclassification : Discuss how we handle this, like should old/new
>> lists both receive emails?
>
> Both lists should receive reclassifaction notification, and nothing
> more, imho.
>
>> - Consider different captcha (
Pierre Joye wrote:
> On Wed, Jul 8, 2009 at 1:04 AM, Greg Beaver wrote:
>
>
>> P.S. pecl for windows support is not in pyrus yet, since pecl4win is
>> completely defunct and there's no alternative.
>>
>
> You mean no support in general for binary p
Hi,
Pyrus is within inches of its first alpha release, and as such I want to
run the new features that affect PECL developers and consumers by those
folks who are affected by them.
Pyrus requires PHP 5.3.0 or newer, and is a dramatic leap forward from
the PEAR Installer.
Relevant docs to PECL ar
Paul Biggar wrote:
> On Tue, Jul 7, 2009 at 6:41 PM, Lukas Kahwe Smith wrote:
>> B) foo($bar);
>> function bar((int) $bar) {}
>>
>> What am I really saying with B)?
>> I don't care what you give me, I am going to use it as an int anyways?
>
> Exactly. Very simple. I would phrase it as "I'll accept
Christian Schneider wrote:
> Stan Vassilev wrote:
>>> +1 if the object type hint is change to use T_CLASS so we don't break
>>> every external package using "Object" as a base class.
>>> http://www.google.com/codesearch?as_q=class\s%2Bobject&btnG=Search+Code&hl=en&as_lang=php&as_license_restrict=i&
Stan Vassilev wrote:
>> +1 if the object type hint is change to use T_CLASS so we don't break
>> every external package using "Object" as a base class.
>>
>> http://www.google.com/codesearch?as_q=class\s%2Bobject&btnG=Search+Code&hl=en&as_lang=php&as_license_restrict=i&as_license=&as_package=&as_fi
Ilia Alshanetsky wrote:
> Last week or so there was a fairly detailed discussion on the internals
> list regarding type hinting based on my original patch. Since then the
> patch has been revised to address the major concerns that were
> identified (breakage of binary compatibility) as well extende
troels knak-nielsen wrote:
> On Thu, Jul 2, 2009 at 4:47 PM, Edward Z. Yang wrote:
>> Excerpts from troels knak-nielsen's message of Thu Jul 02 10:14:18 -0400
>> 2009:
>>> I would have expected the second call to __construct() to yield an error.
>> Why should it? Especially since this is idiomatic
Sebastian Bergmann wrote:
> Greg Beaver schrieb:
>> First, add "-drequire_hash=0" to go-pear.bat as a temporary fix for
>> those who already have PHP 5.3.0, and the permanent fix is to
>> re-generate the go-pear.phar on a machine with ext/phar installed.
Christian Weiske wrote:
> Hi,
>
>
> Several users reported that the windows package of php 5.3 does not work with
> the phar:
> - http://pastebin.com/d79a424b3
> - http://pastebin.com/d49c8cc02
>
> phar "C:\Users\Sebastian Bergmann\php\PEAR\go-pear.phar" does not have a
> signature
> Warning: req
Hi,
Are there any resources that summarize the internal differences in the
unicode implementation (things like zend_u_hash_*, how to do strcmp()
with IS_UNICODE zvals, etc.)?
Also, since this is for ext/phar, I need to be able to convert to/from
unicode to binary easily (is this just changing the
Rasmus Lerdorf wrote:
> And 10 years ago I'd be hacking on this for the next 3 hours, but right
> now I am spending the next 3 hours picking up Carl from Lego Camp and
> taking him to his piano lesson...
What, no cello lesson?
Greg
--
PHP Internals - PHP Runtime Development Mailing List
To uns
Scott MacVicar wrote:
> If we're freezing some more after this release for the SVN conversion
> then we could have a pretty cold branch for another week or so.
>
> As I've already said, I agree with only allow verified bug fixes by
> Johannes into 5.3.0. it's this extra bureaucracy that is gettin
Lukas Kahwe Smith wrote:
>
> On 25.06.2009, at 00:12, Greg Beaver wrote:
>
>> cellogWed Jun 24 22:12:47 2009 UTC
>>
>> Modified files: (Branch: PHP_5_3)
>>/php-srcNEWS
>>/php-src/ext/phar/pharpharcommand.inc
>> L
Hi,
I just discovered two critical errors in tar's signature verification
handling that affects archives signed with an openssl signature. The
attached patch fixes these issues, and adds a test for the openssl
functionality (this slipped through the cracks somehow).
This is an important iss
jvlad wrote:
>> Hi,
>>
>> Thanks. The line in question is the first line of the generated
>> (non-phar) phar.php script which is the foreach line in:
>>
>> > foreach (array("SPL", "Reflection", "Phar") as $ext) {
>> if (!extension_loaded($ext)) {
>> echo "$argv[0] requires PHP extension $ext.\n"
>
jvlad wrote:
>> can you run the custom gdb dumpbt so we can see which line of
>> install-pear-nozlib.phar is triggering the error?
>>
>
> (gdb) dump_bt executor_globals.current_execute_data
> [0x00861cc0] ???
> /export/home/jvlad/php/php5.3-200906221030/ext/phar/phar.php:10
Hi,
Thanks. The lin
Hannes Magnusson wrote:
> Just by updating the UPGRADING file you will increase the chance of
> the feature actually making it to the end-user by 100%, and getting it
> documented "for free" by 75%. And as we all know, 82.5% of all stats
> are made up on the spot.
The best part is that 60% of the
jvlad wrote:
>> Hi,
>>
>> I just ran a make install of PHP 5.3 on Solaris 32-bit:
>>
>> cel...@t2000-010131:~/php5$ gcc -v
>> Reading specs from /usr/sfw/lib/gcc/sparc-sun-solaris2.11/3.4.3/specs
>> Configured with:
>> /gates/sfwnv/builds/sfwnv-gate/usr/src/cmd/gcc/gcc-3.4.3/configure
>> --prefix=/
jvlad wrote:
Generating phar.php
*** Error code 138
make: Fatal error: Command failed for target `ext/phar/phar.php'
>>> next run of "make install" produces:
>>>
>>> $ make install
>>> Generating phar.phar
>>> make: *** [ext/phar/phar.phar] Bus Error (core dumped)
>> System info
jvlad wrote:
>>> php5.3-200906221030 make produces suspecious output under FreeBSD
>>> 6/amd64:
>>>
>>> Generating phar.php
>>> Generating phar.phar
>>> pear: not found
>>>
>>> Pear package PHP_Archive or Archive.php class file not found.
>>> ^^
jvlad wrote:
> Did you hear about crashes under Solaris and MacOSX, and compiler
> failures
> under all *BSD systems?
> They were posted against RC3 and the problems are still the same in
> RC4.
We fixed several compile failures recently (both FreeBSD related and
GCC2
Hannes Magnusson wrote:
> On Tue, Jun 16, 2009 at 20:59, Greg Beaver wrote:
>
>> Lukas Kahwe Smith wrote:
>>
>>> 1) its not about "punishing", its about alerting people that they are
>>> relying on stuff that will go away
>>> 2) E_DE
Lukas Kahwe Smith wrote:
> 1) its not about "punishing", its about alerting people that they are
> relying on stuff that will go away
> 2) E_DEPRECATE is for development only and only as a check you enable
> now and then
> 3) its off in both of the php.ini's we will ship with 5.3
OK, then the UPGR
Daniel Convissor wrote:
> Folks:
>
>> I propose the following behavior: "Throw a deprecated warning unless
>> magic quotes are currently enabled and the
>> parameter is to disable them".
>
> The function is going away. A deprecated warning is necessary to alert
> people of this fact, no matter
Hi,
in PHP_5_3 if you're using set_magic_quotes_runtime(0), it raises an
E_DEPRECATED. I thought all that argument was resolved to only throw
E_DEPRECATED for set_magic_quotes_runtime(1)?
This is a major pain if magic_quotes are enabled and you need to turn
them off to do unserialize or serializ
Derick Rethans wrote:
> On Sun, 14 Jun 2009, Greg Beaver wrote:
>
>
>> I just updated cvs for my main test bed (my last full update was a
>> couple of weeks ago) and xdebug was no longer loaded. I had been
>> loading it via:
>>
>> zend_extension_debug=
Hi,
I just updated cvs for my main test bed (my last full update was a
couple of weeks ago) and xdebug was no longer loaded. I had been
loading it via:
zend_extension_debug=/usr/local/lib/php/extensions/debug-non-zts-20090115/xdebug.so
and all was fine (I have the debug build).
Today, it stopp
Christian Seiler wrote:
> Hi Greg,
>
>
>> (I meant commit when I said patch, sorry :)
>>
>> http://news.php.net/php.cvs/58696
>> and
>> http://news.php.net/php.cvs/58697
>>
>
> Thanks, looks fine to me. However, I noticed that closures don't work
> with spl_autoload_unregister() and spl_aut
Christian Seiler wrote:
> Hi Greg,
>
>> I can do it if someone can answer this question: how do closures
>> uniquely identify themselves? spl_autoload_register is mistakenly
>> treating all closures as if they were a single copy of the static method
>> "Closure::__invoke", and so only the first r
Mark Karpeles wrote:
> Hello,
>
> After extracting my freshly downloaded copy of PHP 5.3.0RC3, I decided
> to read NEWS and saw something that caught my attention:
>
> - Fixed isset() on sub-directories (isset("blah") if file "blah/foo.php"
> exists). (Greg)
>
> Derick agreed with me on the fa
Hi,
I didn't mark http://bugs.php.net/48541 as critical because it is not a
critical bug, but it is critical that this thing be fixed in PHP 5.3.
I can do it if someone can answer this question: how do closures
uniquely identify themselves? spl_autoload_register is mistakenly
treating all closur
I suppose it would help to see the patch, no?
Index: win32/build/Makefile
===
RCS file: /repository/php-src/win32/build/Makefile,v
retrieving revision 1.35.2.1.2.6.2.12
diff -u -r1.35.2.1.2.6.2.12 Makefile
--- win32/build/Makefile
Hi,
I have a working patch against mkdist.php, is it all right to commit?
Greg
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Pierre Joye wrote:
> On Wed, Jun 10, 2009 at 5:36 PM, Greg Beaver wrote:
>
>> Hi,
>>
>> I don't see an obvious way to build the phar.phar on windows.
>>
>> Can someone with knowledge of how configure.js works (i.e. a Pierre)
>> give me a tip on
Hi,
I don't see an obvious way to build the phar.phar on windows.
Can someone with knowledge of how configure.js works (i.e. a Pierre)
give me a tip on how to tell it to make phar.phar after building
Release_TS/php.exe or Debug_TS/php.exe?
Otherwise, it would also be easy to provide a simple scr
Guilherme Blanco wrote:
> Just 2 questions
>
> 1- Will it include new autoloader definition that standards group was
> talking about?
Hi,
I am not an official RM representative, the following is my opinion:
Not the slightest chance. It hasn't even been suggested to internals
yet and additi
Hannes Magnusson wrote:
> On Thu, Jun 4, 2009 at 14:31, Hannes Magnusson wrote:
>
>> On Thu, Jun 4, 2009 at 14:21, Hannes Magnusson wrote:
>>
>>> bjori Thu Jun 4 12:21:59 2009 UTC
>>>
>>> Modified files:
>>>/php-src/ext/phar/phar pharcommand.inc
>>> Log:
>>> Fixed cr
Hi,
How does one do the equivalent of Makefile.frag for the windows build?
Greg
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Andrei Zmievski wrote:
> Hannes Magnusson wrote:
>> I assume the names in parentheses are people who volunteered to do the
>> task, not whoever brought it up? (very ambitious crowd) :)
>
> Volunteered to do it or at least guide others.
I think some people were "volunteered" based on prior contrib
Johannes Schlüter wrote:
> Hi,
>
> what's the state of the phar command line tool on Windows? - I juat
> fetched a snapshot-zip and it was missing there, I remember some IRC
> discussion about some trouble as it's depending on the phar.phar being
> generated during the build.
>
> Does anybody have
Christopher Jones wrote:
>
>
> Greg Beaver wrote:
>> Hi,
>>
>> Could someone fix phpize to make it return 0 on success? It always
>> returns -1 when opened via proc_open(), which is exceedingly annoying
>> when you're trying to use it in a PHP script.
Hi,
Could someone fix phpize to make it return 0 on success? It always
returns -1 when opened via proc_open(), which is exceedingly annoying
when you're trying to use it in a PHP script.
Thanks,
Greg
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.
Kalle Sommer Nielsen wrote:
> kalle Thu May 7 03:14:07 2009 UTC
>
> Modified files: (Branch: PHP_5_3)
> /php-src UPGRADING
> Log:
> * use is a reserved keyword
Hi,
FYI, use has been a reserved keyword since the initial commit of
zend_language_parser.y in October
Hi,
I have just found a significant memory leak, but cannot get a truly
short reproducing script. I have opened a bug, but I wanted to make
sure this doesn't slip through the cracks since RC2 is slated for Tuesday.
http://bugs.php.net/bug.php?id=48141
is the bug. I don't have a clear idea
Hi,
I never do Makefile stuff, so I need someone who can tell me why this
blasted piece of scripting doesn't work:
@if test "a$(program_prefix)" != "a"; then \
PEAR_PREFIX = " -dp php_prefix=$(program_prefix)"; \
fi
@if test "a$(program_suffix)" != "a"; then \
PEAR_SUFFIX = " -ds php_suf
hi,
I've noticed that it is very difficult to tell if your --CLEAN--
sections are actually working, so I wonder if it might be possible to
brainstorm ways of fixing this.
A couple of options come to mind that could be considered
- append this code to the end of the .clean.php file: ?> and captur
Stan Vassilev | FM wrote:
>
> Hi,
>
> There is a way to implement in some future release of PHP (without
> hurting performance), but it's not in the scope of 5.3.
>
> Each namespace should have a meta file listing all symbols present in
> it. The parser loads that static file at parse time and r
Lukas Kahwe Smith wrote:
>
> On 13.03.2009, at 00:39, Andrei Zmievski wrote:
>
>> Christian Schneider wrote:
>>> Things gettings reserved at a later stage (like originally keywords, now
>>> namespaces) can lead to a big deal of frustration. Therefore I think it
>>> is crucial to have a clear nami
Kalle Sommer Nielsen wrote:
> Hi Greg
>
> 2009/3/27 Greg Beaver :
>
>> Pierre Joye wrote:
>>
>>
>>>> - php_phar.dll present as an option in php.ini but there is no need (causes
>>>> confusion)
>>>>
>&g
Pierre Joye wrote:
>> - php_phar.dll present as an option in php.ini but there is no need (causes
>> confusion)
>
> Will be change when we are sure of the built type (builtin or shared)
What is the debate? Whether windows build should match unix build?
Greg
--
PHP Internals - PHP Runtime Dev
Jeremy wrote:
> Is there any way to access the parse tree of a PHP file from within PHP?
>
> I'm trying to write a code-checking utility to find namespace-related
> problems in code and alert me to them. Specifically:
>
> namespace foo\bar;
>
> function foobar()
> {
> try
> {
>
Lukas Kahwe Smith wrote:
>
> On 13.03.2009, at 00:39, Andrei Zmievski wrote:
>
>> Christian Schneider wrote:
>>> Things gettings reserved at a later stage (like originally keywords, now
>>> namespaces) can lead to a big deal of frustration. Therefore I think it
>>> is crucial to have a clear nami
Olivier Doucet wrote:
> Hi,
>
>
>> not sure if this was mentioned on the general list but, i believe what
>> youre describing is documented in the manual under php5 classes/objects ->
>> "the basics":
>>
>> http://www.php.net/manual/en/language.oop5.basic.php
>>
>> $this is a reference to the cal
Stanislav Malyshev wrote:
> Hi!
>
>> That said: On the wiki is a list of open items
>> http://wiki.php.net/todo/php53#next_release_beta2rc1
>
> I don't think #21 there is a bug - AFAIK client of get_class_name is
> supposed to free it - which happens automatically if this is assigned to
> zval, b
David M. Patterson wrote:
> I'm having a curious problem with my extension.
> I just moved to PHP 5.3-200903031530, made various changes as appropriate
> and successfully built it.
> Running php -i generates the expected output, including all of the stuff
> from my extension.
> The odd thing is th
zoe wrote:
>
>> Hi Zoe,
>>
>> Is there documentation on this change?
> Hi Greg - you mean the change I made to the phpinfo.phpt test? If so I
> changed it because it was failing and should not have been. Or do you
> mean changes to run-tests.php options?
I meant to run-tests.php.
>> I'm finding i
Zoe Slattery wrote:
> zoe Wed Mar 4 10:23:01 2009 UTC
>
> Modified files: (Branch: PHP_5_3)
> /php-src/ext/standard/tests/general_functions phpinfo.phpt
> Log:
> fixed test
>
> http://cvs.php.net/viewvc.cgi/php-src/ext/standard/tests/general_functions/phpi
Igor Feghali wrote:
> Hello Greg,
>
> AIX 5.3.0.0, PPC 64bit:
>
> 297 passed
> 214 skipped
>
> I am doing a second run right now to see if something goes different.
> Please let me know if you want the test log as well.
Hi Igor,
You can cut down on the skipped tests by building bz2, zlib, and
Kalle Sommer Nielsen wrote:
>>> Phar::getSupportedSignatures()
>>> [C:\php\src\ext\phar\tests\phar_get_supported_signatures_002.phpt]
>> This one is perplexing - I wonder if you have built ext/hash statically
>> or as a .dll? The phar ext is not detected ext/hash, but the test is
>> not skipping
hi Kalle,
Thank you very much for your work on this, it is much appreciated.
Sorry for the delay in replying, I have been out of town for a while.
Kalle Sommer Nielsen wrote:
> Hi Greg
>
> 2009/2/21 Greg Beaver :
>> Hi,
>>
>> [snip]
>
> Good work!
>
>
Pierre Joye wrote:
> Hi,
>
> What's about adding what screan (http://pecl.php.net/scream) to the
> standard PHP? Everyone needs it and it should be possible to do that
> without having to install an extension.
>
> Comments/objections?
If it can be done easily and unobtrusively to existing code,
Hi,
As PHP has the good fortune of being blessed with Scott MacVicar who
connected me with the ppc64 test machine provided by IBM and the sparc
machine provided by Sun through David Soria-Parra (thank you thank you
thank you), phar has now been verified as working in the following
configurations t
Eric Stewart wrote:
> We seem to have a split opinion on what the production INI value for
> allow_call_time_pass_reference should be.
>
> As I understand it, this does not enable or disable the ability to pass
> references at call time. It only enables or disables PHP's warnings about
> this beha
Hi,
I just noticed that this bug I opened
http://bugs.php.net/bug.php?id=45327&edit=1 is still sitting there.
It's easy to reproduce, and easy to fix, but seems to have slipped
between the cracks.
Thanks,
Greg
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: h
Hi,
While tracking down a problem in one of phar's tests, I found what might
be a problem in RecursiveDirectoryIterator's handling of flags. Here is
a crude patch demonstrating the issue, and wondering if this is
something to be concerned about. Basically, we're mixing long and int,
which c
Hannes Magnusson wrote:
> I still find Phar way to dangerous to _enable by default_ and I
> still do not think you are *fit* to handle such extension. (Yes, I did
> indeed say it. And I will not apologize for it. I really don't.)
>
ok. :]
> You have your own agenda (just like everyone else),
Hannes Magnusson wrote:
> On Sat, Feb 14, 2009 at 16:25, Greg Beaver wrote:
>
>> Hannes Magnusson wrote:
>>
>>> On Thu, Feb 5, 2009 at 22:32, Greg Beaver wrote:
>>>
>>>
>>>> I really don't give a crap. Change it if y
Stanislav Malyshev wrote:
> Hi!
>
>> http://bugs.php.net/bug.php?id=46984 - E_STRICT
>
> I think overriding foo($x) with foo($x, $y) - with both parameters
> required - leads to calls to foo with one argument be wrong for child -
> thus violating LSP and warranting E_STRICT.
I agree. If $y were
Lukas Kahwe Smith wrote:
> Hi,
>
> I also just reopened:
> http://bugs.php.net/bug.php?id=46026
>
> Not sure if Greg has time ..
Actually, this was more complex than originally stated, in that this
code is incorrect:
if (SUCCESS == zend_hash_find(HASH_OF(filterparams), "concatenated",
sizeof("c
Lukas Kahwe Smith wrote:
> Hi,
>
> I also just reopened:
> http://bugs.php.net/bug.php?id=46026
>
> Not sure if Greg has time ..
Anyone can do this, the 3 lines that need removal are correct, I simply
forgot about it at commit time, and for the last erm, several months :)
Greg
--
PHP Inte
1 - 100 of 378 matches
Mail list logo
