[riot-notifications] [RIOT-OS/RIOT] WIP net/tcp: make header option pointer c++ compliant (#11300)
notifications at github.com
Sat Mar 30 08:39:36 CET 2019
> > I am fine with replacing the dynamic sized array in general, but I wonder since then this is not iso-c++ compliant?
> Using cppreference.com as something that should com close to the standard, [classes](https://en.cppreference.com/w/cpp/language/classes) can have [non-static data members](https://en.cppreference.com/w/cpp/language/data_members), which are not allowed to be of [incomplete type](https://en.cppreference.com/w/cpp/language/type#Incomplete_type), for which an [array of unknown bound](https://en.cppreference.com/w/cpp/language/array#Arrays_of_unknown_bound) is an example.
> That does technically not answer your question, but it seems like this has always been the case.
> I note that gcc can handle it, but issues a warning, what leads to an error in the default build settings of RIOT
Thanks for the links. I learned something. I am just wondering I am using gcc at work and I never notices an warning from such constructs.
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the notifications