RE: [PHP-DEV] PHP4 vs. PECL

> On Sat, 8 Feb 2003, Kai Schröder wrote: > >some extensions included in the PHP_4_3 branch was moved to PECL (fribidi > >for instance). > Those were only removed from HEAD and not from the PHP_4_3 branch. Right, but because we have this extensions twice we should imo

[PHP-DEV] PHP4 vs. PECL

Hi all, some extensions included in the PHP_4_3 branch was moved to PECL (fribidi for instance). If I understand right, all commits to the PHP_4_3 branch are for bug fixing for the next 4.* releases. How to handle fixes for moved extensions? Commit twice (PHP_4_3 and pear/PECL) or commit only to

[PHP-DEV] patch for pear/PECL/fribidi

I've fixed compilation errors for the fribidi extension (see attached patch). It's tested on Linux and Windows with fribidi 0.10.4 and 0.11.-0 (current dev). Please commit. To solve compilation problems on Windows you need a fribidi.lib _with_ char sets. Regards, Kai Index: fribidi.c ===

RE: [PHP-DEV] fix for ext/notes

> Next try with other name. This version is without indendations (thanks Derick). Regards, Kai Index: notes.dsp === RCS file: /repository/php4/ext/notes/notes.dsp,v retrieving revision 1.1 diff -u -r1.1 notes.dsp --- notes.dsp 16 F

RE: [PHP-DEV] fix for ext/notes

> On Thu, 6 Feb 2003, [iso-8859-1] Kai Schröder wrote: > > Attached diff will fix compiling problems for ext/notes on > Windows (wrong > > includes, wrong output dir). It tested with Notes C API R5 and > R6. Please > > commit. > empty attachment Next try with ot

[PHP-DEV] fix for ext/notes

Attached diff will fix compiling problems for ext/notes on Windows (wrong includes, wrong output dir). It tested with Notes C API R5 and R6. Please commit. Regards, Kai -- PHP Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

RE: [PHP-DEV] Make Windows PHP Fork

> Is it possible to make the php.exe under > window's fork, so it isn't visible in the > start bar? I ask because I would like to > make a PHP program that runs periodically > in the background, and I know how to start > it at computer start time, but it makes that > damned dos window pop up. There

[PHP-DEV] changed/new tests for Win32

I've changed some tests to reduce failed test count on Windows to 7 (latest php4-win32 snap): Bug #21131: fopen($filename, "a+") has broken position [D:\work\php4\ext\standard\tests\file\bug21131.phpt] Various pow() tests [D:\work\php4\ext\standard\tests\math\pow.phpt] unserialize() floats with E

RE: [PHP-DEV] writing test cases

> that's not true guys, PHP4 is in the PHP_4_3 branch and if you don't > explicitely commit the tests to that branch they won't be there. > HEAD is PHP5. Because tests are not in the win32 snaps, I make cvs -z9 -d :pserver:[EMAIL PROTECTED]:/repository co php4 to checkout the PHP4 branch. Is th

[PHP-DEV] writing test cases

Hi all, please take care if you write test cases. Tests for PHP5/ZE2 only are also in the PHP4 branch, but some of them have no SKIPIF for versions < 5.0.0, please use version_compare() to skip these tests for lower versions. Same problem with tests for changed functions (for instance range()). T

[PHP-DEV] RE: [PHP-QA] Test results [failed]

That's the result of testing lastest win32 snap (PHP4-STABLE) against test cases in HEAD (something I should not do, I know): > = > FAILED TEST SUMMARY > - > jdto

RE: [PHP-DEV] RfC: version names

> That can be done, but that means 12 commits "a day" for a single file. I > dont think that's a good idea. That's true. Now we have round about 30 commits each day. 12 more will make less than 5.000 blocks (5MB for 1k-blocks) more disk usage per year. Where do you see the real problem if the comm

RE: [PHP-DEV] RfC: version names

> I suppose we can have the snapshot generator do that, but it would still > hard to differentiate between CVS versions then. Sounds a little bit stupid, but why the snapshot generator can't simply commit a changed /main/php_version.h every 2 hours? The php-cvs mailer should ignore the commits (ig

[PHP-DEV] RfC: version names

Hi all, I'm working on a new framework for analyzing results of "make test" for QA Team (see php-qa list). Talking with Sebastian Nohn, I realized, that we can't differ the versions in detail. That means, that we can't say which source packet was used to build php. Is there any way to name the ve

[PHP-DEV] segfault in latest CVS

I got a segmentation fault during configure php (today cvs) on Linux (SuSE 7.3, Kernel 2.4.20). Last line was "checking getpwnam... no". Regards, Kai -- PHP Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

[PHP-DEV] user_streams.c: Win32, compiler warning

During compile php4ts for Win32 (Windows 2000 Pro, VC++ 6.0), I got the following output: ... user_streams.c D:\Daten\CVS\php4\main\user_streams.c(630) : warning C4244: '=' : Konvertierung von 'long ' in 'unsigned short ', moeglicher Datenverlust D:\Daten\CVS\php4\main\user_streams.c(631) : warni

[PHP-DEV] CVS Account Request: k.schroeder

translating manual to german -- PHP Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php