Mail Archives: cygwin/2006/08/17/09:30:22
> Date: Thu, 17 Aug 2006 14:09:23 +0200
>
> On Aug 17 05:46, Eli Zaretskii wrote:
> > > > Windows doesn't allow colons anywhere else in file names anyway.
> > >
> > > That's not quite right. Colons are also used in file names when the
> > > file name denotes an alternative named stream on NTFS file systems.
> >
> > Right, I forgot about this obscure feature.
> >
> > However, this feature is not specific to Cygwin, so if support for
> > such names is important (I suspect it isn't, but that's me), GNU Make
> > should be modified to support them in all Windows ports; any solution
> > that is good for other Windows ports will be good for Cygwin, and vice
> > versa. Do you agree?
>
> Hmm, no, sorry. I can't agree to "any solution that is good for other
> Windows ports will be good for Cygwin". This should be decided on a
> case by case basis.
Of course! I was talking only about _this_specific_case_, i.e. the
support for ADS. I was saying that, if we need to support it, the
same support will work well for all Windows ports.
> Colons are only a problem in the TARGETS and PREREQUISITES part of a
> make rule, not in the COMMAND part. But it only makes marginal sense to
> use the ADS name for dependency checks, because a file has only one set
> of timestamps for the whole file, not multiple timestamps, one per data
> stream. The availablilty on only one filesystem type restricts the
> usefulness further. So the ability to use ADS names in the COMMAND part
> of a rule should be sufficient.
Agreed.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -