.
Last update: 1997-05-20
9945-2-100 _____________________________________________________________________________ Topic: make Relevant Sections: 6.2.7.2 Defect Report: ----------------------- From: [email protected] (Andrew Josey) Date: Thu, 16 Mar 1995 07:32:02 +0000 The following request regarding an interpretation on 9945-2 is being sent on behalf of X/Open Company Ltd. Publication: 9945-2:1993 Topic: make Page: 671, Lines 361-363 The description on POSIX.2 P671, L361-363 : When an escaped <newline> (one preceded by a backslash) is found anywhere in the makefile, it shall be replaced, along with any leading white space on the following line, with a single <space>. should not apply to command lines in makefiles. It seems that historic practice is something more like: When an escaped <newline> (one preceded by a backslash) is found anywhere in the makefile except in a command line, it shall be replaced, along with any leading white space on the following line, with a single <space>. When an escaped <newline> is found in a command line in a makefile, the command line passed to the command interpreter (see below) shall contain the backslash, the <newline>, and the next line, except the first character of the next line will not be given to the command interpreter if it is a <tab>. Note that the behavior of \<newline> on command lines depends on quoting. Quoting is handled by the shell, not by make. Was this change intentional? Interpretation response ------------------------ The standard states the behavior for escaped <newline>, and conforming implementations must conform to this. However, concerns have been raised about this which are being referred to the sponsor. Rationale: --------- None Forwarded to Interpretations group: Mar 16 1995 Proposed resolution circulated: May 16th Comments due: June 15th Finalised: June 16th 1995