-
Notifications
You must be signed in to change notification settings - Fork 16
Function declaration not handled #52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
…ackage (required for all issues regarding function location)
…unction class to allow local and global variable handling with regards to the function
into account. Test files updated accordingly
An error was corrected on the plugin.xml file on the SH.ERR.String rule. A localization error was corrected in SH.INST.GetOpts. The following rules did not need updating: COM.DATA.Invariant SH.DESIGN.Bash SH.INST.Interpreter SH.INST.Keywords SH.INST.Variables The following rules could not be updated with FNAME without errors appearing in their automatic tests: COM.FLOW.Recursion COM.INST.CodeComment COM.INST.Line COM.PRES.Indent SH.MET.PipeLine SH.FLOW.CheckCodeReturn They were either partially modified (COM.FLOW.Recursion, SH.FLOW.CheckCodeReturn), or left as they were.
The following rules could not be updated with FNAME without errors appearing in their automatic tests: Issue #137 has been created to allow for further investigation of the problem for each of these rules. |
failing after introducing FNAME. The issue was solved by removing \space from the SPACE token.
In all, 47 rules out of 49 now have the FUNCT token. The 2 remaining ones doen't require localization as they check the first line of the file and any violation found can only be in MAIN PROGRAM. |
…ackage (required for all issues regarding function location)
…unction class to allow local and global variable handling with regards to the function
…a wait situations
…ization, took "until" into account. Test files updated accordingly
An error was corrected on the plugin.xml file on the SH.ERR.String rule. A localization error was corrected in SH.INST.GetOpts. The following rules did not need updating: COM.DATA.Invariant SH.DESIGN.Bash SH.INST.Interpreter SH.INST.Keywords SH.INST.Variables The following rules could not be updated with FNAME without errors appearing in their automatic tests: COM.FLOW.Recursion COM.INST.CodeComment COM.INST.Line COM.PRES.Indent SH.MET.PipeLine SH.FLOW.CheckCodeReturn They were either partially modified (COM.FLOW.Recursion, SH.FLOW.CheckCodeReturn), or left as they were.
…e automatic tests were failing after introducing FNAME. The issue was solved by removing \space from the SPACE token.
(required for all issues regarding function location)
global variable handling with regards to the function
into account. Test files updated accordingly
An error was corrected on the plugin.xml file on the SH.ERR.String rule. A localization error was corrected in SH.INST.GetOpts. The following rules did not need updating: COM.DATA.Invariant SH.DESIGN.Bash SH.INST.Interpreter SH.INST.Keywords SH.INST.Variables The following rules could not be updated with FNAME without errors appearing in their automatic tests: COM.FLOW.Recursion COM.INST.CodeComment COM.INST.Line COM.PRES.Indent SH.MET.PipeLine SH.FLOW.CheckCodeReturn They were either partially modified (COM.FLOW.Recursion, SH.FLOW.CheckCodeReturn), or left as they were.
failing after introducing FNAME. The issue was solved by removing \space from the SPACE token.
Problem
For shell languages, it's possible to declare a new function by several ways. However, some analyzers require the shell function to be declared with the keyword
function
before the function's name while it's optional.How to fix
Adding a new transition FUNCT to handle this declaration independantly to the keyword one on function declaration to retrieve function's name.
Also, make FUNCT identifier using FNAME identifier as function's name instead of VAR one.
Fix status
The text was updated successfully, but these errors were encountered: