File: comments

package info (click to toggle)
gridengine 8.1.9%2Bdfsg-10
  • links: PTS, VCS
  • area: main
  • in suites: bookworm
  • size: 56,880 kB
  • sloc: ansic: 432,689; java: 87,068; cpp: 31,958; sh: 29,429; jsp: 7,757; perl: 6,336; xml: 5,828; makefile: 4,701; csh: 3,928; ruby: 2,221; tcl: 1,676; lisp: 669; yacc: 519; python: 503; lex: 361; javascript: 200
file content (35 lines) | stat: -rw-r--r-- 1,251 bytes parent folder | download | duplicates (46)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
$description = "The following test creates a makefile to test comments\n"
              ."and comment continuation to the next line using a \n"
              ."backslash within makefiles.";

$details = "To test comments within a makefile, a semi-colon was placed \n"
          ."after a comment was started.  This should not be reported as\n"
          ."an error since it is within a comment.  We then continue the \n"
          ."comment to the next line using a backslash.  To test whether\n"
          ."the comment really continued, we place an echo command with some\n"
          ."text on the line which should never execute since it should be \n"
          ."within a comment\n";

open(MAKEFILE,"> $makefile");

# The Contents of the MAKEFILE ...

print MAKEFILE <<\EOF;
# Test comment vs semicolon parsing and line continuation
target: # this ; is just a comment \
	@echo This is within a comment. 
	@echo There should be no errors for this makefile.
EOF

# END of Contents of MAKEFILE

close(MAKEFILE);

&run_make_with_options($makefile,"",&get_logfile);

# Create the answer to what should be produced by this Makefile
$answer = "There should be no errors for this makefile.\n";

# COMPARE RESULTS

&compare_output($answer,&get_logfile(1))