Re: [Flightgear-devel] C++ and/or OSG question

[Scott <sc...@gm...>]

#1 - I recommend taking a look at the C++ Core Guidelines

#2 - clang-tiny can report c++11 modernizer results

#3 - No, they are not disabled to my knowledge

#4 - Much of plib has already been replaced.  The big piece that remains 
is the GUI in which James and I were collaborating on last year for 
potential replacement of it - presently on our backlog.

Scott


On 3/18/20 10:44 AM, Patrick Callahan wrote:
> 1. Is there advice somewhere on what older c++ styles or forms to 
> watch for and how to think about them?
> Something along the lines of:
>   When you see a try/catch block, think about the following:
>   1. .....
>   2. .....
>   3. .....
>   Specific advice from senior Flightgear developers guiding folks like 
> me might help move things along.
>
> 2. Is there any kind of linting tool or compiler setting that can 
> detect code structures that might benefit from a more modern style of 
> coding in a given C++ version?
>
> 3. in the tools we use like jenkins, download_and_compile.sh and 
> fg-from-scratch,  do we see deprecation warnings, or are they turned 
> off in any of these tools?
>
> 4. gcc allows you to mark a function deprecated and will produce a 
> warning wherever deprecated code is used.   If we marked all of plib 
> as deprecated and built with it so marked, would that help to identify 
> code that calls things in plib that should be replaced?
>
> -p callahan
>
>