Re: Problem with backslash/newline on DOS/Windows/OS2/etc.?

[Paul D. Smith]

%% Eli Zaretskii <address@hidden> writes:

  ez> Yes, I think testing unixy_shell would be okay.

Good stuff; so if !unixy_shell we want to go back to the old model,
where make would eat the backslash-newline pair before invoking the
shell, right?

What about the TAB on the next line?  In POSIX if the first character
after a backslash-newline is a TAB, make will remove it from the command
script to be invoked.

The other change between the old behavior and new behavior was that make
used to replace the backslash-newline with a space.  So, if you had
this:

    echo foo\
bar

would print "foo bar".  In POSIX, no whitespace is added so this
would print "foobar".

I like the POSIX way better but it's not backward-compatible so it's up
to you guys.

-- 
-------------------------------------------------------------------------------
 Paul D. Smith <address@hidden>          Find some GNU make tips at:
 http://www.gnu.org                      http://make.paulandlesley.org
 "Please remain calm...I may be mad, but I am a professional." --Mad Scientist