[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #65308] bytecode interpreter: incorrect number
From: |
Fernando |
Subject: |
[Octave-bug-tracker] [bug #65308] bytecode interpreter: incorrect number of output arguments |
Date: |
Tue, 13 Feb 2024 13:43:59 -0500 (EST) |
URL:
<https://savannah.gnu.org/bugs/?65308>
Summary: bytecode interpreter: incorrect number of output
arguments
Group: GNU Octave
Submitter: tutissanalio
Submitted: mar 13 feb 2024 18:43:59
Category: Interpreter
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: Missed Error or Warning
Status: None
Assigned to: None
Originator Name:
Originator Email:
Open/Closed: Open
Release: dev
Discussion Lock: Any
Operating System: Any
Fixed Release: None
Planned Release: None
_______________________________________________________
Follow-up Comments:
-------------------------------------------------------
Date: mar 13 feb 2024 18:43:59 By: Fernando <tutissanalio>
While investigating bug #64783, I found another bug in the bytecode
interpreter, related to the number of output arguments.
>> __vm_enable__ (1)
>> f=@(x)[x{:}];
>> [a,b]=f({5,9})
a = 5
b = 9
Note that this should give an error (we are asking 2 outputs from f, but f
should return only 1 output vector). Disabling the bytecode interpreter
produces the correct result.
>> __vm_enable__ (0)
>> f=@(x)[x{:}];
>> [a,b]=f({5,9})
a =
5 9
error: element number 2 undefined in return list
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?65308>
_______________________________________________
Mensaje enviado vía Savannah
https://savannah.gnu.org/
- [Octave-bug-tracker] [bug #65308] bytecode interpreter: incorrect number of output arguments,
Fernando <=