How armoha/eudplib works
Main Components
a. Core Components:
• EPScript Compiler (src/epscript)
• EUDPLib Core (src/eudplib/core)
• Read/Write System (src/eudplib/maprw)
• Memory I/O System (src/eudplib/memio)
• Rust Backend (src/rust)
b. Supporting Components:
• Collections Library (src/eudplib/collections)
• String Handling (src/eudplib/string)
• Trigger System (src/eudplib/trigger)
• StarCraft Data Handlers (src/eudplib/scdata)
• Utility Functions (src/eudplib/utils)
┌─────────────────────────────────────────┐
• User Interface │
• (EPScript Language & Python API) │
• ┤
• High-Level Features │
• (Collections, String, Trigger System) │
• ┤
• Core Systems │
• (EUDPLib Core, Memory I/O, MapRW) │
• ┤
• Native Backends │
• (Rust Components, EPScript DLL) │
• ┘
Key Relationships
a. Data Flow:
• EPScript source → Compiler → Python bytecode
• Data → MapRW → Core Systems
• Memory operations through the Rust backend
b. Dependencies:
• Core systems' reliance on native backends
• High-level features' usage of core systems
• String and trigger systems' integration
Additional Elements
• Component types
• Language indicators
• Special markers
b. Annotations for:
• File formats handled
• Key APIs
• Integration points
• Performance-critical paths
Implementation Details
• Clear hierarchical layout
• Consistent styling
• Proper spacing
• Readable fonts
• Detailed but uncluttered connections
Specific Component Details
a. EPScript Compiler:
• Lexer/parser pipeline
• Optimization stages
• Code generation points
b. Core Systems:
• Detail memory management
• Trigger processing
• Map manipulation flows
c. Native Backends:
• FFI boundaries
• Memory allocation systems
• Performance-critical paths