RE: deprecating features: -wf, Repository_Sig_Times_OK?

[Gary Oberbrunner]

I was originally going to use -wf to rebuild the emacs TAGS file from only
the relevant source files, but never got around to it.  I suppose I'd like
it to stay just in case someone wants to do that, but on the other hand that
output still has to be filtered before you can use it, so maybe it's not the
right answer to that need.

-- Gary Oberbrunner

 > ----- Original Message -----
 > From: "Steven Knight" <address@hidden>
 > To: <address@hidden>
 > Sent: Wednesday, June 27, 2001 8:40 PM
 > Subject: deprecating features: -wf, Repository_Sig_Times_OK?
 >
 >
 > > Is anyone out there actively using the Cons -wf option, or the
 > > Repository_Sig_Times_OK feature?
 > >
 > > A while ago, someone on the list suggested a -w option to warn about
 > > deprecated features.  Great idea; it would give us a mechanism for
 > > smoother feature transitions.  But it conflicts with the -wf option
 > > (write all "considered" file names into a file).
 > >
 > > -wf happens to be the only multi-character option that takes an
 > > argument, which contradicts good *NIX command-line
 > conventions. -wf also
 > > doesn't really do anything that -d doesn't do, except that it
 > writes the
 > > list to a separate file, not intermixed with the build output.
 > >
 > > I propose at least renaming -wf to some other single-character option,
 > > so that we can use -w for warnings.  If no one is really relying on the
 > > separate file list, maybe we could even get rid of it entirely...?  How
 > > badly would that mess up anyone?
 > >
 > > Repository_Sig_Times_OK was a bad solution for problem specific to my
 > > build environment when the Repository functionality was first being
 > > developed.  It tells Cons to ignore the time stamps in any .consign
 > > files in a Repository directory.  I doubt that anyone is using it, and
 > > I'd suggest just getting rid of it.  Any objections?
 > >
 > > --SK
 >