[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[sr #110912] Backslash followed by quote treated as escape sequence on W
From: |
Eric Blake |
Subject: |
[sr #110912] Backslash followed by quote treated as escape sequence on Windows. |
Date: |
Mon, 31 Jul 2023 14:22:13 -0400 (EDT) |
Follow-up Comment #1, sr #110912 (project m4):
As you pointed out, it is the responsibility of the calling program to pass in
argv[] with expected contents. Most ports of GNU programs to Windows
environments have their own idioms in place to either alter the shell to have
normal Unix parsing, or to have the CRT normalize the incoming arguments prior
to reaching main() (examples of these environments being Cygwin and MSYS). In
which case, the problem is in your environment, and not in m4 proper, as the
normalization still happens before main() (whether it happens in the parent
process as with Unix sh, or in the child process). I don't see how upstream
m4 can do anything about your problem. What's more, if it is the CRT not
normalizing arguments the way you want, then every other application you
compile with the same CRT will have the same problem.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/support/?110912>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/