Vidar Hasfjord

@luigibianchi wrote: actually I am using [my own customised version of] owlnext 7 Sorry, I didn't mean to imply that you use 8. I just wanted to make sure I acknowledged your contribution to [discussion:bcaf261176], which helped me implement support on the trunk for Embarcardero's new toolset ("Clang Modern"). While you have made your own private extension, OWLNext 7 does not officially have any support, and will never get any, since as I noted, adding support cannot be done without breaking compatibility...

@luigibianchi wrote: Regarding OWLNext7, are you sure that supporting the modern (clang15) compiler would break compatibility? Good question! On second thought, the incompatible changes that I made on the trunk [feature-requests:#249][r7102] could be made with preprocessor directives, I guess, thereby not affecting existing code. If you want to do so, feel free to add support on "branches/7", and we'll include it in the upcoming 7.0.20 release. Same goes for "branches/6.44" and the upcoming 6.44.28...

@luigibianchi wrote: Regarding OWLNext7, are you sure that supporting the modern (clang15) compiler would break compatibility? Good question! Actually, the incompatible changes that I made on the trunk [feature-requests:#249][r7102] could be made with preprocessor directives, I guess, thereby not affecting existing code. If you want to do so, feel free to add support on "branches/7", and we'll include it in the upcoming 7.0.20 release. Same goes for "branches/6.44" and the upcoming 6.44.28 release....

@luigibianchi wrote: Regarding OWLNext7, are you sure that supporting the modern (clang15) compiler would break compatibility? Good question! Actually, the incompatible changes that I made on the trunk could be made with preprocessor directives, I guess, thereby not affecting existing code. If you want to do so, feel free to add support on "branches/7", and we'll include it in the upcoming 7.0.20 release. Same goes for "branches/6.44" and the upcoming 6.44.28 release. You should coordinate with Sebastian...

@luigibianchi wrote: Regarding OWLNext7, are you sure that supporting the modern (clang15) compiler would break compatibility? Good question! Actually, the incompatible changes that I made on the trunk could be made with preprocessor directives, I guess, thereby not affecting existing code. If you want to do so, feel free to add support on "branches/7", and we'll include it in the upcoming 7.0.20 release. Same goes for "branches/6.44" and the upcoming 6.44.28 release. You should coordinate with Sebastian...

@luigibianchi wrote: Regarding OWLNext7, are you sure that supporting the modern (clang15) compiler would break compatibility? Good question! Actually, the incompatible changes that I made on the trunk could be made with preprocessor directives, I guess, thereby not affecting existing code. If you want to do so, feel free to add support on "branches/7", and we'll include it in the upcoming 7.0.20) release. Same goes for "branches/6.44" and upcoming 6.44.28 release. You should coordinate with Sebastian...

@luigibianchi wrote: Regarding OWLNext7, are you sure that supporting the modern (clang15) compiler would break compatibility? Good question! Actually, the imcompatible changes that I made on the trunk could be made with preprocessor directives, I guess, thereby not affecting existing code. If you want to do so, feel free to add support on "branches/7", and we'll include it in the upcoming 7.0.20) release. Same goes for "branches/6.44" and upcoming 6.44.28 release. You should coordinate with Sebastian...

@luigibianchi wrote: actually I am using [my own customised version of] owlnext 7 Sorry, I didn't mean to imply that you use 8. I just wanted to make sure I acknowledged your contribution to [discussion:bcaf261176], which helped me implement support on the trunk for Embarcardero's new toolset ("Clang Modern"). While you have made your own private extension, OWLNext 7 does not officially have any support, and will never get any, since as I noted, adding support cannot be done without breaking compatibility...