query find-callers
Lists callers of a routine by name, with an option to restrict results to precise, resolved callers.
Read this to see who calls a routine. Give it the bare member name; with --resolved it keeps only precise, resolved callers and also shows who reads or writes a property or field.
How to run it
Full flag list: query in the CLI reference.
Flags
| Flag | Argument | Meaning | Default |
|---|---|---|---|
--name | <callee-name> | ||
--context | N | ||
--resolved | precise callers via resolved call_edges (grouped by target, certain|ambiguous); a PROPERTY/FIELD name lists its bound accesses [certain, read|write]; an ENUM VALUE name lists each bound read [certain, read] (resolver 1.6.0-alpha) | ||
--db | |||
--json |
Where to click
- RAD Studio main menu: drag-lint > Find Usages...
Pitfalls
- the BARE member name. --name TFoo.Bar silently returns 0; --name Bar returns the sites.
Details
Lists callers of a routine by name, with an option to restrict results to
precise, resolved callers. Reach for it to see who calls a given routine
across the index -- and, with --resolved, who reads or writes a property or
field and who reads an enum value.
Running it from the CLI
drag-lint query find-callers --name <callee-name> [--context N] [--resolved] [--db ...] [--json]--name is the callee to look up -- the bare member name. `--name
TFoo.Barsilently returns 0 rows;--name Bar` returns the call sites.
--context N adds N lines of surrounding source.
Plain vs --resolved
Without --resolved the answer is every site whose NAME matches -- complete,
but a same-named routine elsewhere is listed too. --resolved answers from
what the resolver bound, grouped by target:
| You name | --resolved lists | Tag |
|---|---|---|
| a routine | its resolved call sites (call_edges) | certain or ambiguous |
| a property or field | every bound access (member_accesses) | [certain, read] / [certain, write] |
| an enum value | every bound READ, bare (cmdDelta) or qualified (TCommandID.cmdDelta) -- one row per site | [certain, read] |
A write through Self (Self.FFlag := False) is listed as [certain, write] on
an index parsed with extractor 1.20.0-alpha or later -- earlier it was indexed as
a READ -- and it always names the field, even when a local of the same name is
in scope.
The enum-value rows need an index resolved at resolver 1.6.0-alpha or later;
an older index answers 0 until index --all --resolve-only has run. A read the
resolver DECLINED (two visible candidates, or a same-named local, constant or
member in scope) is not listed, so an absent caller means "not bound with
certainty", never "not present".
Which line a row names. Every --resolved row -- call, property/field
access, enum-value read, parenless call, callback -- names the CALL SITE: the
text form prints (<file>:<site line>) and the JSON line key is the same
number. The caller routine's own declaration line is a separate JSON key,
caller_line, omitted when the enclosing routine is unknown (a unit-level
reference). Key order: `caller_qname, file, confidence, target_qname, line,
caller_line, mode. Before 2026-09-23 the JSONline` on every row except a
callback was the caller's DECLARATION line, and the text form printed no line
for those rows.
Two known wrong-bind risks, both on BARE enum reads only. Inside a with
whose target the index cannot type (since resolver 1.8.0-alpha the with scope
is modelled, and wherever the target types a with member wins), and inside a
{$SCOPEDENUMS ON} unit, a bare name can bind to an enum value the compiler
would not have chosen. Verify such a binding against the declaration.
Qualified reads (TEnum.Value) are unaffected.
Reaching it in the IDE
Not reachable through a main-menu item. The plugin's CodeLens cache
(DragLint.Plugin.CodeLensCache.pas) runs it to power the inline
caller-count annotations in the editor.
What it needs
The --db flag is optional -- drag-lint auto-resolves the index when
omitted. An index must still exist.
Example
Illustrative:
drag-lint query find-callers --name DoWork --resolved --db C:\Projects\MyApp\_D-RAG\MyApp.sqlite
drag-lint query find-callers --name cmdDelta --resolved --json --db C:\Projects\MyApp\_D-RAG\MyApp.sqliteThe first lists every resolved caller of every routine named DoWork,
grouped by target as certain or ambiguous. The second lists every bound read
of the enum value cmdDelta, tagged [certain, read].
For the same data as a chart, see ask who-calls and
ask protocol-trace.