Follow-up Comment #5, bug #35063 (project make):
Well, when saying "altering the basic syntax" I mean changing the semantics of
'$(...)' notation, which currently stands for expanding a variable reference
or invoking a built-in function.
Personally for me it is unclear what '$(%20)' or '$(.%20)' means. If we
perceive it just as a variable reference, then what would '$(value %20)' or
'$(call %20)' return? I guess, it still should be a space. Also, what's about
computed references, like '$(%$(twenty))', or the one I told about in my
previous comment? In such case the problem can't be solved only by the
tokenizer and requires '%XX' special variables to be defined.
Finally, encoding/decoding multiple characters at once becomes a pain. For
example, how do I properly unescape 'Hello%2C%20world%21' string (assuming it
is computed somewhere, that is not literal)?
However, I agree, that Paul is to make the final decision.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?35063>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-make mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-make
