--- "Greg A. Woods" <[EMAIL PROTECTED]> wrote:
-8<-
>
> > If we can deal with ":" - fine, if we cannot - no problem.
>
> It might be sensible for GNU Make to try and introduce quoting rules
> that would allow ':' to be used in filenames. However I would hope that
> wouldn't mean that the GNU Coding Standards, and in particular Automake,
> would require that GNU Make be used unconditionally because of this
> feature. Similar tricks could be employed by shells to quote field
> separators in multi-field variables, etc. However again this would
> imply restricting the user to shells compatible with autoconf. As a
> result I think it's not sensible to even try to have autoconf (or
> automake) handle filenames with embedded ':' characters, or even
> extension separators other than '.'.
>
Hmm... We've gone from discussing autoconf to discussing make. At any rate,
since "GNU's Not Unix", and a : in a file name isn't portable; so that being
that, and given that autoconf is a portability tool, autoconf should take care
to error on filenames given with characters that aren't portable. I've been
bitten recently by a tar file with a : in the filename that I downloaded from
the net :(.
Cheers,
=====
---
Earnie Boyd: <mailto:[EMAIL PROTECTED]>
__Cygwin: POSIX on Windows__
Cygwin Newbies: <http://www.freeyellow.com/members5/gw32/index.html>
__Minimalist GNU for Windows__
Mingw32 List: <http://www.egroups.com/group/mingw32/>
Mingw Home: <http://www.mingw.org/>
__________________________________________________
Do You Yahoo!?
Send instant messages & get email alerts with Yahoo! Messenger.
http://im.yahoo.com/
