[bug #18561] Why backslash line continuation introduce an extra space

[Paul D. Smith]

Update of bug #18561 (project make):

  Status:None => Not A Bug  
 Open/Closed:Open => Closed 

___

Follow-up Comment #1:

It is by design; in fact it's mandated by the POSIX standard for make, which
states:

> When an escaped  (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 .

Since there is no limit to the length of a physical line in a makefile in GNU
make, I suggest you only break physical lines at whitespace.

___

Reply to this item at:

  

___
  Message sent via/by Savannah
  http://savannah.gnu.org/



___
Bug-make mailing list
Bug-make@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-make

[bug #18561] Why backslash line continuation introduce an extra space

[anonymous]

URL:
  

 Summary: Why backslash line continuation introduce an extra
space
 Project: make
Submitted by: None
Submitted on: Wednesday 12/20/06 at 05:32 UTC
Severity: 3 - Normal
  Item Group: Bug
  Status: None
 Privacy: Public
 Assigned to: None
 Open/Closed: Open
 Discussion Lock: Any
   Component Version: 3.81
Operating System: Any
   Fixed Release: None

___

Details:

For GNUmake 3.81 and 3.80:

For a makefile like this:

{code}
nlap = a\n\
b

$(warning $(nlap))

nlappend:
echo -e "$(nlap)" > out.dat
{code}

The generated out.dat has the following content(represented in hex):


61 0A 20 62 0A


You can see a space introduced in the value of `nlap'. Is this by design? I
hope it's not -- but a bug, since the user wants only line-continuation, not
an extra space. If he wants an extra space, he can add it himself.




___

Reply to this item at:

  

___
  Message sent via/by Savannah
  http://savannah.gnu.org/



___
Bug-make mailing list
Bug-make@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-make