Download the PHP package ozhantr/ebnf without Composer
On this page you can find all versions of the php package ozhantr/ebnf. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package ebnf
EBNF
Framework-agnostic PHP 8.2+ library for reading .ebnf grammar files, parsing EBNF syntax, analyzing grammar definitions, and validating input against those grammars.
What Is EBNF?
EBNF stands for Extended Backus-Naur Form.
It is a formal notation used to describe the syntax of a language or mini-language. Developers often use EBNF to define things like:
- search query languages
- filter expressions
- calculator-like expressions
- config formats
- small domain-specific languages
What This Library Does
This library helps you work with grammars defined in EBNF.
You can use it to:
- read
.ebnfgrammar files from disk - parse those grammar definitions into a structured AST
- analyze grammars for semantic issues
- validate user input against a chosen grammar rule
- report syntax errors with line and column information
In practice, this is useful when you want to build features such as custom query inputs, textarea validation, editor tooling, or mini-DSL parsers in PHP.
Typical Use Cases
You might use this library when you want to:
- validate a custom search or filter input
- parse a small expression language
- define and enforce a config file format
- build grammar-driven textarea or editor validation
- experiment with or debug EBNF grammars in PHP
EBNF Syntax Basics
This library currently supports a practical subset of EBNF syntax:
rule = expression ;defines a grammar rulea , bmeansafollowed byba | bmeansaorb[ a ]makesaoptional{ a }meansacan repeat zero or more times( a )groups expressions"text"matches a literal string/.../matches a regex terminalidentifierreferences another rule
See docs/grammar-syntax.md for a fuller syntax guide.
Features
- Strictly typed token system
- Line/column-aware lexer
- Recursive descent parser
- Immutable AST nodes
- Rich syntax exceptions
- Support for inline grammar strings and
.ebnfgrammar files - Regex terminals such as
/^[a-z]+/ - Grammar analyzer for duplicate, undefined, and unreachable rules
- Runtime validation with line/column-aware syntax errors
- JSON export and pretty-print helpers
Key Terms
Lexer: breaks grammar text into small meaningful pieces calledtokens, such as names, strings, and symbols.Parser: turns those tokens into a structured grammar model.AST: an Abstract Syntax Tree, the structured representation of a parsed grammar.
Installation
Development Setup
If you want to work on the library itself:
Quick Start
Parse a grammar definition into an AST:
Regex terminals are also supported:
You can also load a .ebnf file from disk and parse it:
Example grammar files in this repository:
- examples/grammars/task-search.ebnf
- examples/grammars/calculator.ebnf
- tests/Fixtures/config.ebnf
Validate real input against a start rule:
Analyze a grammar for semantic issues:
End-to-End Example
Imagine that you want to validate a custom search box in your application.
- Define the search syntax in an EBNF grammar file such as examples/grammars/task-search.ebnf.
- Parse that grammar into an AST.
- Use the runtime layer to validate real user input against a start rule.
For example, this input is valid for the search_request rule:
And this input is invalid:
The runtime validator can report that failure with line and column information, which makes it suitable for textarea validation, editor tooling, or custom query inputs.
Architecture
The library is organized into separate grammar parsing, runtime validation, analyzer, and export layers. See docs/architecture.md for the current design.
Examples Guide
For a short guide to each script in examples/, see docs/examples.md.
Running Examples
Install dependencies first if you are working from the repository source:
See examples/basic.php for the runnable example.
Additional examples:
Current Scope
Supported today:
- Rule definitions, choices, sequences, optionals, repetitions, and grouping
- String and regex terminals
- Grammar AST export and pretty-printing
- Runtime validation against a chosen start rule
- Semantic grammar analysis
Not yet supported:
- Native EBNF comments such as
(* ... *) - Match tree generation
- Advanced ambiguity or recursion analysis
