The latest nightly (upp-win-16223.7z) shows version 11.0.0. for clang:

I do see a weird problem with Md5Stream. I'll check it tomorrow.

FindAllPaths("/home/ssg/data/download", "*.pdf")

v = Z:\home\ssg\dvlp\cpp\code\upp\out\MyApps\MINGWcpp17.Debug.Debug_Full.Gui.Shared.Win32\home\ssg\data\download\mysqluc2007-wikipedia-workbook.pdf
v = Z:\home\ssg\dvlp\cpp\code\upp\out\MyApps\MINGWcpp17.Debug.Debug_Full.Gui.Shared.Win32\home\ssg\data\download\recsplit.pdf
v = Z:\home\ssg\dvlp\cpp\code\upp\out\MyApps\MINGWcpp17.Debug.Debug_Full.Gui.Shared.Win32\home\ssg\data\download\StatisticsWithJuliaDRAFT.pdf
v = Z:\home\ssg\dvlp\cpp\code\upp\out\MyApps\MINGWcpp17.Debug.Debug_Full.Gui.Shared.Win32\home\ssg\data\download\UHHA Info Update 5-8-20.pdf
v = Z:\home\ssg\dvlp\cpp\code\upp\out\MyApps\MINGWcpp17.Debug.Debug_Full.Gui.Shared.Win32\home\ssg\data\download\web-prolog.pdf
v = Z:\home\ssg\dvlp\cpp\code\upp\out\MyApps\MINGWcpp17.Debug.Debug_Full.Gui.Shared.Win32\home\ssg\data\download\whole-book.pdf

It turned out that Windows has a command line package manager called "winget" now. (This, probably, was already discussed on this forum)
IMHO, it would be cool to have an Upp package for it.
Installing Upp via "winget install Upp" seems to be the easiest way to get it.
And "winget search upp" seems to be the easiest way to find it.

mirek wrote on Sun, 03 April 2022 19:36

Klugier wrote on Sun, 03 April 2022 15:43

Hello Mirek,

I also proposed bumping C++ standard from c++14 to c++17. However, this could be done in the next release. There are a lot of risks here in context of compilation on various platforms.

Even if we do not have any features that particularly targets c++17 we should compile with that standard and our users should have access to it by default. Also, maybe this is a bug, but for MSVC we do not force any standard. It is always latest. I think it should change and we should target exactly the same standard as for GCC and CLANG.

Klugier

Yeeah, I was thinking about it a lot, problem is we have so far universal package for Posixes and we are not 100% sure c++17 compliant compiler is there. I think we would need to add detection code before adding -std=c++17 to options, which is sort of complicated and quirky.

Hello Mirek,

What about chaning approch? If it doesn't compile you could always back to older stable release of Upp. The old systems shouldn't hold us back and keep with old standard. We could make 2022.1 last official release with c++14 and the next one will be c++17.

The C++14 was introduced in 2017 in our code base. 3 years after official standard announcement. Right now we are 5 years after c++17. There is no consistency here.

Klugier

Novo wrote on Wed, 06 April 2022 09:07

It turned out that Windows has a command line package manager called "winget" now. (This, probably, was already discussed on this forum)
IMHO, it would be cool to have an Upp package for it.
Installing Upp via "winget install Upp" seems to be the easiest way to get it.
And "winget search upp" seems to be the easiest way to find it.

Go for it

(1) C++ that is required by U++
(2) default C++ setting of build methods

mirek wrote on Wed, 06 April 2022 06:05

(1) C++ that is required by U++
(2) default C++ setting of build methods

IMHO, it makes sense to ship Upp with different C++-versioned builders.
CLANG14, CLANG17, e.t.c instead of just a CLANG ...
And Upp should be tested against all versions of C++ because old code often doesn't compile with new versions of C++.
I personally use C++17 because my own code doesn't compile with older versions of C++

Hi,

Bundled clang in windows now seems up to version 14.0.0.

However, when linking my project with CLANG I get the following error:

Linking...
ld.lld: error: duplicate symbol: std::__throw_bad_alloc()
>>> defined at C:/upp-git/out/program/Core/CLANGx64.Blitz.Gui.Protect/heap.o
>>> defined at libc++.a(new.cpp.obj)
clang-14: error: linker command failed with exit code 1 (use -v to see invocation)

There were errors. (1:31.25)

Please note that this is not specific to CLANG-14 but also happened with previous CLANG version bundled.

Any idea where this comes from and suggestions how to proceed?

Best regards,

Tom

I still think that we should bump c++ version everywhere.

And Upp should be tested against all versions of C++ because old code often doesn't compile with new versions of C++.

/home/ssg/dvlp/cpp/code/upp/git/uppsrc/CtrlCore/CtrlPos.cpp:152:11: error: use of overloaded operator '!=' is ambiguous (with operand types 'Upp::Rect' (aka 'Rec
    t_<int>') and 'Upp::Rect16' (aka 'Rect_<short>'))
                if(view != f.view) {
                   ~~~~ ^  ~~~~~~
/home/ssg/dvlp/cpp/code/upp/git/uppsrc/Core/Gtypes.h:337:9: note: candidate function
        bool   operator!=(const Rect_& b) const                 { return !operator==(b); }
               ^
/home/ssg/dvlp/cpp/code/upp/git/uppsrc/Core/Gtypes.h:336:9: note: candidate function
        bool   operator==(const Rect_& b) const;
               ^
/home/ssg/dvlp/cpp/code/upp/git/uppsrc/Core/Gtypes.h:336:9: note: candidate function (with reversed parameter order)

Novo wrote on Wed, 06 April 2022 13:34

And Upp should be tested against all versions of C++ because old code often doesn't compile with new versions of C++.

TheIDE cannot be compiled with C++20.
Clang + -std=c++20

/home/ssg/dvlp/cpp/code/upp/git/uppsrc/CtrlCore/CtrlPos.cpp:152:11: error: use of overloaded operator '!=' is ambiguous (with operand types 'Upp::Rect' (aka 'Rec
    t_<int>') and 'Upp::Rect16' (aka 'Rect_<short>'))
                if(view != f.view) {
                   ~~~~ ^  ~~~~~~
/home/ssg/dvlp/cpp/code/upp/git/uppsrc/Core/Gtypes.h:337:9: note: candidate function
        bool   operator!=(const Rect_& b) const                 { return !operator==(b); }
               ^
/home/ssg/dvlp/cpp/code/upp/git/uppsrc/Core/Gtypes.h:336:9: note: candidate function
        bool   operator==(const Rect_& b) const;
               ^
/home/ssg/dvlp/cpp/code/upp/git/uppsrc/Core/Gtypes.h:336:9: note: candidate function (with reversed parameter order)

IMHO, this should be fixed.

Klugier wrote on Thu, 07 April 2022 06:55

I still think that we should bump c++ version everywhere.

I have a different proposal. Upp doesn't really use any of C++14 language features.