Re: [Plplot-devel] Status of our octave binding and examples for version 4.4.0 of octave

[Arjen Markus]

Hi Alan,

> -Original Message-
> From: Alan W. Irwin [mailto:alan.w.irwin1...@gmail.com]
> Sent: Monday, August 13, 2018 9:56 PM
> To: Arjen Markus
> Cc: Orion Poplawski; PLplot development list
> Subject: RE: Status of our octave binding and examples for version 4.4.0 of 
> octave
>
>
> Let's ignore octave for a bit and look at the more general picture.
> If you like the goal (in its own right) of learning to build packages for the 
> MinGW-
> w64/MSYS2 platform, then I suggest you follow the package build documentation
> examples under the heading "Re-building a package" at
> .
> Can you use those steps to build both their examples (flex and python3)?  If 
> not,
> then you should take the problem to the MSYS2 mailing list to get help with 
> that
> documentation.  But if that general procedure works for you, then the next 
> obvious
> step is to help out with the PLplot packaging at
> 
> by first building that package as is, fixing it according to your own 
> experience (e.g.,
> by moving to Python 3, and by enabling qt), and drawing Alex's attention to 
> your
> improvements (likely via a pull
> request) so they will be made part of the official Plplot package for this 
> platform.
>
I can certainly try ...

> Moving back to the octave case, I am pretty sure unless that semi-official 
> package
> is completely broken, that the same procedures used to build flex, python3, 
> and
> PLplot should also work fine for octave without all the issues you encountered
> above.  Assuming you can build that octave package, then the next steps would 
> be
> to evaluate the result for our needs, and assuming it does work for those 
> needs (or
> can easily be fixed), advocate making it an official package that the PLplot 
> package
> depends on.
>
> > I guess an alternative could be to simply build Octave and install it 
> > without
> pacman, but I have not tried that yet.
>
> I would advise against that since unofficial octave builds are not going to 
> help our
> octave users that much on this particular platform and may turn out to be a 
> black
> hole sucking up a lot of your time.
> Instead, I think it would be better in the long-run to help get an official 
> octave
> package running for this platform as I have outlined above.
>

Last night I tried to build Octave out of the box, as the computer would do 
most of the work - run configure, make, make install ... However, the make step 
fails:

  CXX  libinterp/corefcn/libinterp_corefcn_libcorefcn_la-pr-output.lo
