MB Sure it cannot because insert cannot. The problem and the error you did
MB above is that you split an operation into two. Your real operation is
MB insert_with_password and that is different from insert. Again insert is an
That's the whole point of OO - to allow overloading the same operation,
Fixed.
At 01:44 28/01/2003, Magnus Määttä wrote:
This is in current head.
(cd .libs rm -f libphp4.la ln -s ../libphp4.la libphp4.la)
Installing PHP SAPI module
Installing shared
extensions:
/usr/local/www/php5mincli/lib/php/extensions/debug-non-zts-20020429/
Installing PEAR environment:
Hi,
we have an application, which connects to a database of
type interbase. We can see, that the times of the
connects go very high, if more people call our site
at the same time.
Per default we use the function ibase_connect and at
the end of the script we make an ibase_close.
If three users go
Hi,
From the PHP manual I find that the flock() function does a advisory
file locking. Is there a way to do mandatory file locking where we do
strict locking? That is once a file is locked, no other process or
thread is allowed to edit the file untill the lock owner is done with
his job and he
That makes PEAR installer coredump with the following core:
Core was generated by `/data/src/php5/sapi/cli/php -n -dsafe_mode 0
/data/src/php5/pear/install-pear.php'.
#0 0x08142d78 in _efree (ptr=0x400b396c,
__zend_filename=0x81a89e0
/data/src/php5/Zend/zend_execute_API.c,
EK That makes PEAR installer coredump with the following core:
Doesn't happen to me. What were the arguments?
--
Stanislav Malyshev, Zend Products Engineer
[EMAIL PROTECTED] http://www.zend.com/ +972-3-6139665 ext.109
--
PHP Development Mailing List http://www.php.net/
To unsubscribe,
EK That makes PEAR installer coredump with the following core:
Doesn't happen to me. What were the arguments?
You need to remove $PREFIX/lib/php to reproduce on my RedHat 7.3
box.
./configure --enable-debug make make install-pear
Edin
--
PHP Development Mailing List http://www.php.net/
Try the direct I/O extension, specifically dio_fcntl(). Just make sure the
filesystem you're using the locks on was mounted with -o mand, and the
locks will be mandatory by default.
J
Ananth Kesari wrote:
Hi,
From the PHP manual I find that the flock() function does a advisory
file
Aside from this being on the wrong list (this should go to
php-general), it's worth noting that mandatory locking support is
pretty inconsistently implemented across most OSs.
George
On Wednesday, January 29, 2003, at 10:59 AM, J Smith wrote:
Try the direct I/O extension, specifically
Hello,
Here at Johns Hopkins we use Apache+PHP to drive the user interface to
our Hubble Space Telescope image archive. Using PHP has been one of the
best decisions we have made. One of our new features is an mosaic image
browser. In some cases a PHP script will run a custom command line
Should be fixed now.
EK EK That makes PEAR installer coredump with the following core:
EK
EK Doesn't happen to me. What were the arguments?
EK
EK You need to remove $PREFIX/lib/php to reproduce on my RedHat 7.3
EK box.
EK
EK ./configure --enable-debug make make install-pear
EK
EK Edin
EK
For this case, could you just consider running
PHP as a CGI? That would leave Apache up but
let PHP close down after execution, yes?
Dante
--
D. Dante Lorenso
Web Adminstrator
[EMAIL PROTECTED]
-Original Message-
From: William Jon McCann [mailto:[EMAIL PROTECTED]]
Sent:
This feature request (which seems worth doing) has sat on the back burner
awhile. Probably because, in the words of one commenter, those who can
produce the patch are just using regex instead.
I've got an implementation put together, the patch for which can be viewed
at:
Translating the php-gtk documentation to spanish
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php
I've got an implementation put together, the patch for which can be
viewed at:
http://169.229.139.97/test/str_ireplace.diff.txt
After some comments on IRC, here's an alternate version to the above
patch. This second approach avoids creating php_memnstri by simply
searching through a copy of
On Wed, 29 Jan 2003, Sara Golemon wrote:
I've got an implementation put together, the patch for which can be
viewed at:
http://169.229.139.97/test/str_ireplace.diff.txt
After some comments on IRC, here's an alternate version to the above
patch. This second approach avoids creating
Derick Rethans wrote:
On Wed, 29 Jan 2003, Sara Golemon wrote:
I've got an implementation put together, the patch for which can be
viewed at:
http://169.229.139.97/test/str_ireplace.diff.txt
After some comments on IRC, here's an alternate version to the above
patch. This second approach
I may be wrong since I haven't profiled this, but my understanding is
that str_replace is much faster than doing either of the regex
replacements. For that reason alone, there is a use for it.
Normally it would be quite faster, however once case sensitivity is added to
the mix I believe the
I may be wrong since I haven't profiled this, but my understanding is
that str_replace is much faster than doing either of the regex
replacements. For that reason alone, there is a use for it.
Normally it would be quite faster, however once case sensitivity is
added to the mix I believe
I suggest to check out
http://citeseer.nj.nec.com/navarro01fast.html
The presented BNDM algorithm is one of the fastest string
searching algorithm while being easy to implement. Its main
loop is faster than the naive str_replace implementation(*).
Check out a C test
On a related topic, the 'boyer' option of str_replace isn't even
documented. That alternate method of performing str_replaces look like
it's a bit more efficient (no benchmarkes atm) but I'm wondering if
there's a specific reasons why it wasn't documented yet.
The BM algorithm is
Ilia A. wrote:
I may be wrong since I haven't profiled this, but my understanding is
that str_replace is much faster than doing either of the regex
replacements. For that reason alone, there is a use for it.
Normally it would be quite faster, however once case sensitivity is added to
the mix
whoops, missent just to sascha instead of list...
On a related topic, the 'boyer' option of str_replace isn't even
documented. That alternate method of performing str_replaces look
like it's a bit more efficient (no benchmarkes atm) but I'm wondering
if there's a specific reasons why it
I'd tip my hat towards implementing it. Pollita has a good point on
consistency and for those who don't know regex's.
On Wed, 29 Jan 2003, Sara Golemon wrote:
I may be wrong since I haven't profiled this, but my understanding is
that str_replace is much faster than doing either of the regex
On Thu, 30 Jan 2003 06:48, Ilia A. wrote:
I may be wrong since I haven't profiled this, but my understanding is
that str_replace is much faster than doing either of the regex
replacements. For that reason alone, there is a use for it.
Normally it would be quite faster, however once case
Gah.
I botched that, I didn't reset the timer.
Total Time: 00:00:03.08 //str_replace
Total Time: 00:00:04.32 //preg_replace
Total Time: 00:00:03.05 //str_replace
Total Time: 00:00:03.67 //preg_replace
Total Time: 00:00:03.27 //str_replace
Total Time: 00:00:04.40 //preg_replace
Closer than I
On January 29, 2003 04:35 pm, Shane Caraveo wrote:
What's the benchmark code? How is the benchmark difference on large
text (ie. 100K of text) vs. small text (1K or smaller)?
Attached is the benchmark script that I've used. I've intentionally used
'small' strings, since that is what I imagine
On Thu, 30 Jan 2003 09:09, Ilia A. wrote:
On January 29, 2003 04:35 pm, Shane Caraveo wrote:
What's the benchmark code? How is the benchmark difference on large
text (ie. 100K of text) vs. small text (1K or smaller)?
Attached is the benchmark script that I've used. I've intentionally used
At 09:46 29.01.2003, Stanislav Malyshev wrote:
MB Sure it cannot because insert cannot. The problem and the error you did
MB above is that you split an operation into two. Your real operation is
MB insert_with_password and that is different from insert. Again insert
is an
That's the whole point
At 18:07 29.01.2003, George Schlossnagle wrote:
Aside from this being on the wrong list (this should go to php-general),
it's worth noting that mandatory locking support is pretty inconsistently
implemented across most OSs.
Why wrong list?
I guess Ananth needs it somewhere forthe netware
better and better...
Ilia offered up an optimized version of php_str_to_str which skips string
resizing and handles do-no-work scenarios up front.
I've made necessary changes to make this case_optional and made a new patch:
http://169.229.139.97/test/str_ireplace.diff-4.txt
as well as posting
I don't even see the speed difference as an issue as much as (A)
simplicity for the user who hasn't figured out regex yet, (B) consistency
(we have 'i' versions of most other string functions, why not this one?)
+1 for the reasons stated above.
Edin
--
PHP Development Mailing List
At 00:47 30.01.2003, Edin Kadribasic wrote:
I don't even see the speed difference as an issue as much as (A)
simplicity for the user who hasn't figured out regex yet, (B) consistency
(we have 'i' versions of most other string functions, why not this one?)
+1 for the reasons stated above.
+1
The real question is why you need mandatory locks and not advisory
locks. If everyone is playing on the same team, advisory locks should
provide all the semantics you need (and are very portable). Mandatory
locks (on linux at least) require not only special mount options, but
special perms
better and better...
One last optimization to save memcpys when needle_len == str_len (thanks
again ilia):
Actual Patch:
http://169.229.139.97/test/str_ireplace.diff-5.txt
Resultant string.c for easy reading:
http://169.229.139.97/test/string-5.c
I've heard enough Ayes over Nays (here, in
One last optimization to save memcpys when needle_len == str_len (thanks
again ilia):
Actual Patch:
http://169.229.139.97/test/str_ireplace.diff-5.txt
Resultant string.c for easy reading:
http://169.229.139.97/test/string-5.c
I've heard enough Ayes over Nays (here, in bugs.php.net, and
On Wednesday, January 29, 2003, at 07:11 PM, Marcus Börger wrote:
The real question is why you need mandatory locks and not advisory
locks. If everyone is playing on the same team, advisory locks
should provide all the semantics you need (and are very portable).
Mandatory locks (on
/usr/local/lib/libsablot.so: undefined reference to `operator new[](unsigned)'
/usr/local/lib/libsablot.so: undefined reference to `vtable for
__cxxabiv1::__si_class_type_info'
/usr/local/lib/libsablot.so: undefined reference to `operator delete(void*)'
/usr/local/lib/libsablot.so: undefined
38 matches
Mail list logo
