Path: utzoo!telly!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!rutgers!rochester!pt.cs.cmu.edu!cadre!pitt!cisunx!jgh2
From: jgh2@cisunx.UUCP (John G. Hardie)
Newsgroups: gnu.emacs.bug
Subject: Re: ETAGS strangeness with 18.52 on VMS
Message-ID: <17617@cisunx.UUCP>
Date: 19 Apr 89 19:50:44 GMT
References: <17616@cisunx.UUCP>
Reply-To: jgh2@unix.cis.pittsburgh.edu (John G. Hardie)
Distribution: gnu
Organization: Nuclear Physics Lab, Univ. of Pittsburgh
Lines: 46


Awww Sh*t!

Why is it that you always find the solution to a problem 5 minutes after
posting a question asking for help?

Anyway, the fix for ETAGS is the following.  In find_entries(), change
the follwing lines:

  /* if not a .c or .h or .y file, try fortran */
  if (cp && (cp[1] != 'c' && cp[1] != 'h' && cp[1] != 'y')
      && cp[2] == '\0')
    {
      if (PF_funcs(inf) != 0)
	{
	  fclose(inf);
	  return;
	}
      rewind(inf);	/* no fortran tags found, try C */
    }


to:

  /* if not a .c or .h or .y file, try fortran */
  if (cp && (cp[1] != 'c' && cp[1] != 'h' && cp[1] != 'y'))
    {
      if (PF_funcs(inf) != 0)
	{
	  fclose(inf);
	  return;
	}
      rewind(inf);	/* no fortran tags found, try C */
    }


Which removes the requirement that a fortran file have a one character
extension.

Sheesh! I hate it when this happens - makes me feel stupid.

John-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
John G. Hardie					jgh2@unix.cis.pittsburgh.edu
Dept. of Physics, Univ of Pittsburgh		jgh2@vms.cis.pittsburgh.edu
	   An ounce of inaccuracy saves a pound of explanation