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

[Earnie Boyd]

On 12:31:01 pm 2005-07-13 "Paul D. Smith" <address@hidden> wrote:
> %% "Earnie Boyd" <address@hidden> writes:
>
>   eb> Would it remove the tab or change it to a space?
>
> On a POSIX system it's removed.
>
>   eb> As long as tab is converted to space then not converting \\n to
> a space   eb> would be ok.
>
>   eb> So:
>
>   eb>         echo foo\
>   eb>         bar
>
>   eb> prints "foo bar" while
>
>   eb>         echo foo\
>   eb> bar
>
>   eb> prints "foobar"
>
> OK... if that's the way you want it I guess it's your port.  This is
> not compatible with UNIX/POSIX, however, which means that makefiles
> written on one system will have even less chance of working "out of
> the box" on the other system.
>
>
> My preference would be to keep this behavior identical between
> systems (that is, remove the TAB and do not add a space)... one less
> difference between ports is a good thing in my book.
>

I should clarify that I mean when !unixy_shell or whatever the variable is.

As far as compliant behaviour I wonder how many GNU make files will need to
change as a result of these POSIX compliance changes?

Earnie