libinterp/corefcn/pr-output.cc: In function 'float_display_format 
make_format(const T&) [with T = intNDArray >]':
libinterp/corefcn/pr-output.cc:1736:59: error: call of overloaded 'abs(signed 
char)' is ambiguous
   (std::floor (log10 (double (abs (nda(i).value ( + 1));  \
   ^
libinterp/corefcn/pr-output.cc:1748:1: note: in expansion of macro 
'MAKE_INT_MATRIX_FORMAT'
 MAKE_INT_MATRIX_FORMAT (octave_int8)
 ^~
In file included from C:/msys64/mingw64/include/c++/6.2.0/cmath:45:0,
 from libinterp/corefcn/pr-output.cc:27:
C:/msys64/mingw64/x86_64-w64-mingw32/include/math.h:254:15: note: candidate: 
int abs(int)
   int __cdecl abs(int _X);
   ^~~
In file included from 
C:/msys64/mingw64/include/c++/6.2.0/ext/string_conversions.h:41:0,
 from 
C:/msys64/mingw64/include/c++/6.2.0/bits/basic_string.h:5402,
 from C:/msys64/mingw64/include/c++/6.2.0/string:52,
 from 
C:/msys64/mingw64/include/c++/6.2.0/bits/locale_classes.h:40,
 from C:/msys64/mingw64/include/c++/6.2.0/bits/ios_base.h:41,
 from C:/msys64/mingw64/include/c++/6.2.0/iomanip:40,
 from libinterp/corefcn/pr-output.cc:29:
C:/msys64/mingw64/include/c++/6.2.0/cstdlib:185:3: note: candidate: __int128 
std::abs(__int128)
   abs(__GLIBCXX_TYPE_INT_N_0 __x) { return __x >= 0 ? __x : -__x; }
   ^~~
C:/msys64/mingw64/include/c++/6.2.0/cstdlib:180:3: note: candidate: long long 
int std::abs(long long int)
... (a lot more complaints)

So that is the end of that road as well as far as I am concerned.

It would seem that the only way we can proceed is indeed by obtaining an 
official Octave package, as you indicate.

Regards,

Arjen

DISCLAIMER: This message is intended exclusively for the addressee(s) and may 
contain confidential and privileged information. If you are not the intended 
recipient please notify the sender immediately and destroy this message. 
Unauthorized use, disclosure or copying of this message is strictly prohibited. 
The foundation 'Stichting Deltares', which has its seat at Delft, The 
Netherlands, Commercial Registration Number 41146461, is not liable in any way 
whatsoever for consequences and/or damages resulting from the improper, 
incomplete 

Re: [Plplot-devel] Status of our octave binding and examples for version 4.4.0 of octave

[Alan W. Irwin]

On 2018-08-13 08:41- Arjen Markus wrote:


Hi Alan,


However, I hope those comments (such as the possibility mentioned above of
building an octave MinGW-w64/MSYS2 package for yourself using the pacman
packaging information at
)
are still of some use to you.


I have tried to build Octave under MinGW-w64/MSYS2 using that webpage. However:
- I had to remove the references to the patches, as these do not seem to be 
available. No idea what the effect is
- The build failed on a mismatch in the checksums:

$ makepkg -sCLf
==> Making package: mingw-w64-octave-hg r19590.6d75f1683ce8-1 (Sun, Aug 12, 
2018 15:56:07)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
 -> Updating gnulib git repo...
Fetching origin
 -> Found tip.tar.bz2
==> ERROR: Integrity checks (sha256) differ in size from the source array.

This is the point where I stopped. I have no clue as to whether this is a 
serious issue or not.


Let's ignore octave for a bit and look at the more general picture.
If you like the goal (in its own right) of learning to build packages
for the MinGW-w64/MSYS2 platform, then I suggest you follow the
package build documentation examples under the heading "Re-building a
package" at .
Can you use those steps to build both their examples (flex and
python3)?  If not, then you should take the problem to the MSYS2
mailing list to get help with that documentation.  But if that general
procedure works for you, then the next obvious step is to help out
with the PLplot packaging at

by first building that package as is, fixing it according to your own
experience (e.g., by moving to Python 3, and by enabling qt), and
drawing Alex's attention to your improvements (likely via a pull
request) so they will be made part of the official Plplot package for
this platform.

Moving back to the octave case, I am pretty sure unless that
semi-official package is completely broken, that the same procedures
used to build flex, python3, and PLplot should also work fine for
octave without all the issues you encountered above.  Assuming you can
build that octave package, then the next steps would be to evaluate
the result for our needs, and assuming it does work for those needs
(or can easily be fixed), advocate making it an official package
that the PLplot package depends on.


I guess an alternative could be to simply build Octave and install it without 
pacman, but I have not tried that yet.


I would advise against that since unofficial octave builds are not
going to help our octave users that much on this particular platform
and may turn out to be a black hole sucking up a lot of your time.
Instead, I think it would be better in the long-run to help get an
official octave package running for this platform as I have outlined
above.

Alan
__
Alan W. Irwin

Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__

Linux-powered Science
__

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel

Re: [Plplot-devel] Status of our octave binding and examples for version 4.4.0 of octave

[Arjen Markus]

Hi Alan,

> However, I hope those comments (such as the possibility mentioned above of
> building an octave MinGW-w64/MSYS2 package for yourself using the pacman
> packaging information at
> )
> are still of some use to you.
>
I have tried to build Octave under MinGW-w64/MSYS2 using that webpage. However:
- I had to remove the references to the patches, as these do not seem to be 
available. No idea what the effect is
- The build failed on a mismatch in the checksums:

$ makepkg -sCLf
==> Making package: mingw-w64-octave-hg r19590.6d75f1683ce8-1 (Sun, Aug 12, 
2018 15:56:07)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Updating gnulib git repo...
Fetching origin
  -> Found tip.tar.bz2
==> ERROR: Integrity checks (sha256) differ in size from the source array.

This is the point where I stopped. I have no clue as to whether this is a 
serious issue or not.

I guess an alternative could be to simply build Octave and install it without 
pacman, but I have not tried that yet.

Regards,

Arjen
DISCLAIMER: This message is intended exclusively for the addressee(s) and may 
contain confidential and privileged information. If you are not the intended 
recipient please notify the sender immediately and destroy this message. 
Unauthorized use, disclosure or copying of this message is strictly prohibited. 
The foundation 'Stichting Deltares', which has its seat at Delft, The 
Netherlands, Commercial Registration Number 41146461, is not liable in any way 
whatsoever for consequences and/or damages resulting from the improper, 
incomplete and untimely dispatch, receipt and/or content of this e-mail.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel

Re: [Plplot-devel] Status of our octave binding and examples for version 4.4.0 of octave

[Arjen Markus]

Hi Alan,

> -Original Message-
> From: Alan W. Irwin [mailto:alan.w.irwin1...@gmail.com]
> Sent: Thursday, August 09, 2018 1:07 AM
>
> Thanks for that confirmation on Cygwin.  That is the first time in a long 
> time (if
> ever?) that octave has worked on that platform for us which I regard as a big 
> step
> forward.
>

:)

> And as far as MinGW-w64/MSYS2 is concerned, my guess is the information at
> 
> is for a pacman package for octave that has not matured yet so the package 
> build
> results are not included in the official pacman packages for MinGW-w64/MSYS2.
> But the small part of that package that we use for our octave binding build 
> and tests
> might work well.  So if you want to follow up further, I suggest you build 
> the pacman
> package for octave following the cookbook located at
> .
>

I guess it is worth a try ... Will keep you informed on progress.

> As you know, my long-term dream has been to use Wine to help you out more with
> both Cygwin and MinGW-w64/MSYS2 testing so recently I looked into that again.
> But currently it does not look good.  For example, both Cygwin and MinGW-
> w64/MSYS2 upgraded from Windows XP to Windows Vista functionality a couple of
> years back, but according to discussion at  packages/issues/682>
> Wine has a lot of missing Vista functionality that has to be implemented 
> before
> either of those two distributions will work on Wine again.  So until that 
> happens, I
> am limited to just commenting from the sidelines concerning those 
> distributions.
> However, I hope those comments (such as the possibility mentioned above of
> building an octave MinGW-w64/MSYS2 package for yourself using the pacman
> packaging information at
> )
> are still of some use to you.
>

Pity about Wine, but it seems quite difficult to keep up with a moving target 
like Windows.

Regards,

Arjen
DISCLAIMER: This message is intended exclusively for the addressee(s) and may 
contain confidential and privileged information. If you are not the intended 
recipient please notify the sender immediately and destroy this message. 
Unauthorized use, disclosure or copying of this message is strictly prohibited. 
The foundation 'Stichting Deltares', which has its seat at Delft, The 
Netherlands, Commercial Registration Number 41146461, is not liable in any way 
whatsoever for consequences and/or damages resulting from the improper, 
incomplete and untimely dispatch, receipt and/or content of this e-mail.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel

Re: [Plplot-devel] Status of our octave binding and examples for version 4.4.0 of octave

[Alan W. Irwin]

On 2018-08-07 06:37- Arjen Markus wrote:


Hi Alan,

I can confirm clean test results for Octave 4.2.2 on Cygwin - I cannot do the 
same for MinGW-w64/MSYS2 as that does not provide an octave package as far as I 
can tell. There is an Octave pacakge on github 
(https://github.com/Alexpux/MINGW-packages/tree/master/mingw-w64-octave-hg) but 
its status is completely unclear to me. As is how it should be installed 
(pacman does not recognise it)


Hi Arjen:

Thanks for that confirmation on Cygwin.  That is the first time in a
long time (if ever?) that octave has worked on that platform for us
which I regard as a big step forward.

And as far as MinGW-w64/MSYS2 is concerned, my guess is the
information at

is for a pacman package for octave that has not matured yet so the
package build results are not included in the official pacman packages
for MinGW-w64/MSYS2.  But the small part of that package that we use
for our octave binding build and tests might work well.  So if you
want to follow up further, I suggest you build the pacman package for
octave following the cookbook located at
.

As you know, my long-term dream has been to use Wine to help you out
more with both Cygwin and MinGW-w64/MSYS2 testing so recently I looked
into that again.  But currently it does not look good.  For example,
both Cygwin and MinGW-w64/MSYS2 upgraded from Windows XP to Windows
Vista functionality a couple of years back, but according to
discussion at 
Wine has a lot of missing Vista functionality that has to be
implemented before either of those two distributions will work on Wine
again.  So until that happens, I am limited to just commenting from
the sidelines concerning those distributions.  However, I hope those
comments (such as the possibility mentioned above of building an
octave MinGW-w64/MSYS2 package for yourself using the pacman packaging
information at
)
are still of some use to you.

Alan
__
Alan W. Irwin

Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__

Linux-powered Science
__

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel

Re: [Plplot-devel] Status of our octave binding and examples for version 4.4.0 of octave

[Arjen Markus]

Hi Alan,

I can confirm clean test results for Octave 4.2.2 on Cygwin - I cannot do the 
same for MinGW-w64/MSYS2 as that does not provide an octave package as far as I 
can tell. There is an Octave pacakge on github 
(https://github.com/Alexpux/MINGW-packages/tree/master/mingw-w64-octave-hg) but 
its status is completely unclear to me. As is how it should be installed 
(pacman does not recognise it)

Regards,

Arjen

> -Original Message-
> From: Arjen Markus [mailto:arjen.mar...@deltares.nl]
> Sent: Monday, August 06, 2018 2:33 PM
> To: Alan W. Irwin; Orion Poplawski
> Cc: PLplot development list
> Subject: Re: [Plplot-devel] Status of our octave binding and examples for 
> version
> 4.4.0 of octave
>
> Hi Alan,
>
> I am back from my holiday, so I should have the opportunity to test the new 
> binding.
>
> Regards,
>
> Arjen
>
> > -Original Message-
> > From: Alan W. Irwin [mailto:alan.w.irwin1...@gmail.com]
> > Sent: Thursday, August 02, 2018 12:40 AM
> > To: Orion Poplawski; Arjen Markus
> > Cc: PLplot development list
> > Subject: Re: Status of our octave binding and examples for version
> > 4.4.0 of octave
> >
> > On 2018-07-31 21:10-0700 Alan W. Irwin wrote:
> >
> > > To Orion and Arjen:
> > >
> > > As of
> > > <https://sourceforge.net/p/plplot/plplot/ci/d7310aa9864ce1676177f393
> > > 23 c9daf593ae0765/> our octave binding and all
> > > examples/octave/x??c.m examples give a perfect PostScript difference
> > > report for Octave 4.4.0 for Debian Buster == Debian Testing.  Please
> > > do equivalent checks (i.e., by simply building the
> > > test_noninteractive target in the build
> > > tree) for Cygwin, MinGW-w64/MSYS2, and Fedora to check all is well
> > > on platforms other than Debian Buster.  I emphasize build-tree
> > > checks because install-tree checks currently won't work []
> >
> > That request for testing help still applies, but I can now report (see
> > the log for commit 391ec0ad0 for the details) that I have been able to
> > replace the cellstr-based workaround with an actual fix for the issue
> > which should work for late octave-3 as well as all versions of octave-4.
> >
> > Alan
> > __
> > Alan W. Irwin
> >
> > Programming affiliations with the FreeEOS equation-of-state
> > implementation for stellar interiors (freeeos.sf.net); the Time
> > Ephemerides project (timeephem.sf.net); PLplot scientific plotting
> > software package (plplot.sf.net); the libLASi project
> > (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the 
> > Linux
> Brochure Project (lbproject.sf.net).
> > __
> >
> > Linux-powered Science
> > __
> DISCLAIMER: This message is intended exclusively for the addressee(s) and may
> contain confidential and privileged information. If you are not the intended 
> recipient
> please notify the sender immediately and destroy this message. Unauthorized 
> use,
> disclosure or copying of this message is strictly prohibited. The foundation 
> 'Stichting
> Deltares', which has its seat at Delft, The Netherlands, Commercial 
> Registration
> Number 41146461, is not liable in any way whatsoever for consequences and/or
> damages resulting from the improper, incomplete and untimely dispatch, receipt
> and/or content of this e-mail.
>
> --
> Check out the vibrant tech community on one of the world's most engaging tech
> sites, Slashdot.org! http://sdm.link/slashdot
> ___
> Plplot-devel mailing list
> Plplot-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/plplot-devel
DISCLAIMER: This message is intended exclusively for the addressee(s) and may 
contain confidential and privileged information. If you are not the intended 
recipient please notify the sender immediately and destroy this message. 
Unauthorized use, disclosure or copying of this message is strictly prohibited. 
The foundation 'Stichting Deltares', which has its seat at Delft, The 
Netherlands, Commercial Registration Number 41146461, is not liable in any way 
whatsoever for consequences and/or damages resulting from the improper, 
incomplete and untimely dispatch, receipt and/or content of this e-mail.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel

Re: [Plplot-devel] Status of our octave binding and examples for version 4.4.0 of octave

[Arjen Markus]

Hi Alan,

I am back from my holiday, so I should have the opportunity to test the new 
binding.

Regards,

Arjen

> -Original Message-
> From: Alan W. Irwin [mailto:alan.w.irwin1...@gmail.com]
> Sent: Thursday, August 02, 2018 12:40 AM
> To: Orion Poplawski; Arjen Markus
> Cc: PLplot development list
> Subject: Re: Status of our octave binding and examples for version 4.4.0 of 
> octave
>
> On 2018-07-31 21:10-0700 Alan W. Irwin wrote:
>
> > To Orion and Arjen:
> >
> > As of
> >  > c9daf593ae0765/> our octave binding and all examples/octave/x??c.m
> > examples give a perfect PostScript difference report for Octave 4.4.0
> > for Debian Buster == Debian Testing.  Please do equivalent checks
> > (i.e., by simply building the test_noninteractive target in the build
> > tree) for Cygwin, MinGW-w64/MSYS2, and Fedora to check all is well on
> > platforms other than Debian Buster.  I emphasize build-tree checks
> > because install-tree checks currently won't work []
>
> That request for testing help still applies, but I can now report (see the 
> log for
> commit 391ec0ad0 for the details) that I have been able to replace the 
> cellstr-based
> workaround with an actual fix for the issue which should work for late 
> octave-3 as
> well as all versions of octave-4.
>
> Alan
> __
> Alan W. Irwin
>
> Programming affiliations with the FreeEOS equation-of-state implementation for
> stellar interiors (freeeos.sf.net); the Time Ephemerides project 
> (timeephem.sf.net);
> PLplot scientific plotting software package (plplot.sf.net); the libLASi 
> project
> (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the 
> Linux
> Brochure Project (lbproject.sf.net).
> __
>
> Linux-powered Science
> __
DISCLAIMER: This message is intended exclusively for the addressee(s) and may 
contain confidential and privileged information. If you are not the intended 
recipient please notify the sender immediately and destroy this message. 
Unauthorized use, disclosure or copying of this message is strictly prohibited. 
The foundation 'Stichting Deltares', which has its seat at Delft, The 
Netherlands, Commercial Registration Number 41146461, is not liable in any way 
whatsoever for consequences and/or damages resulting from the improper, 
incomplete and untimely dispatch, receipt and/or content of this e-mail.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel

Re: [Plplot-devel] Status of our octave binding and examples for version 4.4.0 of octave

[Alan W. Irwin]

On 2018-07-31 21:10-0700 Alan W. Irwin wrote:


To Orion and Arjen:

As of

our octave binding and all examples/octave/x??c.m examples give a
perfect PostScript difference report for Octave 4.4.0 for Debian
Buster == Debian Testing.  Please do equivalent checks (i.e., by
simply building the test_noninteractive target in the build tree) for
Cygwin, MinGW-w64/MSYS2, and Fedora to check all is well on platforms
other than Debian Buster.  I emphasize build-tree checks because
install-tree checks currently won't work []


That request for testing help still applies, but I can now report (see
the log for commit 391ec0ad0 for the details) that I have been able to
replace the cellstr-based workaround with an actual fix for the issue
which should work for late octave-3 as well as all versions of
octave-4.

Alan
__
Alan W. Irwin

Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__

Linux-powered Science
__

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel

[Plplot-devel] Status of our octave binding and examples for version 4.4.0 of octave

[Alan W. Irwin]

To Orion and Arjen:

As of

our octave binding and all examples/octave/x??c.m examples give a
perfect PostScript difference report for Octave 4.4.0 for Debian
Buster == Debian Testing.  Please do equivalent checks (i.e., by
simply building the test_noninteractive target in the build tree) for
Cygwin, MinGW-w64/MSYS2, and Fedora to check all is well on platforms
other than Debian Buster.  I emphasize build-tree checks because
install-tree checks currently won't work until I finish another
project that was half-completed when I discovered the octave-4 cell array
workaround described below.

The way I got the previously dropped octave examples 26 and 33 to work
was to use cell arrays at those points in the examples where Octave
non-cell arrays were not working due to an upstream bug in Octave 4.4
for the transformation method used to determine C strings from an
Octave non-cell array of strings.  For a long time I thought the issue
was UTF-8, but I discovered when testing the recent commit that pure
ascii strings could also cause issues.

Since that commit I have discovered (with my hex_print private test
project) the issue is a simple one which is the transformation method
that used to work fine for octave 3.8 no longer works for octave-4.4
*if* there are more than 15 bytes in the character strings in the
non-cell arrays.  (Of course, UTF-8 strings tend to have more bytes
which is why they tend to expose this upstream bug more than ascii
strings, but with hex_print I found in every case whether using the
ascii subset of UTF-8 or more general UTF-8 strings that short strings
worked, but when the number of bytes in the Octave string (excluding the NULL
byte) exceeded 15, the result was an invalid UTF-8 C string.

I have just submitted this issue to the upstream octave developers
(see ).  That bug
report is based on the hex_print experience summarized above, and
since that experience proves there is now an explicit length limit of
15 imposed by the octave code, the issue should be easy to find and
fix (I hope).

But meanwhile, the cellstr workaround in the above commit for long
strings avoids this issue so with luck the PLplot testers lurking here
will now get perfect octave-4 results when building the
test_noninteractive target on all platforms of interest to them.

Also note in the subsequent commit 95f823ec0, I have changed our
octave detection method so that octave-4 is no longer a special case
with warnings attached.  Which finally (from the better late than
never department) answers Orion's question about those warnings from
long ago.  :-)

Alan
__
Alan W. Irwin

Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__

Linux-powered Science
__

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel