On Tue, 2018-02-27 at 16:54 +0100, zyx wrote:
> this introduces new compiler warning in podofosign (interestingly
> only at this place, good job):
Hi again,
I forgot to add, I do not think that implicit casts cause any real
issue, compilers are able to claim warnings when it's a problem these
days, thus it should be better to address them, than to hunt for
static_cast<>-s or anything like that, which can work for the external
library API of version X, but would cause similar casts with version Y
(like when the API changes between X and Y).
There are surely issues with higher priority and higher impact than
this (not that having a clean code is a wrong thing, it's the opposite;
compilers usually do know why they claim certain issues and having the
code without compiler warnings is a good goal to achieve).
Just my opinion.
Bye,
zyx
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Podofo-users mailing list
Podofo-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/podofo-users
