Re: 4 errors generated when compiling Quad_MX,hh

2024-12-02 Thread Paul Rockwell
I agree with you Henrik that’ it’s Jürgen’s call here on what would be the best way forward. I suspect you and Jürgen didn’t encounter the issue because you’re using a GCC compiler suite that defaults to a newer standard. It’s just us Mac folks using clang are more likely to see it because of

Re: 4 errors generated when compiling Quad_MX,hh

2024-12-02 Thread Henrik Moller
Quad_MX is my code, but the GNU APL code base is Jürgen Sauermann's, so I'm going to leave it to him what to do about this. I've experimented with using "> >" and it works with whatever gcc options Jürgen has baked into the package.   It's his decision. Henrik Moller On 12/2/24 14:50, Paul Ro

Re: 4 errors generated when compiling Quad_MX,hh

2024-12-02 Thread Paul Rockwell
More research indicates that this may indeed be an issue related to old standards. See https://en.cppreference.com/w/cpp/language/angle_bracket_hack It indicates that there were issues with some compilers when using standards prio

Re: 4 errors generated when compiling Quad_MX,hh

2024-12-02 Thread Paul Rockwell
Peter/Jürgen Success with adding the -std=gnu++11 flag to the compiler on High Sierra. TL;DR I was able to test this on a VM with macOS High Sierra, and I’m seeing the same thing as Peter did. I ran the script that checks for the C++ standard being used, and it returns 199711L - indicating th

Re: 4 errors generated when compiling Quad_MX,hh

2024-12-02 Thread Peter Teeson
I am on High Sierra 13.6 which is a high as I can go on my Mac hardware (unless I patch.) QuadMX is a recent addition so not really surprised. > On Dec 1, 2024, at 11:56 PM, Paul Rockwell wrote: > > Peter (and Jűrgen) > > I am seeing this same error when compiling on macOS 15 Sequoia on Apple