Re: [Lazarus] RFC: Code tools Feature?

2014-03-27 Thread Marc Santhoff
On Do, 2014-03-27 at 13:09 +0100, Michael Van Canneyt wrote: > > On Thu, 27 Mar 2014, Martin Frb wrote: > > In addition, you do not need the IfDef. > > But I want the ifdef :) > > The reason is that I very often add some code inside the $IFDEF to check for > assigned props, params and whatnot

Re: [Lazarus] RFC: Code tools Feature?

2014-03-27 Thread Michael Van Canneyt
On Thu, 27 Mar 2014, Mattias Gaertner wrote: On Thu, 27 Mar 2014 09:22:21 +0100 (CET) Michael Van Canneyt wrote: [...] I would like to be able to specify a code snippet that is inserted at the start and end of a procedure [...] Similarly, I'd like to be able to specify a code snippet to in

Re: [Lazarus] RFC: Code tools Feature?

2014-03-27 Thread Michael Van Canneyt
On Thu, 27 Mar 2014, Mark Morgan Lloyd wrote: Michael Van Canneyt wrote: If the compiler could track the current procedure (or function, or class.method etc.) name, then couldn't that be done with a macro? Then the app source would be a less-obtrusive: Procedure TMyClass.MyMethod; begin_

Re: [Lazarus] RFC: Code tools Feature?

2014-03-27 Thread Michael Van Canneyt
On Thu, 27 Mar 2014, Martin Frb wrote: On 27/03/2014 08:22, Michael Van Canneyt wrote: The intended use is that the IDE generates stuff like Procedure TMyClass.MyMethod; begin {$IFDEF LOGPROCESSFLOW}Log('Entering TMyClass.MyMethod');{$ENDIF} {$ENDIF LOGPROCESSFLOW}Log('Exiting TMyClas

Re: [Lazarus] RFC: Code tools Feature?

2014-03-27 Thread Mark Morgan Lloyd
Michael Van Canneyt wrote: If the compiler could track the current procedure (or function, or class.method etc.) name, then couldn't that be done with a macro? Then the app source would be a less-obtrusive: Procedure TMyClass.MyMethod; begin_logged end_logged; I prefer not to use macros.

Re: [Lazarus] RFC: Code tools Feature?

2014-03-27 Thread Martin Frb
On 27/03/2014 08:22, Michael Van Canneyt wrote: The intended use is that the IDE generates stuff like Procedure TMyClass.MyMethod; begin {$IFDEF LOGPROCESSFLOW}Log('Entering TMyClass.MyMethod');{$ENDIF} {$ENDIF LOGPROCESSFLOW}Log('Exiting TMyClass.MyMethod');{$ENDIF} end; If I have speci

Re: [Lazarus] RFC: Code tools Feature?

2014-03-27 Thread Mattias Gaertner
On Thu, 27 Mar 2014 09:22:21 +0100 (CET) Michael Van Canneyt wrote: >[...] > I would like to be able to specify a code snippet that is inserted at the > start and end of a procedure >[...] > Similarly, I'd like to be able to specify a code snippet to insert > before/after the procedure header:

Re: [Lazarus] RFC: Code tools Feature?

2014-03-27 Thread Michael Van Canneyt
On Thu, 27 Mar 2014, Mark Morgan Lloyd wrote: Michael Van Canneyt wrote: Hi, Is it possible to have the following in the code tools: I would like to be able to specify a code snippet that is inserted at the start and end of a procedure (after begin, before end keywords). The code snippet s

Re: [Lazarus] RFC: Code tools Feature?

2014-03-27 Thread Mark Morgan Lloyd
Michael Van Canneyt wrote: Hi, Is it possible to have the following in the code tools: I would like to be able to specify a code snippet that is inserted at the start and end of a procedure (after begin, before end keywords). The code snippet should contains some macros like $(CLASSNAME) $(ME

[Lazarus] RFC: Code tools Feature?

2014-03-27 Thread Michael Van Canneyt
Hi, Is it possible to have the following in the code tools: I would like to be able to specify a code snippet that is inserted at the start and end of a procedure (after begin, before end keywords). The code snippet should contains some macros like $(CLASSNAME) $(METHODNAME). Conceivably, oth