> On May 5, 2020, at 4:35 PM, Mattias Gaertner via fpc-pascal
> wrote:
>
> Yes, recording is a todo.
> If you want to check this you have to use the parsing functions like
> ProcNodeHasSpecifier or MoveCursorToProcSpecifier.
Why don't the nodes keep track of this information btw? That was the
On Tue, 5 May 2020 11:19:34 +0200 (CEST)
Michael Van Canneyt wrote:
> On Tue, 5 May 2020, Ryan Joseph via fpc-pascal wrote:
>
> >
> >
> >> On May 5, 2020, at 3:56 PM, Michael Van Canneyt
> >> wrote:
> >>
> >> They are in the system unit, so they're always related to any unit.
> >>
> >> They
On Tue, 5 May 2020, Ryan Joseph via fpc-pascal wrote:
On May 5, 2020, at 3:56 PM, Michael Van Canneyt wrote:
They are in the system unit, so they're always related to any unit.
They have a compilerproc modifier set, so I suppose there is some
property/attribute of the identifier that ind
> On May 5, 2020, at 3:56 PM, Michael Van Canneyt
> wrote:
>
> They are in the system unit, so they're always related to any unit.
>
> They have a compilerproc modifier set, so I suppose there is some
> property/attribute of the identifier that indicates this modifier.
> You should check for
On Tue, 5 May 2020, Ryan Joseph via fpc-pascal wrote:
Code tools completions are returning functions that don't appear related to the current
unit such as "fpc_Copy" from /usr/local/share/fpcsrc/rtl/inc/compproc.inc.
Here's a snippet of the code I use to get identifiers.
if CodeToolBos
Code tools completions are returning functions that don't appear related to the
current unit such as "fpc_Copy" from
/usr/local/share/fpcsrc/rtl/inc/compproc.inc.
Here's a snippet of the code I use to get identifiers.
if CodeToolBoss.GatherIdentifiers(Code,X + 1,Y + 1) then
begin
