[minor style issue] filenames and C++ reserved words in header files

lilo (rmenon@tisl.ukans.edu)
Tue, 19 Mar 1996 22:42:25 -0600 (CST)

Has anyone noticed that emacs bombs while trying to scan etags files
of the kernel ? (or does no one use such tools anymore ? Its really useful
for browsing through lots of code)
It does'nt seem to like a "," (comma) in a filename and
drivers/scsi has a couple of files like these (53c7,8xx.c and 53c7,8xx.h).

Basically etags seems to assume that a "," marks the end of the filename
and gets confused with the filenames 53c7,8xx.c and 53c7,8xx.h in drivers/scsi.

For eg. here's a proper filename line in the TAGS files:

fs/read_write.c,324

and here's what the problem files look like:

drivers/scsi/53c7,8xx.c,2429

After reading this emacs tries to open the file drivers/scsi/53c7
(which does'nt exist) instead of drivers/scsi/53c7,8xx.c and
stops scanning with an error message.

I usually fix this by editing the etags file and deleting these entries.
Linus: Do you think this could be changed to use a more standard
name ? It would be nice if minor iritants like this did not exist by 1.4

ps: Not related to this but pci.h and related files use C++ keywords "class" as
structure member and variable names. I discoverd this when it
got accidentally included in a system C++ program I was writing. Think
this should be changed ? I would'nt say ban reserved words from every
existing programming language but its reasonable to expect that C
header files can be included in C++ programs.

Cheers,

-- 
Raghavan ============ rmenon@tisl.ukans.edu or rmenon@engr.ukans.edu