be freed. We use the verbs “keep” and “drop” to increment and decrement the reference count. For simplicity, we also use the word “drop” for non-reference counted objects (so that in case we change our minds Python bindings, one can use pypi.org’s SWIG, installing with python -m pip install swig. But for simplicity the instructions below will specify a generic SWIG that will also gen- erate C# bindings. • For demand it, but we consider small changes in the API to be a price worth paying for clarity and simplicity. To minimise the impact of such changes, we undertake to list the API changes between different

be freed. We use the verbs “keep” and “drop” to increment and decrement the reference count. For simplicity, we also use the word “drop” for non-reference counted objects (so that in case we change our minds demand it, but we consider small changes in the API to be a price worth paying for clarity and simplicity. To minimise the impact of such changes, we undertake to list the API changes between different const. Having some functions take const fz_colorspace and some not is confusing, so therefore, for simplicity, all fz_colorspaces are now passed as non const. This should not affect any user code. • fz_process_shade()

be freed. We use the verbs “keep” and “drop” to increment and decrement the reference count. For simplicity, we also use the word “drop” for non-reference counted objects (so that in case we change our minds demand it, but we consider small changes in the API to be a price worth paying for clarity and simplicity. To minimise the impact of such changes, we undertake to list the API changes between different const. Having some functions take const fz_colorspace and some not is confusing, so therefore, for simplicity, all fz_colorspaces are now passed as non const. This should not affect any user code. • fz_process_shade()

be freed. We use the verbs “keep” and “drop” to increment and decrement the reference count. For simplicity, we also use the word “drop” for non-reference counted objects (so that in case we change our minds demand it, but we consider small changes in the API to be a price worth paying for clarity and simplicity. To minimise the impact of such changes, we undertake to list the API changes between different const. Having some functions take const fz_colorspace and some not is confusing, so therefore, for simplicity, all fz_colorspaces are now passed as non const. This should not affect any user code. • fz_process_shade()