notepad-plus-plus / notepad-plus-plus/notepad-plus-plus
The function outline view does not recognize parameters when used semicolon in clipper (xbase)
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 29.4k
- Forks
- 5.4k
- PR merge metrics
- No merged PRs in 30d
Description
Description of the Issue
The function outline view does not recognize parameters when used semicolon in clipper (xbase).
In xbase dialects you can use semicolon for line continuation, so you can interrupt the code at an appropriate spot with a semicolon and continue on the next line. This helps to have a more readable code.
set filter to CUSTFILE->NAME == 'BRIGIT BARDO' .AND. ;
CUSTFILE->STATE == 'FRANCE'
Note function b doesn't show the second argument
Steps to Reproduce the Issue
Create a clipper source file with a function using a semicolon for line continuation after View -> Function List
Expected Behavior
All functions appear in function outline with all arguments regardless the use of semicolon
Actual Behavior
in a function declaration any information after a semicolon does not appear in function outline nor in code completion
Debug Information
Notepad++ v8.6.2 (32-bit)
Build time : Jan 14 2024 - 02:18:41
Path : C:\Program Files (x86)\Notepad++\notepad++.exe
Command Line :
Admin mode : OFF
Local Conf mode : OFF
Cloud Config : OFF
OS Name : Windows 10 Home (64-bit)
OS Version : 22H2
OS Build : 19045.4046
Current ANSI codepage : 1252
Plugins :
BetterMultiSelection (1.5)
BracketsCheck (1.2.2)
ccc (1.4.1)
CodeAlignmentNpp (14.1.107)
ColorPicker (2.3)
ColumnTools (1.4.5.1)
ComparePlugin (2.0.2)
ComparePlus (1.1)
DoxyIt (0.4.4)
ExtSettings (1.3.1)
IndentByFold (0.7.3)
JsMapParser.NppPlugin (4.2)
LocationNavigate (0.4.8.1)
mimeTools (3)
NavigateTo (2.6.4)
NppConverter (4.5)
NppExport (0.4)
NppQCP (2)
NppTaskList (2.5)
NppTextFX (1.4.1)
NppToolBucket (1.10.6622.41336)
QuickOpenPlugin (1.1)
TakeNotes (1.2.6)
Tidy2 (0.2)
WindowManager (1.2.2)
XMLTools (3.1.1.13)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue in a Clipper source file using a semicolon for line continuation in a function declaration, then inspect the function outline and code-completion behavior. The change is complete when all function arguments after the semicolon are recognized in both views.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100