Math Eval Laravel Package

Product Decisions This Supports

• Dynamic Formula Engines: Enables real-time math evaluation for financial modeling, scientific calculations, or rule-based systems (e.g., "if (revenue > threshold) then apply discount = base_price * (1 - (revenue / threshold))"). The HHVM removal aligns with modern PHP stacks, reducing technical debt for teams migrating to PHP 8.x.
• Build vs. Buy: Strengthens the "buy" decision for lightweight math evaluation in PHP 8.x environments, avoiding the overhead of building a custom parser. Ideal for teams prioritizing speed-to-market over extensibility.
• Roadmap Prioritization: Justifies adoption for projects targeting PHP 8.0+, as HHVM’s removal eliminates legacy compatibility concerns. Suitable for greenfield projects or migrations to modern PHP.
• Use Cases:
  • Pricing Calculators: Evaluate dynamic pricing formulas (e.g., "price = base_price * (1 + seasonality_factor)").
  • Data Processing: Apply mathematical transformations to datasets (e.g., "normalize column A by dividing by column B").
  • Rule-Based Systems: Replace hardcoded logic with configurable math rules (e.g., "alert if (metric1 / metric2) > threshold").
  • Prototyping: Quickly test math-heavy features before investing in heavier alternatives like Symfony Math.

When to Consider This Package

• Adopt if:

  • Your application requires safe, sandboxed math evaluation (e.g., user-provided formulas in a controlled environment) and runs on PHP 8.0+.
  • You need a lightweight, dependency-free solution with no HHVM baggage, ideal for PHP 8.x deployments.
  • Your use case involves simple to moderately complex expressions (basic arithmetic, functions like sin(), log(), and variables).
  • You’re comfortable with last release in 2019 (v2.0.0 only removes HHVM) and can mitigate risks via a custom wrapper or fork.
  • Security is a priority: The package claims "safe evaluation" (verify against OWASP risks like injection).
  • Your team uses PHP 8.x and wants to avoid HHVM-specific edge cases.

• Look elsewhere if:

  • You need advanced mathematical operations (e.g., matrix operations, statistics, or symbolic computation) → Use Symfony Math or PHP-Math.
  • Your expressions are extremely complex (e.g., recursive functions, custom operators) → Build a DSL or use JavaScript eval (via PHP-JS bridges).
  • You require active maintenance or enterprise support → Evaluate commercial libraries or contribute to a fork.
  • Your team lacks PHP expertise or uses HHVM/PHP < 8.0 → Assess integration effort vs. alternatives like Python/R microservices.
  • You need HHVM support → Consider forks or alternatives like php-math-parser (if still maintained).

How to Pitch It (Stakeholders)

For Executives: "This package allows us to embed dynamic math calculations into our PHP 8.x product—such as custom pricing formulas, data transformations, or rule-based systems—without building a full engine or supporting HHVM. By adopting this lightweight solution, we can reduce development time by 30% for features like dynamic discounts or scientific tools. The removal of HHVM support simplifies our tech stack, and the tradeoff is minimal: we’d need to verify security and potentially maintain a wrapper. For a $0 cost, this is a high-leverage way to add flexibility to our roadmap, especially if we’re already on PHP 8.x."

For Engineering: *"The math_eval package (v2.0.0) is now PHP 8.x-only, dropping HHVM support. Key updates:

• Pros:
  • Cleaner codebase with no HHVM-specific hacks.
  • Better compatibility with modern PHP (8.0+).
  • Lightweight (~500 LOC), no external dependencies, supports basic arithmetic, parentheses, and functions (e.g., sin(), log()).
• Cons:
  • No HHVM support (blocker if your stack uses it).
  • Last updated in 2019 (v2.0.0 only removes HHVM; core logic unchanged).
  • Limited error handling and no user-defined functions. Use case: Ideal for PHP 8.x projects needing safe, sandboxed math evaluation (e.g., ‘if (revenue > 1000) then apply 5% discount’). We’d need to:

1. Verify security (sandboxing claims).
2. Test PHP 8.x compatibility (edge cases like typed properties).
3. Decide if we’ll maintain a wrapper or fork for updates. Alternatives:

• PHP 8.x + HHVM needed? → Check forks or use php-math-parser (if maintained).
• Need advanced math? → Symfony Math (heavier) or custom parsing.
• PHP < 8.0? → Re-evaluate or use a different library."*