I have always wondered why we did not pick another character than ascii 32 to represent space in file names. There are a lot of codepoints in unicode that could be used.
//Fredrik 2013/2/28 Eli Zaretskii <e...@gnu.org>: >> Date: Thu, 28 Feb 2013 10:32:32 +0100 >> From: Reinier Post <reinp...@win.tue.nl> >> >> I don't think make can be expected to handle spaces in filenames >> because by design it relies on many other tools and scripts that >> cannot handle them or handle them in very idiosyncratic ways. >> You're in for a lot of trouble regardless of what make itself supports. > > "Lot of trouble" and "no support at all" are two very different > things. E.g., in Unix shell scripts, if I do care about supporting > such file names, I can have it if I'm careful enough to quote every > file name (a.k.a. "a lot of trouble"). But in a Makefile, I simply > cannot have them at all. No fire escape, period. > > _______________________________________________ > Bug-make mailing list > Bug-make@gnu.org > https://lists.gnu.org/mailman/listinfo/bug-make _______________________________________________ Bug-make mailing list Bug-make@gnu.org https://lists.gnu.org/mailman/listinfo/bug-make
