[Olena] #296: Adress recent GCC warnings regarding unused local typedefs
#296: Adress recent GCC warnings regarding unused local typedefs ----------------------+------------------------ Reporter: levill_r | Owner: Olena Team Type: defect | Status: new Priority: major | Milestone: Olena 2.1 Component: Milena | Version: 2.0 Keywords: | ----------------------+------------------------ GCC's `-Wunused-local-typedefs` option (which seems to be hooked to `-Wall` since version 4.8) triggers a lot of messages regarding Milena's code (and probably Scribo's as well). Some cases are easy to solve (typedefs actually used nowhere), while others are more delicate to handle, as `typedef` is used as a concept checking mechanism within Milena's concept classes. See how other projects doing concept checking with typedefs handled this issue. I guess we may be able to leverage GCC attributes to solve this. -- Ticket URL: <https://trac.lrde.epita.fr/olena/ticket/296> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform
#296: Adress recent GCC warnings regarding unused local typedefs -----------------------+------------------------ Reporter: levill_r | Owner: Olena Team Type: defect | Status: new Priority: major | Milestone: Olena 2.1 Component: Milena | Version: 2.0 Resolution: | Keywords: -----------------------+------------------------ Description changed by levill_r: Old description:
GCC's `-Wunused-local-typedefs` option (which seems to be hooked to `-Wall` since version 4.8) triggers a lot of messages regarding Milena's code (and probably Scribo's as well).
Some cases are easy to solve (typedefs actually used nowhere), while others are more delicate to handle, as `typedef` is used as a concept checking mechanism within Milena's concept classes. See how other projects doing concept checking with typedefs handled this issue. I guess we may be able to leverage GCC attributes to solve this.
New description: GCC's `-Wunused-local-typedefs` option (which seems to be hooked to `-Wall` since version 4.8) triggers a lot of messages regarding Milena's code (and probably Scribo's as well). Some cases are easy to solve (typedefs actually used nowhere), while others are more delicate to handle, as `typedef` is used as a concept checking mechanism within Milena's concept classes. See how other projects doing concept checking with typedefs handled this issue. I guess we may be able to leverage GCC attributes to solve this. Or maybe use macros, as suggested by Akim. -- -- Ticket URL: <https://trac.lrde.epita.fr/olena/ticket/296#comment:1> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform
#296: Adress recent GCC warnings regarding unused local typedefs --------------------------+----------------------- Reporter: levill_r | Owner: levill_r Type: enhancement | Status: new Priority: major | Milestone: Olena 2.1 Component: Milena | Version: 2.0 Resolution: | Keywords: --------------------------+----------------------- Changes (by levill_r): * owner: Olena Team => levill_r * type: defect => enhancement -- Ticket URL: <https://trac.lrde.epita.fr/olena/ticket/296#comment:2> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform
#296: Adress recent GCC warnings regarding unused local typedefs --------------------------+----------------------- Reporter: levill_r | Owner: levill_r Type: enhancement | Status: closed Priority: major | Milestone: Olena 2.1 Component: Milena | Version: 2.0 Resolution: fixed | Keywords: --------------------------+----------------------- Changes (by levill_r): * status: new => closed * resolution: => fixed -- Ticket URL: <https://trac.lrde.org/olena/ticket/296#comment:3> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient image processing platform
participants (1)
-
Olena Trac