Interpreter bypasses overloaded logical negation

Open
#2,122 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
47/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
java, perl
Domain
backend, testing

Research direction

Start with CompileOperator.visitOperator, the interpreter’s NOT handler, and MathOperators.not()/Overload.bool_not() to trace how overloaded negation differs across backends. First run the focused reproducer and the unchanged Math-Logic 1.19 t/logic.t suite on system Perl, the JVM backend, and the interpreter. Done means a project regression passes on both backends, raw negation still works under no overloading, and all 332 upstream assertions pass.

Written by the indexing model from the issue text.

Description

area:backend area:cpan-port area:runtime bug

Summary

Math::Logic 1.19's upstream t/logic.t fails five assertions under PerlOnJava when negating overloaded objects with !. System Perl passes the complete suite. A focused reproducer confirms that the PerlOnJava interpreter returns a plain boolean instead of invoking the class's overloaded ! method.

Evidence

  • CPAN random-tester run: 20261119-133823-51077.
  • Distribution: pure-Perl Math-Logic 1.19; no XS/native dependency.
  • System Perl 5.42.2: t/logic.t passes all 332 tests.
  • PerlOnJava: 5/332 tests fail (tests 230, 260, 278–280), all in ! assertions for three-valued or multi-valued logic. The same failures reproduce with the JVM-default launcher and --interpreter on source 543f9dfef.
  • Focused reducer: system Perl and the JVM backend return a Math::Logic object for the overloaded negation; the interpreter returns a scalar and fails the result-type/value assertion.
use Math::Logic qw($UNDEF);
my $x = Math::Logic->new(-value => $UNDEF, -degree => 3, -propagate => 1);
my $negated = !$x;
die "expected Math::Logic result\n"
    unless ref($negated) eq 'Math::Logic' && $negated == $UNDEF;

Root cause

The interpreter compiler emits Opcodes.NOT when overloading is enabled (CompileOperator.visitOperator). The interpreter's NOT handler currently calls RuntimeScalar.getBoolean() and stores a cached plain true/false scalar. It does not route through MathOperators.not() or Overload.bool_not(), so it skips the (! overload. NOT_NO_OVERLOAD is a separate opcode and should remain the raw-boolean path.

The JVM implementation routes logical negation through MathOperators.not(), which calls Overload.bool_not() for overloaded values. The focused JVM reducer passes, but the complete upstream test still fails five assertions through the default launcher. That state-dependent full-suite failure must also be reduced and resolved before claiming distribution compatibility.

Acceptance criteria

  • Add a project-owned regression for overloaded !, validate it with system Perl first, and make it pass on the JVM and interpreter.
  • Preserve raw boolean behavior under no overloading.
  • Reduce and resolve the five full-suite failures, including the discrepancy between the passing focused JVM case and failing t/logic.t run.
  • Pass the unchanged Math-Logic 1.19 t/logic.t suite (332/332) on both PerlOnJava backends.

Related issue search

No existing issue was found for overloaded unary !. #2074 covers separate Set::Scalar parser and binary-operation failures; #2007 covers recursive re-dispatch of an active overload handler.

Dominant language
Perl
Stars
67
Forks
8
Avg merge
5h 12m
Merged PRs (30d)
131

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from fglock/PerlOnJava

All issues in fglock/PerlOnJava

Similar issues

More Perl issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.