On 4/1/2014 4:22 PM, h.becker wrote:
On 04/01/2014 06:41 AM, John E. Malmberg wrote:
If you have the make variable be a MCR command, it has a space which can
have side effects when if the resulting string is processed by other
strings or macros.
You mentioned this already. Can you point me to an example where this
fails? Is this in a test, which I couldn't run so far?
For the $(MAKE), macro, I do not have an example.
In the tests though, several examples show up where the VMS specific
change to have some macros return "," delimiters instead of " "
delimiters broke the tests and required some workarounds.
That is why adding an unexpected space to the value returned by a
standard macro can be predicted to have problems.
With 20/20 hindsight, a new set of macros should have been created that
returned the data with comma delimiters that could have been used with
VMS specific rules and recipes. That can not be done now with out
breaking backward VMS compatibility.
But having a set of functions to easily swap commas for spaces and the
reverse would probably still be useful to add, as it would be more
convenient than the hack I had to use.
Regards,
-John
_______________________________________________
Bug-make mailing list
Bug-make@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-make
