Single public header file or separate by topic

[farindk]

The heif.h header file is growing to a large size. Recently, support for regions was added, which introduced a lot of new functions. This begs the question whether we should put all API declarations into a single heif.h file or whether we should split it into several files, like heif-regions.h.

[bradh]

I think the first two are the same from a user perspective (i.e. I need heif.h, and how it works under the hood is an implementation detail).

I would support splitting off the regions and other specialist functionality as it is added. I'm not sure whether existing API should be split off until 2.x.

[farindk]

Yes, I would not split off things that are currently in heif.h to maintain backward compatibility. But the regions part is a good candidate because it is not released yet.