diff options
author | Robin Watts <robin.watts@artifex.com> | 2012-10-08 16:16:14 +0100 |
---|---|---|
committer | Robin Watts <robin.watts@artifex.com> | 2012-10-08 16:57:44 +0100 |
commit | dd4f6ffd475b0e769ba6231cf24b050bcdc97814 (patch) | |
tree | 96afc56cb815e26c39e8d95e0e906c165d82fe66 /apps/man/mupdf.1 | |
parent | d66ff690beb8c49e39311c9f6208fd4ac1fc1e1f (diff) | |
download | mupdf-dd4f6ffd475b0e769ba6231cf24b050bcdc97814.tar.xz |
Bug 693350: Add some dreaded 'const's for string keys.
On the whole we avoid using const within MuPDF, but bug 693350
highlights cases where this can cause a problem with C++.
In C, if you do: foo("bar"); then "bar" has type char *.
In C++, if you do foo("bar"); then "bar" has type const char *.
This means that any calls to the MuPDF library from C++ that take
strings give warnings.
The fix is simple, so it seems to be worthwhile adding a few consts.
None of our internal data structures are affected in any way by
this change.
Thanks to Franz Fellner for pointing out this issue.
Diffstat (limited to 'apps/man/mupdf.1')
0 files changed, 0 insertions, 0 deletions