[Octave-bug-tracker] [bug #45996] io package: add named ranges/definedNames

[Philip Nienhuis]

Follow-up Comment #6, bug #45996 (project octave):

Hmmm it did work for me. Anything not representing a regular range ("A1",
"B25:VDF10234") could be a named range; if not matching one of the present
named ranges it's an error.
I think it is not the job of xls2oct / oct2xls / ods2oct / oct2ods to validate
or even gate range names. That's the user's responsibility, he/she can explore
the present named ranges with xlsfinfo / odsfinfo.

AFAICS in Excel 2013 a named range applies to just one worksheet. A "local"
named range can be invoked from that worksheet only, "global" named ranges
from other worksheets as well (w/o specifying the sheet name).
For xlsread/write that implies that specifying a named range implicitly also
specifies a specific worksheet.

For LibreOffice it works largely the same (for Excel files that is, .ods
doesn't work, see upstream bug report:
https://bugs.documentfoundation.org/show_bug.cgi?id=94423 )

However, in gnumeric "global" ranges seem to apply to the currently selected
worksheet.

IOW, the usual mess with competing programs.
I suppose that by io-2.2.12 it will all have been sorted out as far as
possible.

As to a patch, I indicated that the named range stanza could be singled out
into a separate private function. If you could do that it would be awesome.
But I might find time this week, it doesn't seem daunting.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?45996>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/