This is the code documentation for the Pelzini project
Search documentation |
namespace processorClassesGeneric language analyser. Analysers are used to tranform the language-specific tokens into a set of ParserItems Analyses the C tokens, and creates a set of ParserItem objects. Tokenises a C file. Stores information about parser items that are actual source code. Typically these parser items have authors and versions, so all of that information is stored in this class. Stores the processor configuration Does the complete parsing of a C file. Outputs the tree to a database. Outputs the tree to the screen This is a transformer that does quality checks on the codebase It checks that the documentation has the required tags. Currently the 'required tags' are only the summary The documentation is created in a report called the check report. Analyses the javascript tokens, and creates a set of ParserItem objects. Tokenises a javascript file. Does the complete parsing of a javascript file. Outputs the tree to a metadata file Outputs the tree as MySQL The top-level class for all outputters Represents a function argument Represents an author of a parser item (e.g. a ParserFunction or ParserClass) Stores information about a specific class Represents a constant Represents a function Represents an enumeration Represents a file Represents a function Represents an interface The top-level class of all parser items. Almost all ParserItems should extend CodeParserItem. Represents a function return type Represents the contents of a @table tag Represents an exception which is thrown Represents a variable This is the parser for PHP files. It converts a file from the raw PHP into a document tree Outputs the tree to a PostgreSQL database This is a transformer that does quality checks on the codebase It checks that the documentation has the required tags. Currently the 'required tags' are only the summary The documentation is created in a report called the check report. Outputs the tree to a SQLite database This class is used to represent a token that has been tokenised using a Lexer. (e.g. the JavascriptLexer) These tokens are used to create various ParserItems, by passing them to an Analyser (e.g. the JavascriptAnalyser) The top-level class of all transformers. Transformers alter the parser model before it is outputted, for creating reports, etc. VirtualEnumerationsTransformer This transformer converts constants that start with the same name into an enumeration of that name. So if a file has the following constants: APP_VERSION ITEM_TYPE_APPLE ITEM_TYPE_ORANGE The APPLE and ORANGE constants will become a part of the virtual enumeration ITEM_TYPE. Outputs the tree to an xml file FunctionsGets all the filenames in a directory and in the subdirectories Does processing on a single HTML tag, as provided by a regex in htmlify_text This will take the provided text, and turn it into HTML If it contains HTML, it will validate it, otherwise it will wrap everything in a PRE This function also removes extra spaces from the beginning of lines but will do so in a manner that indenting is preserved Outputs a status message Parses a DocBlock comment tag Accepts the raw comment text of the comment straight from the file, including all the stars in the middle Returns an array of tags. Each paremeter will contain an array of the tags that existed, one for each tag The summary is returned in a 'summary' tag. The output for a function with two param tags, a return tag and a summary will be something like the following: array { ['@summary'] = '...', ['@param'] { [0] = '...', [1] = '...' }, ['@return'] { [0] = '...', } } Processes the parsing of an individual tag Automatically loads the classes that are needed Processes the javadoc tags for a specific parser item |
Powered by Pelzini, version 0.9.0 |
Documentation is made available under the
GNU Free Documentation License 1.2. Generated: Thursday, 15th March, 2018 at 02:05 pm |