Re: whitespaces in filenames [was: bug in $(wildcard) on Windows?]

2005-03-18 Thread Paul D. Smith
%% Boris Kolpackov <[EMAIL PROTECTED]> writes: bk> "Paul D. Smith" <[EMAIL PROTECTED]> writes: >> * A new method for encoding strings would need to be found. Maybe >> something like $[...] where "..." would be encoded. This part is >> tricky and needs to be considered carefully. bk> I

Re: whitespaces in filenames [was: bug in $(wildcard) on Windows?]

2005-03-18 Thread Boris Kolpackov
"Paul D. Smith" <[EMAIL PROTECTED]> writes: > * A new method for encoding strings would need to be found. Maybe > something like $[...] where "..." would be encoded. This part is > tricky and needs to be considered carefully. Is this really necessary? Can't we just say that if someone

Re: whitespaces in filenames [was: bug in $(wildcard) on Windows?]

2005-03-18 Thread Paul D. Smith
%% Fabio Alemagna <[EMAIL PROTECTED]> writes: fa> Couldn't it be done so that instead of using spaces, as word fa> delimiters, make used NUL chars? No, because NUL characters delimit the end of strings. You must understand that make is just a string manipulator. It doesn't really have a sep

whitespaces in filenames [was: bug in $(wildcard) on Windows?]

2005-03-18 Thread Fabio Alemagna
On Thu, 17 Feb 2005 08:50:33 -0500, Paul D. Smith <[EMAIL PROTECTED]> wrote: > The short answer is that GNU make doesn't support filenames with spaces > in them. > > The slightly longer answer is that GNU make uses whitespace as a word > delimiter, and there is NO reliable way to quote whitespace