Currently the dozen header files an embedder may need to include live in
fpdfsdk/include, along with a half-dozen other files that shouldn't be included.
It would be much cleaner if the first kind moved to a top-level public/
directory, with consistent naming (i.e. all files start with fpdf, but some
files have underscores and some don't (e.g. fpdfview.h vs. fpdf_dataavail.h)).
public/ itself should be entirely self-contained.
Original issue reported on code.google.com by tsepez@chromium.org on 5 Mar 2015 at 12:38
Original issue reported on code.google.com by
tsepez@chromium.org
on 5 Mar 2015 at 12:38