octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #64831] Split chained subsrefs to multiple ins


From: Petter
Subject: [Octave-bug-tracker] [bug #64831] Split chained subsrefs to multiple instructions
Date: Sat, 28 Oct 2023 09:57:19 -0400 (EDT)

URL:
  <https://savannah.gnu.org/bugs/?64831>

                 Summary: Split chained subsrefs to multiple instructions
                   Group: GNU Octave
               Submitter: petter
               Submitted: Sat 28 Oct 2023 01:57:17 PM UTC
                Category: None
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: None
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
                 Release: dev
         Discussion Lock: Any
        Operating System: GNU/Linux
           Fixed Release: None
         Planned Release: None


    _______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: Sat 28 Oct 2023 01:57:17 PM UTC By: Petter <petter>

To allow for bytecode calls in the middle of a chained subsref, instead
of allocating a new bytecode interpreter for chained calls. I.e. the vm
need a separate instruction to return to, for each chained subsref.

Use a wrapper octave_base_value derived class to support collecting
arguments for a classdef subsref.


The patch builds on:
https://savannah.gnu.org/bugs/?64827
https://savannah.gnu.org/bugs/?64829
https://savannah.gnu.org/bugs/?64830






    _______________________________________________________
File Attachments:


-------------------------------------------------------
Date: Sat 28 Oct 2023 01:57:17 PM UTC  Name: octave_32628.patch  Size: 49KiB  
By: petter

<http://savannah.gnu.org/bugs/download.php?file_id=55283>

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?64831>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]