Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » Community » U++ community news and announcements » Gearing up for 2022.1 release...
Re: Gearing up for 2022.1 release... [message #58277 is a reply to message #58276] Fri, 08 April 2022 15:34 Go to previous messageGo to next message
mirek is currently offline  mirek
Messages: 13975
Registered: November 2005
Ultimate Member
I am really frustrated with C++20. It breaks backward compatibility huge way, I will probably have to spend weeks to fix my codebase Sad What were they thinking?
Re: Gearing up for 2022.1 release... [message #58279 is a reply to message #58277] Fri, 08 April 2022 16:15 Go to previous messageGo to next message
Tom1
Messages: 1212
Registered: March 2007
Senior Contributor
mirek wrote on Fri, 08 April 2022 16:34
I am really frustrated with C++20. It breaks backward compatibility huge way, I will probably have to spend weeks to fix my codebase Sad What were they thinking?

How about not going to C++20 just yet? Instead, release the stable U++ 2022.1 and only thereafter re-start to look at the C++20 standard issues.

Best regards,

Tom
Re: Gearing up for 2022.1 release... [message #58280 is a reply to message #58279] Fri, 08 April 2022 16:50 Go to previous messageGo to next message
mirek is currently offline  mirek
Messages: 13975
Registered: November 2005
Ultimate Member
Tom1 wrote on Fri, 08 April 2022 16:15
mirek wrote on Fri, 08 April 2022 16:34
I am really frustrated with C++20. It breaks backward compatibility huge way, I will probably have to spend weeks to fix my codebase Sad What were they thinking?

How about not going to C++20 just yet? Instead, release the stable U++ 2022.1 and only thereafter re-start to look at the C++20 standard issues.

Best regards,

Tom


OK, I have probably exaggerted a bit.. Smile Right now I have just one really annoying warning to fix...

That said, breaking overloading rules is not a good idea. Had to add quite some lines to support C++20...

Mirek
Re: Gearing up for 2022.1 release... [message #58281 is a reply to message #58280] Fri, 08 April 2022 17:04 Go to previous messageGo to next message
mirek is currently offline  mirek
Messages: 13975
Registered: November 2005
Ultimate Member
ide now compiles with C++ 20 with some warnings. If anybody had time to investigate these, it would be much appreciated...

C:\u\upp.src\uppsrc\RichText\ParaData.cpp (344): warning: ISO C++20 considers use of overloaded operator '!=' (with operand types 'const WithDeepCopy<Vector<Upp::RichPara::Tab>>' and 'const WithDeepCopy<Vector<Upp::RichPara::Tab>>') to be ambiguou
s despite there being a unique best viable function [-Wambiguous-reversed-operator]
Re: Gearing up for 2022.1 release... [message #58283 is a reply to message #58275] Fri, 08 April 2022 21:37 Go to previous messageGo to next message
Novo is currently offline  Novo
Messages: 1358
Registered: December 2006
Ultimate Contributor
mirek wrote on Fri, 08 April 2022 05:19

Actually, we use C++14 lambda features that cannot be worked around. But I would like to stay there (at C++ 14).

Mirek

Sorry, I missed that ...


Regards,
Novo
Re: Gearing up for 2022.1 release... [message #58284 is a reply to message #58145] Fri, 08 April 2022 21:39 Go to previous messageGo to next message
Novo is currently offline  Novo
Messages: 1358
Registered: December 2006
Ultimate Contributor
MacOS 10.15
./umk uppsrc ide CLANG -bus
In file included from /Users/ssg/worker0/m-upp/build/uppsrc/CtrlCore/MKeys.h:3:
/Users/ssg/worker0/m-upp/build/uppsrc/CtrlCore/CocoKeys.h:12:1: error: default initialization of an object of const type 'const Upp::dword' (aka 'const unsigned int')
K_CTRL_KEY,
^
           = 0
/Users/ssg/worker0/m-upp/build/uppsrc/CtrlCore/CocoKeys.h:13:1: error: default initialization of an object of const type 'const Upp::dword' (aka 'const unsigned int')
K_ALT_KEY,
^
          = 0
...


Regards,
Novo
Re: Gearing up for 2022.1 release... [message #58288 is a reply to message #58284] Mon, 11 April 2022 12:07 Go to previous messageGo to next message
mirek is currently offline  mirek
Messages: 13975
Registered: November 2005
Ultimate Member
Novo wrote on Fri, 08 April 2022 21:39
MacOS 10.15
./umk uppsrc ide CLANG -bus
In file included from /Users/ssg/worker0/m-upp/build/uppsrc/CtrlCore/MKeys.h:3:
/Users/ssg/worker0/m-upp/build/uppsrc/CtrlCore/CocoKeys.h:12:1: error: default initialization of an object of const type 'const Upp::dword' (aka 'const unsigned int')
K_CTRL_KEY,
^
           = 0
/Users/ssg/worker0/m-upp/build/uppsrc/CtrlCore/CocoKeys.h:13:1: error: default initialization of an object of const type 'const Upp::dword' (aka 'const unsigned int')
K_ALT_KEY,
^
          = 0
...


Should be now fixed.
Re: Gearing up for 2022.1 release... [message #58290 is a reply to message #58288] Mon, 11 April 2022 19:14 Go to previous message
Novo is currently offline  Novo
Messages: 1358
Registered: December 2006
Ultimate Contributor
mirek wrote on Mon, 11 April 2022 06:07
Novo wrote on Fri, 08 April 2022 21:39
MacOS 10.15
./umk uppsrc ide CLANG -bus
In file included from /Users/ssg/worker0/m-upp/build/uppsrc/CtrlCore/MKeys.h:3:
/Users/ssg/worker0/m-upp/build/uppsrc/CtrlCore/CocoKeys.h:12:1: error: default initialization of an object of const type 'const Upp::dword' (aka 'const unsigned int')
K_CTRL_KEY,
^
           = 0
/Users/ssg/worker0/m-upp/build/uppsrc/CtrlCore/CocoKeys.h:13:1: error: default initialization of an object of const type 'const Upp::dword' (aka 'const unsigned int')
K_ALT_KEY,
^
          = 0
...


Should be now fixed.

Thank you!
It is fixed now. Compilation on MacOS 11.1 is fine as well.


Regards,
Novo
Previous Topic: 2022.1rc1
Next Topic: 2022.1rc2
Goto Forum:
  


Current Time: Thu Mar 28 09:55:05 CET 2024

Total time taken to generate the page: 0.01431 seconds