[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bug Report (Feature request?) etags (GNU Emacs 21.1)

From: Kim F. Storm
Subject: Re: Bug Report (Feature request?) etags (GNU Emacs 21.1)
Date: 18 Feb 2002 13:21:54 +0100
User-agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2.50

address@hidden (Sven Utcke) writes:

> > However, if the original source file is not available, it would not
> > make sense to do so.  
> But, as you point out below, in that case you would also get into all
> kinds of trouble trying to debug the thing, and the user should then
> really remove the #line directives (which, of course, is easily done
> using grep -v).

Suppose I get a source package Z from you in which there is a file xyz.c 
which is generated from some file xyz.dum which is NOT included in
the package.

Now, what should etags do with the #line directives in xyz.c ?

Should it generate the TAGS file with references to xyz.dum
(i.e. nowhere as far as I am concerned), or should it make references
to xyz.c (which might make some sense to me)?

Alternatively, etags could put dual references into TAGS -- one for
the .c file and one for the .dum file, at least that would give me
a chance to find both  [in some cases, looking at the generated code
is necessary].

But I guess that if we have a command line option to control this,
then everybody will be happy!

Kim F. Storm  http://www.cua.dk

reply via email to

[Prev in Thread] Current Thread [Next in Thread]