[bug #17521] target-specific variables inluding semicolon

[Paul D. Smith]

Follow-up Comment #2, bug #17521 (project make):

Actually, Eli, if the example shown is accurate (I haven't tried it) then
this seems to be a bug.  First note that the two cases behave differently:
the one without the semicolon strips the backslash and the one with it does
not.  That can't be right.

Second, the text you're quoting applies to backslashes inside the command
script: these backslashes are in variable values (even though they're
target-specific variables they still follow the rules for setting variables)
and the behavior of backslashes in variable values didn't change.

Again, I haven't looked at this at all but offhand I'd say there's some issue
with the parser finding semicolons in target-specific variables: remember make
needs to handle semicolons in a normal target definition such as "all: ; @echo
all" specially.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?17521>

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