scriptlog:start
This is an old revision of the document!
Table of Contents
Scriptlog Source Documentation
This wiki documents the Scriptlog codebase as it exists on disk. It is generated directly from the PHP source by static analysis, so it describes what the code does rather than what it was intended to do.
What is covered
^ Measure ^ Count ^ | Files analysed | 826 | | Classes, interfaces, traits, enums | 430 | | Methods | 4768 | | Standalone functions | 626 |
Excluded from generation: `lib/vendor/`, `lib/core/HTMLPurifier/`, `node_modules/` and `vendor-bin/`. Those trees are third-party code and are not Scriptlog behaviour.
How to read this documentation
- Start from the module index to find the layer you care about.
- Module pages list every type and file in that layer, with member counts and line spans.
- Type pages give the declaration, the full member tables, the signature of every method, and its documentation block rendered as prose.
- A type link in a signature column means the type is documented; a plain monospace name means it is a built-in or third-party type.
- Cross-links between layers are the fastest way to see the real call graph, because the extractor records every `use` statement and every declared type.
Caveats
- Extraction is purely structural. A method body is not analysed, so a `throw` or a `new` inside a body is only visible where the source declares it in the signature or in an `@throws` tag.
- The locator column shows the line where a member is declared, not where its behaviour lives.
- An empty summary means the source has no docblock there. That is itself a finding, not a generator failure.
- These pages are regenerated wholesale. Local edits are lost.
Generated by `tools/gendoc`.
scriptlog/start.1790413766.txt.gz · Last modified: by admin
