Re: [Lazarus] Code explorer implementation

2019-09-14 Thread Sven Barth via lazarus
Ryan Joseph via lazarus schrieb am Sa., 14. Sep. 2019, 20:18: > > > > On Sep 14, 2019, at 2:07 PM, Michael Van Canneyt via lazarus < > lazarus@lists.lazarus-ide.org> wrote: > > > > By default, FPC also does not allow C style operators. > > > > You need to provide the -Sc command-line flag to the

Re: [Lazarus] Code explorer implementation

2019-09-14 Thread Michael Van Canneyt via lazarus
On Sat, 14 Sep 2019, Ryan Joseph via lazarus wrote: On Sep 14, 2019, at 2:07 PM, Michael Van Canneyt via lazarus wrote: By default, FPC also does not allow C style operators. You need to provide the -Sc command-line flag to the parser or set the appropriate flag manually on the parser

Re: [Lazarus] Code explorer implementation

2019-09-14 Thread Ryan Joseph via lazarus
> On Sep 14, 2019, at 2:07 PM, Michael Van Canneyt via lazarus > wrote: > > By default, FPC also does not allow C style operators. > > You need to provide the -Sc command-line flag to the parser or set the > appropriate flag manually on the parser object. I tried using -Mobjfpc because I

Re: [Lazarus] Code explorer implementation

2019-09-14 Thread Michael Van Canneyt via lazarus
On Sat, 14 Sep 2019, Ryan Joseph via lazarus wrote: On Sep 13, 2019, at 12:19 PM, Michael Van Canneyt via lazarus wrote: You can also try the fcl-passrc sources. It is standalone by design, and can give you all info that lazarus gives you. Thanks Michael this looks like exactly what

Re: [Lazarus] Code explorer implementation

2019-09-14 Thread Michael Van Canneyt via lazarus
On Sat, 14 Sep 2019, Ryan Joseph via lazarus wrote: A follow up. I built the parsepp.pp program and used it to parse a file. Everything seems to work except it tries to follow include macros (that would be nice to turn off since it requires compiler flags to work properly) and += operators

Re: [Lazarus] Code explorer implementation

2019-09-14 Thread Ryan Joseph via lazarus
A follow up. I built the parsepp.pp program and used it to parse a file. Everything seems to work except it tries to follow include macros (that would be nice to turn off since it requires compiler flags to work properly) and += operators are causing errors. Why doesn’t it know c style

Re: [Lazarus] Code explorer implementation

2019-09-14 Thread Ryan Joseph via lazarus
> On Sep 13, 2019, at 12:19 PM, Michael Van Canneyt via lazarus > wrote: > > You can also try the fcl-passrc sources. It is standalone by design, and can > give you all info that lazarus gives you. Thanks Michael this looks like exactly what I want. How well do they keep up with new syntax

Re: [Lazarus] Code explorer implementation

2019-09-13 Thread Michael Van Canneyt via lazarus
On Fri, 13 Sep 2019, Ryan Joseph via lazarus wrote: I want to make a tool that can analyze source files for functions/classes etc... that can be used for auto complete in 3rd party editors. I see Lazarus already has such a “Code Explorer” feature and I wonder how it gets this information

[Lazarus] Code explorer implementation

2019-09-13 Thread Ryan Joseph via lazarus
I want to make a tool that can analyze source files for functions/classes etc... that can be used for auto complete in 3rd party editors. I see Lazarus already has such a “Code Explorer” feature and I wonder how it gets this information and if I could scavenge it from the project. Does anyone