Hi,
I'm running into some race conditions with the CVS of PEAR installer in
PHP5 where it fails to remove existing php files, and locks a file so
firmly (Windows XP) that I have to reboot to get the OS to loose its
grip on it.
I'm wondering if the locking of included source files has changed fr
It shouldn't be locking the file.
Is there any chance that you have a "zombie" process that does have a
lock? I noticed some weird locking behaviour like this today using a
recent cygwin release (seems like bash held a lock on a directory that
I had cd'ed into earlier in the day). This was total
Wez Furlong wrote:
It shouldn't be locking the file.
Is there any chance that you have a "zombie" process that does have a
lock? I noticed some weird locking behaviour like this today using a
recent cygwin release (seems like bash held a lock on a directory that
I had cd'ed into earlier in the day
I've got a short test script:
saved as C:\php5\pear\test.php:
');
fclose($fp);
include_once $statedir . DIRECTORY_SEPARATOR . 'Tester.php';
unlink($statedir . DIRECTORY_SEPARATOR . 'Tester.php');
?>
It's *definitely* related to include_once/require_once
Greg
Output:
Warning: unlink(C:\php5\pear\T
Quoting Greg Beaver <[EMAIL PROTECTED]>:
> Wez Furlong wrote:
> > It shouldn't be locking the file.
> >
> > Is there any chance that you have a "zombie" process that does have a
> > lock? I noticed some weird locking behaviour like this today using a
> > recent cygwin release (seems like bash he
Hello.
Some time ago I have posted a patch that would make PHP call __autoload() for
unknown functions too.
I didn't get any feedback regarding the patch so I send it to the mailing list
once again. The patch
adds two constants AUTOLOAD_CLASS and AUTOLOAD_FUNCTION. The __autoload()
definition is
