RE: backslash does not simply continue line?

[Brian R Cowan]

In many cases this construct is necessary to make a makefile readable. 
I've seen too many makefiles where there are 200+ files in a macro like 
that. Putting a macro liek that on a single line would break a number of 
editors. 

I think this isn't "continue line" as much as "insert the literal line 
termination instead of stopping the line parse here."

I've seen this other places where it is absolutely a bad thing (using C 
#defines as multi-line function declarations). But I don't have a problem 
with it in makefiles as long as it improves makefile readability.

=================================================================
Brian Cowan
Advisory Software Engineer
ClearCase Software Advisory Team (SWAT)
Rational Software
IBM Software Group
550 King St
Littleton, MA 01460
 
Phone: 1.978.899.5436
Web: http://www.ibm.com/software/rational/support/



From:   "Mark Galeck (CW)" <address@hidden>
To:     "address@hidden" <address@hidden>, 
Cc:     "address@hidden" <address@hidden>
Date:   03/03/2012 12:07 PM
Subject:        RE: backslash does not simply continue line?
Sent by:        address@hidden



Well, OK, basically this means for me, I can't really break some lines and 
have to keep them long (or I would have to put an additional $(strip) 
calls)

>Just yesterday I saw a
makefile that contained this:

        SOURCES = foo.c\
        bar.c\
        biz.c\
        baz.c

so changing this would absolutely break many real makefiles.



Well, to me, this is already broken to begin with :)  The person who 
writes code like this should find some other occupation. 

_______________________________________________
Help-make mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/help-make