#327 COBOL tags buggy

[Simon Sobisch]

Hi! I use Exuberant Ctags through the NPP-Plugin SourceCookifier. There are some bugs I've recognized and I guess they're rooting in Exuberant Ctags. Please check this. Thank you!

1. It doesn't matter in COBOL if there is a line break or not (only for comment lines). It seems that CTAGS is checking for the line break. Sample:
Not recognized as a data item:
01 somevar
PIC S9(7)
usage comp-5.
Recognized as a data item:
01 somevar PIC S9(7) usage comp-5.
2. It doesn't matter how much spaces (or line breaks) are between a word and a dot. Sample:
sectest section .
isn't recognized as a section while
sectest section.
is.
3. Not every single word with a dot behind is a new paragraph. Sample:
display 'Something'
end-display.
Most false entries could be removed if there would be a check for the last "word" before: it has to be either the reserved word "section" or to be a dot.

The following are settings/entries of/for CTAGS in SourceCookifier, therefore they're maybe a problem in that plugin, not in this project here:
4. It would be nice to have the same functionality for data types in COBOL-sources as it is available for C-sources in functions: return the definition of a var as access/signature, the sample in 1. would result in the definition "PIC S9(7) usage comp-5" (would be nice for variables in C-sources, too [resulitn in "unsigned int" etc.]).
5. If possible a new builtin tag type "COPY files" would be nice (would be nice for include files in C-sources, too) .
6. COBOL is not case sensitive.

Thank you for your work!
sf-mensch