compile regexp perl Test module

compile regexp perl Test module

[Kevin Ryde]

[-- Attachment #1: Type: text/plain, Size: 399 bytes --]

The format of the failure messages from the perl "Test" module is not
quite the same as from its normal compiling,

        * progmodes/compile.el (compilation-error-regexp-alist): Add perl
        "Test" module error messages.

I've only ever bothered with the plain ok(X) form myself, which is the
first message shown in the comment, but I added the other styles too.
Sample foo.pl I used below.


[-- Attachment #2: compile.el.perl-test.diff --]
[-- Type: text/plain, Size: 923 bytes --]

*** compile.el.~1.282.~	Wed Nov 26 09:29:21 2003
--- compile.el	Tue Dec  2 15:43:25 2003
*************** (defvar compilation-error-regexp-alist
*** 339,344 ****
--- 339,354 ----
      ;; store::odrecall('File_A', 'x2') called at store.pm line 90
      (".* at \\([^ \n]+\\) line \\([0-9]+\\)[,.\n]" 1 2)
  
+     ;; Perl "Test" module:
+     ;;  # Failed test 2 in foo.pl at line 6
+     ;;  # Test 3 got: '0' (foo.pl at line 7)
+     ;; Expected failures (don't match these):
+     ;;  # Failed test 5 in foo.pl at line 10 *TODO*
+     ;;  # Test 6 got: '0' (foo.pl at line 11 *TODO*)
+     ;; Unexpected success:
+     ;;  ok 8 # (foo.pl at line 14 TODO?!)
+     (".*\\((\\| in \\)\\([^ \n]+\\) at line \\([0-9]+\\)\\(\n\\|)\\| TODO\\?!)\\)" 2 3)
+ 
      ;; Oracle pro*c:
      ;; Semantic error at line 528, column 5, file erosacqdb.pc:
      ("Semantic error at line \\([0-9]+\\), column \\([0-9]+\\), file \\(.*\\):"

[-- Attachment #3: foo.pl --]
[-- Type: application/x-perl, Size: 518 bytes --]

[-- Attachment #4: Type: text/plain, Size: 141 bytes --]

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel

Re: compile regexp perl Test module

[Kevin Ryde]

[-- Attachment #1: Type: text/plain, Size: 518 bytes --]

Not sure if this didn't find favour, or was just lost while the cvs
was down.  Re-posting in case it was the latter:


The format of the failure messages from the perl "Test" module is not
quite the same as from its normal compiling,

        * progmodes/compile.el (compilation-error-regexp-alist): Add perl
        "Test" module error messages.

I've only ever bothered with the plain ok(X) form myself, which is the
first message shown in the comment, but I added the other styles too.
Sample foo.pl I used below.


[-- Attachment #2: compile.el.perl-test.diff --]
[-- Type: text/plain, Size: 923 bytes --]

*** compile.el.~1.282.~	Wed Nov 26 09:29:21 2003
--- compile.el	Tue Dec  2 15:43:25 2003
*************** (defvar compilation-error-regexp-alist
*** 339,344 ****
--- 339,354 ----
      ;; store::odrecall('File_A', 'x2') called at store.pm line 90
      (".* at \\([^ \n]+\\) line \\([0-9]+\\)[,.\n]" 1 2)
  
+     ;; Perl "Test" module:
+     ;;  # Failed test 2 in foo.pl at line 6
+     ;;  # Test 3 got: '0' (foo.pl at line 7)
+     ;; Expected failures (don't match these):
+     ;;  # Failed test 5 in foo.pl at line 10 *TODO*
+     ;;  # Test 6 got: '0' (foo.pl at line 11 *TODO*)
+     ;; Unexpected success:
+     ;;  ok 8 # (foo.pl at line 14 TODO?!)
+     (".*\\((\\| in \\)\\([^ \n]+\\) at line \\([0-9]+\\)\\(\n\\|)\\| TODO\\?!)\\)" 2 3)
+ 
      ;; Oracle pro*c:
      ;; Semantic error at line 528, column 5, file erosacqdb.pc:
      ("Semantic error at line \\([0-9]+\\), column \\([0-9]+\\), file \\(.*\\):"

[-- Attachment #3: foo.pl --]
[-- Type: application/x-perl, Size: 518 bytes --]

[-- Attachment #4: Type: text/plain, Size: 141 bytes --]

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel

Re: compile regexp perl Test module

[Richard Stallman]

Kevin Ryde, we can't install your patches until we get an employer
disclaimer.  I've been asking you for months about progress on this,
but I have not got any response.

Until we get papers from you, your posting of patches is
counterproductive.  We can't use them, and anyone else who wants to
fix the same problem has to go out of his way to make sure his change
does not resemble yours.  So please don't post patches until we
have papers from you.

If you would like to do something helpful, please post an explanation
of the problem or the job that needs to be done.  It would be ok for
whoever does write a patch to use that explanation, so it would
facilitate the work without causing an obstacle.