[Octave-bug-tracker] [bug #64977] Explore options for the bytecode interpreter in Octave 9

[Nicholas Jankowski]

Follow-up Comment #8, bug#64977 (group octave):

I share your concern that moving it to a feature branch, which we do not often
use in Octave's development process, puts it at risk of developing slower if
for no other reason than it won't be there to 'get in the way' as people work
on other things. Unfortunately, as we mainly only work with one development
branch, that simpler approach means that on a major release _everything_ from
that dev branch will get merged into the stable branch whether it's ready or
not.  That's what happened here with the VM / bytecode interpreter.  Out of
concern that it still may not be ready for stable with Octave 10, the feature
branch was the best method of keeping it's code separate. 

Maybe with enough focused effort that will change over the next year and it
will get merged back into the development branch before octave 10. maybe not.
but there are a number of people who work with a 'bleeding edge' version of
octave compiled from the development source.   perhaps we could dedicate some
resources to regularly building a version of the bytecode-interpreter branch
for some platforms. I think anyone with resources can set up a bulidbot client
to do so. 


    _______________________________________________________

Reply to this item at:

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

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