Yes, it was using gsl-2.7.1, and no, what I was claiming was 1st setter sets some value at index e.g. 2; 2nd setter sets some value at index "v" which (index) would be 0x100000002.

+ I'm bad communicator + my bad English :). Sorry. OK, forget the above, I found something which maybe will entertain you. I went as far as to boot 22.04 LTS Ubuntu from USB stick, to confirm that 2.7 "official" Debian GSL demonstrates same behaviour, using very similar, to what you posted, C program. And I mailed a bug report to bug-gsl@gnu.org, which their robot bounced back at me couple hours later because of text/html content-type of my letter.

Now I think maybe it was good, because of what I found in meantime. There was significant overhaul of sparse matrix code from version 2.5 to 2.6 of GSL. Actually, NEWS for 2.6 don't mention "no more 64-bit indexing". But maybe it was quite intentional, and NOT documented because "ha, no one is using long long indexes anyway".

We can see size_t type of row/column index (i.e. i and p) in 2.5.

Then they (i and p) were suddenly changed to int in 2.6. Someone went as far as to change %zu to %d format specifier in example file, they were meticulous in what they were doing, how can it be a "bug"? Perhaps it was to optimise speed/space, etc.

This int type is documented in top-level nicely-formatted manual for 2.7. I should have noticed that. Can't call it a "bug" now. If not, it's very sad and messy and not to the level of "GSL is a mature library with a stable API".

So... what's the crust, I'm sorry to have wasted your time, should have done more research? :( Report to Math::GSL queue about "what Alien::GSL compiles is ignored in Windows" seems unimportant if above is correct.

In reply to Re^7: Math::GSL::SparseMatrix is broken if installed on latest 5.32.1.1 "Strawberry Perl PDL edition", whom to report this issue to? by Anonymous Monk
in thread Math::GSL::SparseMatrix is broken if installed on latest 5.32.1.1 "Strawberry Perl PDL edition", whom to report this issue to? by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.