----- Original Message ----- From: "Mattias Gaertner" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Sunday, April 29, 2007 11:40 AM
Subject: Re: [lazarus] Codetools question


On Sat, 28 Apr 2007 21:10:03 +0200
"Darius Blaszijk" <[EMAIL PROTECTED]> wrote:

I have some codetools questions, can anyone help?

- retrieve the list of available classes in the interface section of
a unit

What do you mean with 'available'?
To find all classes defined in an interface:
I added an example:
components/codetools/examples/listinterfaceclasses.lpi.
This is exaclty what I mean


- set a list of search directories for include files in a unit

The codetools use a rule set to define the settings for each directory
(define templates). To set the the include search path for a directory,
add a rule to define the #IncPath for this directory.
This is normally done by Lazarus.
You can not define rules for single units.
You can easily add your own rules. But keep in mind, that Lazarus does
not know, what you are doing, so the built in checks of the IDE might
give misleading messages.
If you use the codetools without Lazarus, then it is
recommended to define rules.
I added an example:
components/codetools/examples/setincludepath.lpi.
Thanks Mattias, this is also what I was looking for. I am developing a tool "maketest" that uses the codetools to create a skeleton class for each class inside a unit. Running maketest again updates the output file if methods are added or deleted later. I feel that this tool should be part of Lazarus once I get the basic functionality there.

Darius



What methods should I be looking at?


Mattias

_________________________________________________________________
    To unsubscribe: mail [EMAIL PROTECTED] with
               "unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives

_________________________________________________________________
    To unsubscribe: mail [EMAIL PROTECTED] with
               "unsubscribe" as the Subject
  archives at http://www.lazarus.freepascal.org/mailarchives

Reply via email to