>While paths with spaces in them may be a fact of reality, they are
>non-portable according to POSIX.  It is going to be an uphill battle if
>you want to submit patches to make autoconf automatically handle file
>names with spaces, as there is nothing portable about them.

POSIX does not forbid the use of spaces, either, and they are a widespread fact 
of reality (as you noted).  There ARE standard ways in POSIX to include such 
filenames in shell scripts: single quotes, double quotes, and backslash.

It is true that there is no standard way to create dependencies on them in 
makefiles. But I do not know of a user who needs that.

All I need is a way to invoke programs that include spaces in their name. That 
is a narrower need. There are already ways to do that in the standard. Perhaps 
autoconf could learn how to do just that.

--- David A.Wheeler

_______________________________________________
Autoconf mailing list
Autoconf@gnu.org
https://lists.gnu.org/mailman/listinfo/autoconf

Reply via email to