Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.10.15

Bug #5958 strange error on misstyping
Submitted: 2005-11-14 14:10 UTC
From: moosh Assigned: cellog
Status: Closed Package: PEAR
PHP Version: Irrelevant OS: winxp
Roadmaps: (Not assigned)    
Subscription  
Comments Add Comment Add patch


Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know! Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem : 48 + 29 = ?

 
 [2005-11-14 14:10 UTC] moosh
Description: ------------ I discover ty by misstyping. I try to run-test on unexisting "helloGreg" file Look the last when I'm in pear root >>pear config-get bin_dir C:\Prg\Net\serveur\EasyPHP1-8\php >>pear run-tests helloGreg Running 0 tests TOTAL TIME: 00:00 0 PASSED TESTS 0 SKIPPED TESTS >>pear run-tests s:\helloGreg Running 0 tests TOTAL TIME: 00:00 0 PASSED TESTS 0 SKIPPED TESTS >>pear run-tests s:\cvs.php.net\pear\helloGreg Warning: Compilation failed: PCRE does not support \L, \l, \N, \P, \p, \U, \u, o r \X at offset 19 in System.php on line 571 Warning: Compilation failed: PCRE does not support \L, \l, \N, \P, \p, \U, \u, o r \X at offset 19 in System.php on line 571 Warning: Compilation failed: PCRE does not support \L, \l, \N, \P, \p, \U, \u , o r \X at offset 19 in System.php on line 571 Warning: Compilation failed: PCRE does not support \L, \l, \N, \P, \p, \U, \u, o r \X at offset 19 in System.php on line 571 Warning: Compilation failed: PCRE does not support \L, \l, \N, \P, \p, \U, \u, o r \X at offset 19 in System.php on line 571 Running 0 tests TOTAL TIME: 00:00 0 PASSED TESTS 0 SKIPPED TESTS

Comments

 [2005-11-16 03:31 UTC] cellog
This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.