Stanislav Malyshev wrote:
Initializing a static class resp. default instance variable with f.e.
an array is an obvious use case.
Err, I'm afraid I don't understand neither your abbreviations nor what
the actual use case is. Can you describe real use case - i.e. module X
has functionality A
On 04/15/2007 11:05 AM, Sebastian Nohn wrote:
?php
$a = 69;
var_dump($a);
$b = A is: .$a;
var_dump($b);
?
5.2.1 output is:
float(6.9E+9)
string(16) A is: 69
5.2.2-dev output is:
float(6.9E+9)
string(12) A is: 6.9E+9
Nice catch, thanks.
What do you think is the most correct
On 4/16/07, Antony Dovgal [EMAIL PROTECTED] wrote:
On 04/15/2007 11:05 AM, Sebastian Nohn wrote:
?php
$a = 69;
var_dump($a);
$b = A is: .$a;
var_dump($b);
?
5.2.1 output is:
float(6.9E+9)
string(16) A is: 69
5.2.2-dev output is:
float(6.9E+9)
string(12) A is:
On Mon, April 16, 2007 10:10 am, Antony Dovgal wrote:
On 04/15/2007 11:05 AM, Sebastian Nohn wrote:
?php
$a = 69;
var_dump($a);
$b = A is: .$a;
var_dump($b);
?
5.2.1 output is:
float(6.9E+9)
string(16) A is: 69
5.2.2-dev output is:
float(6.9E+9)
string(12) A is:
That's good news. Has a patch been submitted? Even if it is initially
only a win32 compiler directive wrapping the lock?
On 14/04/07, Rob Richards [EMAIL PROTECTED] wrote:
I can sometimes reproduce the missing entries though never get data
corruption anymore.
This might now be a Windows only
PHP 4 Bug Database summary - http://bugs.php.net
Num Status Summary (631 total including feature requests)
===[*Directory/Filesystem functions]
40661 Open cwd is reset when shutdown handler runs
PHP 5 Bug Database summary - http://bugs.php.net
Num Status Summary (697 total including feature requests)
===[*General Issues]==
40716 Assigned Installation problem Win/Apache224
PHP 6 Bug Database summary - http://bugs.php.net
Num Status Summary (44 total including feature requests)
===[*General Issues]==
26771 Suspended register_tick_funtions crash under threaded webservers
27372 Verified parse error
I am interested in being able to trap the (currently) fatal error that
results when memory usage exceeds the defined memory limit.
I was thinking it could work as follows:
- in addition to a memory_limit configuration directive, there could
be a memory_limit_grace configuration directive. This
On Windows, there is no such thing as a true open-write-for-append.
Unlike Unix, write for append mode is not atomic, internally it is a
seek + write. Mix that with multiple writers, and you have an inherent
race condition built it.
Richard Quadling wrote:
That's good news. Has a patch been
So isn't locking the solution for Windows?
On 16/04/07, William A. Rowe, Jr. [EMAIL PROTECTED] wrote:
On Windows, there is no such thing as a true open-write-for-append.
Unlike Unix, write for append mode is not atomic, internally it is a
seek + write. Mix that with multiple writers, and you
Richard Quadling wrote:
So isn't locking the solution for Windows?
If this is single writer process, even with multithreads - a mutex
is most efficient, otherwise with concurrent writer processes, file
locking makes the most sense.
Bill
--
PHP Internals - PHP Runtime Development Mailing List
The testing I'm using is to launch multiple copies of the same PHP
script simultaneously using php.exe (CLI mode). This could easily be
multiple FastCGI scripts or multiple ISAPI threads.
On 16/04/07, William A. Rowe, Jr. [EMAIL PROTECTED] wrote:
Richard Quadling wrote:
So isn't locking the
Hi all.
It seems that zend_ts_hash_clean is not actually thread-safe: it
delegates to zend_hash_clean without first acquiring the write lock on
the hashtable.
Is this behavior an oversight (if so, should I open a bug report with
the trivial patch below?) or is this intentional?
Marco
---
Sebastian,
it should also be mentioned that when you are refferring to a test within ZF
you should always look
against the latest version of ZF.
Since 0.8 I've fixed several issues for the I18N core and about 2000 lines
of code have changed only for I18N which you are referring with
- in addition to a memory_limit configuration directive, there could
be a memory_limit_grace configuration directive. This gets stored in
the struct _zend_mm_heap, along with the limit.
That could be a problem because it's very hard to know exact memory
requirements for PHP code for most
Sorry for the cryptic reply. I think that initializing a static class
property as well as initializing a default property with for example
an array is an obvious use case. Try to do the following in an extension:
class c {
static $prop1 = array(foo, bar);
var $prop2 =
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Thomas,
it should also be mentioned that when you are refferring to a test
within ZF you should always look
against the latest version of ZF.
As already mentioned: This also happens in ZF trunk. ZF unit tests fail
on any platform since
You might also come at it from the other direction and detect/notify
at some number smaller than the current hard limit, configurable in
php.ini...
This might play better with anything relying on the current behaviour.
On Mon, April 16, 2007 5:19 am, David Sklar wrote:
I am interested in being
On Sat, April 14, 2007 4:49 am, Bart de Boer wrote:
And let me stress that this is something we're *forcing* people to do
when they're on a short tags enabled server... It's not something
they're allowed to do at free will... PHP's convention is currently
responsible for people creating
On Sat, April 14, 2007 11:07 am, Marcus Boerger wrote:
Hello Guilherme,
?= is also not confirm toxml spec. What we could do is ?echo.
I just don't understand why you think PHP source should conform to XML
spec...
I might use PHP to produce compliant XML.
But my PHP source code itself is
PHP source as an XML document...
[shudder]
--
Some people have a gift link here.
Know what I want?
I want you to buy a CD from some indie artist.
http://cdbaby.com/browse/from/lynch
Yeah, I get a buck. So?
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit:
Hello all,
I build a patch for wrapper php fopen. In this patch I create a way for
the script access the filedescriptos opened by process. Ex:
php file.php 3file_in.txt 7file_out.txt
In this case the script can't read the filedescriptor 3 and 7. Not
have way for read or write in filedescriptor
Hi Oliver,
I was just trying to make a case for removing those ASP short tags (at
least) by advocating to remove short tags all together in the long run.
I didn't mean executing PHP documents with PHP. I meant that it should
be possible to use PHP documents with other (XML-based)
Hello,
A soft memory limit could be very useful; it doesn't necessarily need to throw
an error, but it would provide an opportunity to free some memory and prevent
the script from crashing. Perhaps something like:
// function to call when memory is running out
25 matches
Mail list logo
