Sara Golemon wrote:
While it's technically safe to include user supplied data in
json_encode() serialized values. The fact that characters such as '
remain as is means there room for some as-yet unidentified problem
either in the browser's rendering or (more likely) elsewhere in one's
Richard Quadling wrote:
The idea of a major world player contributing to our lill' old PHP
sounds really exciting. The more the merrier, as long as the
peer-review process works (and it seems to have kept me out of the
core well enough!), let them come!
We welcome any and all contributions,
Stanislav Malyshev wrote:
I can't because I don't know of any successful vectors *currently*. I
also would have sworn that echoing htmlentified data was safeuntil
I came across a browser where it wasn't.
So that's what I wanted to understand, because if we add this feature,
we should
Alexey Zakhlestin wrote:
Is such filtering specific to JSON? Does it have some use out of JSON-context?
Maybe it would be better to provide a set of functions for encoding
characters into '\u'-entities? (similiar to htmlentities,
htmlspecialchars)
because if we speak of 'theoretical'
Alexey Zakhlestin wrote:
On 12/2/07, Rasmus Lerdorf [EMAIL PROTECTED] wrote:
The \u syntax is specific to JSON, yes.
\u syntax is specific to javascripts string literals, regular
expressions and identifiers[1]
And JSON is not the only way to deliver data into javascript. Manual
approaches
I have some new code for it. I'll try to find some time to update it
over the next couple of weeks.
-Rasmus
Silvano Girardi Jr wrote:
Gentleman,
This morning I went to see Lukas speaking at the Brazilian PHP Conference
and he mentioned http://people.php.net
He said that it started with the
Nah, it does more than that.
David Coallier wrote:
You mean something like http://pear.php.net/map ?
On Dec 3, 2007 12:44 PM, Rasmus Lerdorf [EMAIL PROTECTED] wrote:
I have some new code for it. I'll try to find some time to update it
over the next couple of weeks.
-Rasmus
Silvano
Stanislav Malyshev wrote:
Stuff like this often isn't completely deterministic. The attack
vectors will move around and new ones will be discovered but since the
syntax Sara is proposing is completely valid JSON it gives people
another tool. Documenting specific attack vectors is useful too,
Antony Dovgal wrote:
On 04.12.2007 18:31, Andi Gutmans wrote:
You may be right longer term but shorter term I still believe there may be
stability issues with this patch some of which we haven't figured out.
Although we did testing and found crash bugs I wouldn't trust our level of
testing
[EMAIL PROTECTED] wrote:
I think having it configurable is a must. Turning it on / off via a compile
flag will not suit everyone.
Looking at the code, that isn't really possible. You could have a
switch to turn off the collection, but that won't get you your
performance back. To avoid the
Stanislav Malyshev wrote:
1. Always compile it in but leave undocumented #ifdefs in place for
performance freaks. Those same performance freaks aren't going to care
about the binary compatibility issue since they are the same people who
build all their own stuff.
Note that breaking BC is
Keryx Web wrote:
Alexey Zakhlestin skrev:
I think I understand what the use-case is…
If the browser doesn't know anything about script tag, it is
supposed to interpret it's contents as html… In which case, html-tags
which appear in javascript code will actually become active ones
And in
Making sure it is ifdef'ed nicely would let us leave it in CVS until we
get it right and if it causes problems for some people they have a way
to build PHP without it. And yes, that means their build won't be
binary compatible, which is fine and no different from them trying to
revert the patch
PHP is first and foremost a Web scripting language. Everything we do
and every decision is based on that. For every feature the first
question you need to ask yourselves is:
Will this make it easier or harder for the average PHP user to
build a web app? And if it makes it harder, is the
Stefan Esser wrote:
Be conservative in what you do; be liberal in what you accept from
others.
You hopefully realise that this is exactly the opposite of your earlier
opinion that ext/filter should be used to block everything and let only
harmless data through. And only have raw data on
Lukas Kahwe Smith wrote:
On Jan 10, 2008, at 1:05 PM, Joe Orton wrote:
I'm not sure I find the logic of the but the system-provided data will
become stale arguments convincing; systems which are left unmaintained
by the administrators will have old versions of software on; that's a
given. I
And my stance hasn't changed either:
http://marc.info/?l=php-internalsm=117060700805108w=2
Andi Gutmans wrote:
Andi 2003:
http://www.mail-archive.com/internals@lists.php.net/msg03896.html
Andi's brain evolves 2007:
http://marc.info/?l=php-internalsm=117057393530217w=2
And today I'm
Johannes Schlüter wrote:
But well in my results I have a problem: For Rasmus's vote I've counted
a -1 while as such this syntax is appropriate I think has to be
counted as +1.
I don't understand how you interpreted my view as a -1. I'm somewhat
ambivalent about it, but I don't think it would
I don't disagree with this, and that is actually why I insisted on
having the unicode-semantics switch from the early days of the Unicode
discussions, so you can blame me, again, if you consider it a bad design
decision.
My take on it was that just about all ISPs would run with Unicode
Richard Lynch wrote:
On Wed, January 23, 2008 1:28 pm, Rasmus Lerdorf wrote:
I don't disagree with this, and that is actually why I insisted on
having the unicode-semantics switch from the early days of the Unicode
discussions, so you can blame me, again, if you consider it a bad
design
David Zülke wrote:
How about allowing bfoo in 5.3 (so people can start migrating their
code early) and making unicode strings default in PHP7? :D
That's been there for a very long time now.
-Rasmus
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit:
for.
-Rasmus
Andrei Zmievski wrote:
Did you mean to say can't make the default string IS_STRING? Because
that's the only reading that makes sense given the rest of the message.
-Andrei
Rasmus Lerdorf wrote:
If we get rid of the switch, then I agree that we can't make the default
string
Peter Brodersen wrote:
http://php.net/xml also documents this replacement:
==
If PHP encounters characters in the parsed XML document that can not be
represented in the chosen target encoding, the problem characters will be
demoted. Currently, this means that such characters are replaced by a
Greg Beaver wrote:
Dmitry Stogov wrote:
The feature is very useful, however, I agree, the syntax would be
better. :)
The current syntax:
$var = 'TEXT'
text
TEXT;
I would like to see nowdocs. The closest equivalent in another syntax I
can think of is xml's CDATA. Perhaps we can borrow
Greg Beaver wrote:
Marcus Boerger wrote:
Hello Scott,
actually it was a bug. We, sorry I, did not spot this in earlier versions.
Now saying you rely on a bug in PHP 5 to be able to execute PHP 4 code
simply does not work.
Hi Marcus,
How is forcing users to replace
Gregory Beaver wrote:
Anyone have experience with this and advice on what I need to upgrade?
It's normal. Create a suppression file and ignore those.
eg.
--gen-suppressions=yes
And it isn't PHP calls leaking. It's just the way libdl does stuff.
-Rasmus
--
PHP Internals - PHP Runtime
Cristian Rodriguez wrote:
2008/2/1, Marcus Boerger [EMAIL PROTECTED]:
- Fix callable/static mess, the following will now all result in a E_STRICT
. binding a dynamic function as a static callback
. static call of a dynamic function
. is_callable() on a static binding to a
Daniel Brown wrote:
On Feb 5, 2008 3:26 PM, Daniel Brown [EMAIL PROTECTED] wrote:
On Feb 5, 2008 3:23 PM, Pierre Joye [EMAIL PROTECTED] wrote:
Hi,
It seems that there is voices in favor of keeping the GPC related
functions in HEAD/php6 but returning always FALSE.
Personally
XX
Stanislav Malyshev wrote:
Hi!
This topic was already discussed here but never arrived to a conclusion,
so I will raise it again.
The Problem:
We have $_REQUEST superglobal, which is often used to abstract GET/POST
requests. However, in most cases we do not want GET/POST variables to
Jani Taskinen wrote:
On Wed, 2008-02-06 at 20:27 -0800, Rasmus Lerdorf wrote:
Stanislav Malyshev wrote:
Hi!
This topic was already discussed here but never arrived to a conclusion,
so I will raise it again.
The Problem:
We have $_REQUEST superglobal, which is often used to abstract GET
Jani Taskinen wrote:
On Thu, 2008-02-07 at 01:43 -0800, Rasmus Lerdorf wrote:
Jani Taskinen wrote:
On Wed, 2008-02-06 at 20:27 -0800, Rasmus Lerdorf wrote:
Stanislav Malyshev wrote:
The proposal(s):
1. One way to fix it is to create a new .ini request_order that would
control just _REQUEST
Larry Garfield wrote:
You also note that this mechanism has no runtime impact. That's unfortunate,
because I'd find the ability to add methods to an object at runtime
conditionally based on some other value far more useful in my work. :-)
Especially since, as above, there seems to be a
Marcus Boerger wrote:
Hello Stefan,
any dynamic aspect of a class has brought us to problems in inheritance
and required us to design the objct/compile model in a way that
inheritance often is done at run time. Imo traits are a way out of this.
In fact I'd love to issue a deprecated
Richard Lynch wrote:
On Mon, February 18, 2008 7:45 pm, Rasmus Lerdorf wrote:
The idea here is that we want to be able to cache opcodes, classes and
functions and optimize them out of the runtime context so the executor
can skip creating classes and functions on every single request. A
lot
till wrote:
Bjori just nailed it:
class foo { function foo() { echo 'foo'; } }
foo::foo();
It's some constructor BC thing.
I didn't think any of these changes were in the 5_2 tree at all. As far
as I am concerned the E_STRICT is for 5.3. We can't make a change like
this in a minor
Stanislav Malyshev wrote:
Hi!
be much easier, switching to re2c promises a much faster lexer.
Actually,
without any specific re2c optimizations we already get around a 20%
scanner
I think 20% faster is very cool.
However, as I understand re2c is not a standard tool found everywhere.
So
Philip Olson wrote:
On Mar 4, 2008, at 7:07 PM, Daniel Brown wrote:
On Tue, Mar 4, 2008 at 5:17 PM, Philip Olson [EMAIL PROTECTED]
wrote:
The Google Summer of Code sponsors students to work on Open Source
projects over each summer. This RFC introduces guidelines and goals
involving how
Marcus Boerger wrote:
Hello Stanislav,
Friday, March 14, 2008, 5:51:49 PM, you wrote:
But that means we are compiling inheritance when a file is loaded form
the cache. The goal should be to compiling inheritance when writing to
the opcode cache file. All we achieve here is a slow down. If
We are using setjmp(__bailout) in zend_try, but setjmp behaves
differently on BSD and Linux. POSIX doesn't specify whether the signal
mask should be saved or not for this call, so different operating
systems do different things here. I think it would be more consistent
if we used
Edward Z. Yang wrote:
Rasmus Lerdorf wrote:
exit_on_timeout patch
Hi Rasmus, I noticed that this patch modifies the Zend Engine API
slightly. Does this translate into any changes that need documentation
at php.net?
No, I don't think so. I checked all extensions in php cvs, including
Gwynne Raskind wrote:
My two US cents :).
On Mar 19, 2008, at 9:17 PM, Jani Taskinen wrote:
Here is a quick run down of some of the features of CMake and tools
associated with it:
• A single configure script that would be used regardless of the OS
• A much simpler scripting language
m4 is
Stanislav Malyshev wrote:
I see your point... but wouldn't it be better not to need that?
Johannes' idea seemed good to me, always assuming it's do-able.
Well, yes, it would indeed, but we have a lot of ?= templates now so
either we allow ?= on no-short-tags (if XML guys out there will be OK
Soenke Ruempler wrote:
Hi Rasmus,
On 03/23/2008 03:32 PM, Rasmus Lerdorf wrote:
This is what the filter extension is for. You should be working with
escaped data by default and only poke a hole in your data firewall in
the few places where you need to work with the raw data. Doing
Soenke Ruempler wrote:
Hi Rasmus,
On 03/23/2008 04:14 PM, Rasmus Lerdorf wrote:
It is, but it is magic_quotes done right. You apply a really strict
filter that makes your data safe for display and your backend by
default. The only place you can reliably do this this is at the point
Wietse Venema wrote:
Rasmus Lerdorf:
Soenke Ruempler wrote:
Hi Rasmus,
On 03/23/2008 03:32 PM, Rasmus Lerdorf wrote:
This is what the filter extension is for. You should be working with
escaped data by default and only poke a hole in your data firewall in
the few places where you need
Stefan Walk wrote:
Rasmus Lerdorf schrieb:
It is, but it is magic_quotes done right. You apply a really strict
filter that makes your data safe for display and your backend by
default. The only place you can reliably do this this is at the point
the data enters your system. Once
Stefan Walk wrote:
Rasmus Lerdorf schrieb:
The alternative of relying on the developer remembering to filter
simply doesn't work. Wietse's taint mode is another approach, but it
has performance implications.
As I said, when the backend does the escaping, you don't have to
remember
Edward Z. Yang wrote:
Rasmus Lerdorf wrote:
Well, I actually have years of experience taking apps and making them
run under my strict default filter. And it tends to not be very many
changes, if any at all. In the O'Reilly case it gets changed to
O#39;Reilly which for a pure web app is fine
Stefan Walk wrote:
Rasmus Lerdorf schrieb:
Well, I actually have years of experience taking apps and making them
run under my strict default filter. And it tends to not be very many
changes, if any at all. In the O'Reilly case it gets changed to
O#39;Reilly which for a pure web app is fine
Edward Z. Yang wrote:
Rasmus Lerdorf wrote:
Sure, although if you are going to store the raw, I think it is
pointless to store the escaped version.
Yeah, I was thinking more of escaping data that is computationally
expensive; such as bbcodes or wikitext = HTML.
I am not advocating storing
Stanislav Malyshev wrote:
Hi!
I believe, besides the apache SAPI and fcgi SAPI, LiteSpeed SAPI is
one of the top PHP SAPI being used in production environment. And
LiteSpeed SAPI has the combination of best performance, configuration
flexibility via .htaccess and enhanced security with
There is no bug here. Please read:
http://docs.sun.com/source/806-3568/ncg_goldberg.html
-Rasmus
Todd Ruth wrote:
I'm thinking there must be a bug in the heart of php
causing this. I'll debug it, but I haven't looked at
php source code in a few years and would like a tip as
to which files
Alain Williams wrote:
On Sat, Apr 26, 2008 at 05:11:29PM -0700, Chris Stockton wrote:
*cough* lambda *cough*
That would be nice, but the scoping of variables in PHP doesn't seem to
make that nice, the code below results in '' Undefined variable: aa ''
if I take the 'global' statement out, if
Stefan Walk wrote:
And you'll quickly see that the cast to string before comparision is a
bad idea, because:
$ php -dprecision=1 -r 'var_dump((string)1.4 == (string)1.1);'
bool(true)
Having display settings affect comparisions seems like a really bad idea
to me ;)
Yup, it would be a fatal
A bit of a messy patch in that it doesn't have a single top-level
directory, but after hacking it, it applied. For others testing this,
make sure you run ext/tokenizer/tokenizer_data_gen.sh and of course
genfiles with the latest re2c.
I'm still not getting something that works though.
He never asked.
Steph Fox wrote:
Hi Hannes,
CVS HEAD wasn't updated yet with the Windows build system because I was
waiting for re2c development to settle down first, given that there was
no re2c binary available that PHP could be built with at all for several
weeks.
But I agree with you,
Matt Wilmas wrote:
BTW, if I had karma for Zend stuff, I guess
I could fix Bugs #44681 and #44830
You already have Zend karma.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Can someone spot why this code
(tested in both 5.2.5 and 5.3)
?php
function curl($post) {
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, www.fdhfkdsslak.bogus);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
if($post) {
curl_setopt($ch, CURLOPT_POST, 1);
:04 AM, Rasmus Lerdorf [EMAIL PROTECTED] wrote:
start 326616
GET 327256
GET 327276
GET 327276
GET 327276
GET 327276
GET 327276
GET 327276
GET 327276
GET 327276
GET 327276
POST 327516
POST 327588
POST 327652
POST 327712
POST 327892
POST 328064
POST 328228
POST 328384
POST 328528
POST 328628
Cristian Rodríguez wrote:
Rasmus Lerdorf escribió:
Can someone spot why this code
(tested in both 5.2.5 and 5.3)
?php
function curl($post) {
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, www.fdhfkdsslak.bogus);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
if($post
Manuel Mausz wrote:
Rasmus Lerdorf wrote:
Note that you don't actually need to send the request. It looks like
repeatedly doing:
$ch = curl_init();
curl_setopt($ch, CURLOPT_POSTFIELDS, $args);
curl_close($ch);
Is enough to do it. Still looking at the code. Seems like
zend_llist_clean(ch
I think it is a bad idea to add functions for such a trivial math
operation. It's not like people who need to do this can't do it today,
and people who have already written code that needs it may very well
have created userspace functions with these exact names which means
their code will
Lars Strojny wrote:
[ forgot to sent that to the list ]
Hi Philip,
Am Dienstag, den 20.05.2008, 12:55 -0700 schrieb Philip Olson:
[...]
PHP 5.3 is approaching fast, so let's conclude our dealings with
magical quotes... this should be the last time. Please have a look at
the following RFC
Edward Z. Yang wrote:
I don't really care either way, but if it's a well known fact, might as
well stop trying. Does APC work on Windows? I recently submitted a patch
to fix the snaps.php.net compilation of APC, but for any non-trivial
script (interestingly enough, apc.php and and phpinfo()
Stanislav Malyshev wrote:
please add your votes
I'm +1.
I'm ok with it as well. Like I said over a year ago (*), it is a syntax
very familiar to web developers and it feels natural to most people.
(*) http://marc.info/?l=php-internalsm=117060700805108w=2
-Rasmus
--
PHP Internals - PHP
Antony Dovgal wrote:
On 28.05.2008 10:25, Stanislav Malyshev wrote:
Hi!
You do understand that you will not be able to use this syntax in
your products for at least next 5 years without rising min required
PHP version to the latest one, right?
That makes it even more useless.
That's great
Mike wrote:
In my opinion I don't think PHP would be where it is today if it wasn't
for being so easy to learn and use.
I attribute this directly to the fact that it didn't use a lot of
syntax sugar that is unreadable and can't be Googled for. You can't
Google [], and my guess is searching
Actually, checking through my group@ archive, I don't see 2 messages
from you. The only one I see from you is one from June 9 complaining
that your cvs account wasn't granted. I see that someone has approved
your account now.
-Rasmus
Antony Dovgal wrote:
On 11.06.2008 22:44, Baptiste
Pierre Joye wrote:
Hi Lukas,
On Sat, Jun 14, 2008 at 4:26 PM, Lukas Kahwe Smith [EMAIL PROTECTED] wrote:
These extension seem widely used enough that we have to make it an effort to
support them.
If it is so widely used, why noone complains about this removal? Why
there is nobody taking
Alexey Zakhlestin wrote:
On 6/22/08, David Coallier [EMAIL PROTECTED] wrote:
2008/6/21 Alexey Zakhlestin [EMAIL PROTECTED]:
I did curl for 5.3
I don't have karma.
You do now.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Derick Rethans wrote:
On Tue, 24 Jun 2008, Alexey Zakhlestin wrote:
On Tue, Jun 24, 2008 at 6:36 PM, Derick Rethans [EMAIL PROTECTED] wrote:
On Fri, 20 Jun 2008, Gregory Beaver wrote:
The user is obviously intentionally creating a DateTime class, and
doesn't care about the internal
Rui, thanks for your efforts on this. And yes, it would be really good
if you could encourage some people to write more tests for this feature.
We were completely lost in trying to maintain compatibility with this
because of the lack of tests and documentation.
Now we have something to go
Looking through the closures patch, I would tend to agree. GC has
certainly caused us way more headaches in APC-land than closures will,
from the looks of it.
-Rasmus
Dmitry Stogov wrote:
I don't see big problems with closures. The patch is simple and stable.
It's main part isolated in
Derick Rethans wrote:
On Mon, 7 Jul 2008, Marcus Boerger wrote:
how about this. We edit php_config.h to be version 4.4.8pl1. Then
provide a patch for download. All reasonable distributions will pick up
that patch anyway. But at least we didn't do a release as we promised, we
wouldn't.
Uh,
Derick Rethans wrote:
On Mon, 7 Jul 2008, Marcus Boerger wrote:
how about this. We edit php_config.h to be version 4.4.8pl1. Then
provide a patch for download. All reasonable distributions will pick up
that patch anyway. But at least we didn't do a release as we promised, we
wouldn't.
Uh,
Stanislav Malyshev wrote:
Hi!
I am proposing the following RFC to improve signal handling in the Zend
Engine:
http://wiki.php.net/rfc/zendsignals
Looks good. If ti works, I don't think we need two signal models - new
one would be OK. I'm not sure what happens with win32 though.
Note that
Amir Hardon wrote:
I've noticed a weird behavior when doing file access from PHP:
PHP seems to make an lstat call on each of the parent directories of the
accessed file, for example see this script:
?php
$fp=fopen(/var/www/metacafe/test,r);
fclose($fp);
?
When running with strace -e lstat I
Amir Hardon wrote:
On Tue, 2008-07-15 at 11:40 -0700, Rasmus Lerdorf wrote:
Amir Hardon wrote:
I've noticed a weird behavior when doing file access from PHP:
PHP seems to make an lstat call on each of the parent directories of the
accessed file, for example see this script:
?php
$fp
Lars Strojny wrote:
Hi Rasmus,
Am Dienstag, den 15.07.2008, 11:40 -0700 schrieb Rasmus Lerdorf:
[...]
That's a realpath() call and it should be getting cached by the realpath
cache, so if you are seeing these on every request, try increasing your
realpath_cache size in your .ini. Without
Arvids Godjuks wrote:
Hello.
I think this should be optimized.
I'm not an expert ofcourse, but as I understood there is only one case
witch need a special treatment - require/include _one when a file with
equal contents is included from different directories.
You can make a switch witch
Amir Hardon wrote:
On Wed, 2008-07-16 at 06:45 -0700, Rasmus Lerdorf wrote:
Arvids Godjuks wrote:
Hello.
I think this should be optimized.
I'm not an expert ofcourse, but as I understood there is only one case
witch need a special treatment - require/include _one when a file
Arvids Godjuks wrote:
Yesterday I made some tests on my site with strace to see how much lstat
I have and how can I optimize them. Well, I managed to get rid of them
almost at all, but now I have some questions about include_path and
including files based on current dir.
I have such structire
For the start of the string:
substr($haystack,0,strlen($needle)) == $needle
And for the end of the string:
substr($haystack,-strlen($needle)) == $needle
For case-insensitivity, just strtolower both.
Writing built-in functions for something that can be done with trivial
one-liners isn't
I agree that many existing functions can be implemented with a
combination of others, but in this case it is really just one call. The
strlen() call is almost free, and in many cases you wouldn't even use
it. If you are looking for .php files, for example:
if(str_endswith($path,'.php'))
On most requests we end up with a getcwd() followed by a chdir() to the
same directory and then a second chdir() to the same directory at the
end of the request:
getcwd(/var/www, 4095) = 14
chdir(/var/www) = 0
... request is processed ...
chdir(/var/www)
Brian Moon wrote:
Stan Vassilev | FM wrote:
I'm particularly for begins/endswith() function as I do this all over my
code and I'd appreciate the simplification and free extra performance.
I really don't mean to be rude here, but shorter and less typing !==
performance gain. The PHP string
Now that Subversion 1.5 has been out for a little while and it is at the
point where it might actually have some benefit to us, do we have some
volunteers who have some time to try converting over the repository and
all the post-commit and ACL rules from CVSROOT?
Talking to people here at
Gwynne Raskind wrote:
On Jul 24, 2008, at 8:05 PM, Rasmus Lerdorf wrote:
Now that Subversion 1.5 has been out for a little while and it is at
the point where it might actually have some benefit to us, do we have
some volunteers who have some time to try converting over the
repository and all
marius popa wrote:
On Fri, Jul 25, 2008 at 5:06 AM, Gwynne Raskind
[EMAIL PROTECTED] wrote:
At this point it's clear that moving from CVS to SVN for PHP has become a
more or less official project. As such, there is a new mailing list
isn't better to migrate to git or mercurial ?
Lukas Kahwe Smith wrote:
The git and hg integration with svn is also good so any developer who
prefers to have a local repository can very easily use either git or
hg and easily merge into the central svn repository.
However I think we should provide the infrastructure for developers to
setup
Chung-Yang(Kenneth) Lee wrote:
Most of the functionalities were done.
Users can now upload a file to get parsed and visualized from the
interface.
After the file is parsed, the interface will display information like
function names, total self cost in ms and by percentage, invocation count.
The
Could someone please fix this:
Generating phar.php
Generating phar.phar
Pear package PHP_Archive found: API Version: 1.0.0 (stable).
Pear package PHP_Archive or Archive.php class file not found.
clicommand.inc
directorygraphiterator.inc
directorytreeiterator.inc
invertedregexiterator.inc
Dmitry Stogov wrote:
I see several issues with the patch
1) It assumes that web server (and webserver extensions) won't setup any
signal handlers after PHP startup. This assumption may be wrong.
It may be. But there is really no way around that. That's why we
talked about having an
Johannes Schlüter wrote:
Hi,
On Wed, 2008-07-30 at 13:46 -0700, Tore B. Krudtaa wrote:
As most of you probably know Rasmus Lerdorf made som upload hooks
available in PHP 5.2 some long time back.
This was great news for those that wanted more control of uploads
and/or wanted to give real time
Jani Taskinen wrote:
-- Changed PCRE, Reflection and SPL extensions to always be enabled. (Marcus)
+- Changed PCRE, Reflection and SPL extensions to be always enabled. (Marcus)
That was amazingly pedantic, even for you Jani. Captain Kirk blasted
away the split infinitive rule when he decided
I think we either need to make clearstatcache() not affect the realpath
cache, or we should add an optional argument to it to specify whether or
not the realpath cache should be cleared as well.
The realpath cache makes a huge difference on includes and having the
cache blown away by a script
Johannes Schlüter wrote:
On Wed, 2008-08-06 at 21:00 +0200, Arnaud Le Blanc wrote:
btw. I just noticed chroot() calls this
realpath_cache_clean()..intentional?
I'd assume that, as /foo inside a chroot is different from /foo
outside...
Also some streams stuff uses the
Christian Stocker wrote:
Hi
Since quite some time (weeks), I have this very strange and annoying
include bug in 5.3-dev and now I think is the time to report it :)
The reproducable script is here:
http://trash.chregu.tv/include-bug.php.txt
In short, when I have
foo/alpha (empty)
Felipe Pena wrote:
Em Qui, 2008-08-07 às 20:55 +0200, Hannes Magnusson escreveu:
On Thu, Aug 7, 2008 at 20:20, Rasmus Lerdorf[EMAIL PROTECTED] wrote:
Christian Stocker wrote:
Hi
Since quite some time (weeks), I have this very strange and annoying
include bug in 5.3-dev and now I think
Dmitry Stogov wrote:
Hi,
The attached patch is going to fix the problem.
It implements its own realpath() function, so we won't depend on system
anymore. It also improve realpath cache usage by caching intermediate
results.
Very nice. The intermediate caching is going to drastically reduce
1 - 100 of 1709 matches
Mail list logo
