I really like NP++ having COBOL integrated and do not need to make an own scheme. I recognized a big problem and have some FRs:
1. Error: Comments aren't marked at all because the asterisk * in column seven (or *> for free format in every column you like) is seen as operator (COBOL only has line comments like // for C, no comment areas).
2. FR: Code folding - every end-… should be the folding end from its … pendant. For example if/end-if evaluate/end-evaluate
3. FR: Please give us an input field for PREPROCESSOR words in "Settings->Style Configurator". Among COBOLers there are a lot of different preprocessors used and it would be good to be able to just put all preprocessor words there.
4. FR: Please add all COBOL keywords, I can give you a list of the missing ones (context sensitive and non context sensitive) if you explain the difference if KEYWORD and INSTRUCTION WORD to me.
Thank you very much,
sf-mensch
4.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
1+2 are submitted to Scintilla project.
3 Is special: Scintilla defines the Preprocessor style but no Preprocessor keywords. As written before there are a lot of different preprocessors used by COBOLers and it would be good to be able to just put all preprocessor words one needs in an input field in NP++ config.
4 Will be a submitted patch for Scintilla some day (please explain what KEYWORD and INSTRUCTION WORD are in NP++).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
About preprocessors: I don't know a thing in Cobol, but chances are that what the lexer thinks is a preprocessor directive is hardcoded in LexCobol.cxx. Did you check this file?
KEYWORD and friends are externals identifiers for keyword lists some of which can be configured, as chosen by the lexer. For instance, DECLARATION maps to the "insre1" keyword list name that you can find in langs.xml.
Btw the Obsidian theme is completely out of sync concerning cobol, and lists completely different extensions and keywords.
CChris
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Updates:
1/ I checked LexCOBOL.cxx, and preprocessor directives are any lines that start with a ? in the first column. What can be configured there?
2/ I can no longer reproduce it, but on switching to a different theme that does not support cobol, the Styler Configurator list was still showing "COBOL", though the rest of the dialog had nothing to do with cobol. For instance, the C language was bound to the .cmake extension.
CChris
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi!
I really like NP++ having COBOL integrated and do not need to make an own scheme. I recognized a big problem and have some FRs:
1. Error: Comments aren't marked at all because the asterisk * in column seven (or *> for free format in every column you like) is seen as operator (COBOL only has line comments like // for C, no comment areas).
2. FR: Code folding - every end-… should be the folding end from its … pendant. For example if/end-if evaluate/end-evaluate
3. FR: Please give us an input field for PREPROCESSOR words in "Settings->Style Configurator". Among COBOLers there are a lot of different preprocessors used and it would be good to be able to just put all preprocessor words there.
4. FR: Please add all COBOL keywords, I can give you a list of the missing ones (context sensitive and non context sensitive) if you explain the difference if KEYWORD and INSTRUCTION WORD to me.
Thank you very much,
sf-mensch
4.
Cobol support is done from Scintilla, so chances are that most of the issues are with their lexer. They should be reported to the Scintilla project.
CChris
1+2 are submitted to Scintilla project.
3 Is special: Scintilla defines the Preprocessor style but no Preprocessor keywords. As written before there are a lot of different preprocessors used by COBOLers and it would be good to be able to just put all preprocessor words one needs in an input field in NP++ config.
4 Will be a submitted patch for Scintilla some day (please explain what KEYWORD and INSTRUCTION WORD are in NP++).
About preprocessors: I don't know a thing in Cobol, but chances are that what the lexer thinks is a preprocessor directive is hardcoded in LexCobol.cxx. Did you check this file?
KEYWORD and friends are externals identifiers for keyword lists some of which can be configured, as chosen by the lexer. For instance, DECLARATION maps to the "insre1" keyword list name that you can find in langs.xml.
Btw the Obsidian theme is completely out of sync concerning cobol, and lists completely different extensions and keywords.
CChris
Updates:
1/ I checked LexCOBOL.cxx, and preprocessor directives are any lines that start with a ? in the first column. What can be configured there?
2/ I can no longer reproduce it, but on switching to a different theme that does not support cobol, the Styler Configurator list was still showing "COBOL", though the rest of the dialog had nothing to do with cobol. For instance, the C language was bound to the .cmake extension.
CChris