albert-github

This is based on the warning type: 4244 'conversion_type': conversion from 'type1' to 'type2', possible loss of data

This is based on the warning type: 4100 'identifier': unreferenced formal parameter

Specifically handle the bit-field case where the name field contains `int`, `char`, `long`, `short` as they would be types.

Based on the discussion with PR #9555 checking for the file encoding

This is based on the warning type: C4800: Implicit conversion from 'type' to bool. Possible information loss A real bug was found in the writing out of the boolean replacement...

Based on the pull request #9561 adding shadowing warnings for the windows compilation

When having a simple file like: ``` \secreflist \refitem cmdilinebr0 @@ilinebr \refitem cmdilinebr1 \\ilinebr \refitem cmdilinebr2 @\ilinebr \refitem cmdilinebr3 \@ilinebr \endsecreflist as @@_ilinebr and \\_ilinebr as @\_ilinebr and \@_ilinebr \anchor...

bug_777266 Environment variable expansion to default if not set in config file

1

Use BASH-Like parameter expansion: https://www.gnu.org/software/bash/manual/bash.html#Shell-Parameter-Expansion An example would be: `GENERATE_HTML = "$(DX_GENERATE_HTML:-YES)"`

In the preprocessor we have to ignore Fortran comment not only at the beginning of the line but also after a statement like `INTEGER :: I !< The user's comment`....

Doxygen version 1.9.4 (and older) and current master (1.9.5 (5763255ba4fb02b7fa11300515f46fbfda38180e) Example: [example.tar.gz](https://github.com/doxygen/doxygen/files/9288612/example.tar.gz) (Found in the asymptote version 2.82 package By Fossies.) When having: ``` #!/usr/bin/env python3 import gettext p =...