Applying that patch does fix the issue in package

If you look at the tree_index_expression::lvalue method in pt-idx.cc you'll see that it calls subsref on each element of an index expression.  That was done to handle the possibility of the expression including an END index.  But it's not the right thing to do and my latest patch for bug #58953 should avoid this problem.

Can you create an example class that shows the problem without requiring Windows or the COM object?  Then I could more easily verify that the problem is fixed for this case as well, not just the one we were addressing in bug #58953.

set(eLibro.Worksheets.Item(1), 'Name', 'page1');

also works

Hello everyone,

Frist of all I have to say that this is my first bug report ever so please be gentle with me.
The problem that I have detect is the next one, I have a code that has been done in Matlab (and it run well), but with Octave return an error

The code is the following:
eAplicacion = actxserver ('Excel.Application');
eLibro = eAplicacion.Workbooks.Open(abspath([cabeceraOut nombreTipo '.xlsx']));
eLibro.Worksheets.Item(1).Name = 'page1';

And the error this one:
error: com_get: property/method invocation on the COM object failed with error `0x8002000e'

So, I ran the debugger and I saw that If I put this:
eLibro.Worksheets(1).Name = 'page1'; instead of eLibro.Worksheets.Item(1).Name = 'page1';

There is no error, and everything goes fine. But the thing is according to Microsoft’s documentation (https://docs.microsoft.com/en-us/office/vba/api/excel.worksheets.item) both are equivalent.
So both would have to be correct right?

And, in advance, thanks you very much for your help.