diff options
| author | Tor Andersson <tor.andersson@artifex.com> | 2018-11-12 13:29:37 +0100 |
|---|---|---|
| committer | Tor Andersson <tor.andersson@artifex.com> | 2018-11-12 17:30:04 +0100 |
| commit | 8a8114cc9c3ae2f9bc866e15ea9f69778c63c3a3 (patch) | |
| tree | 7f031c287ae0b628c913bbac3ba0dfbeec6ce573 /include/mupdf | |
| parent | 643ff675ff47b5d3d21ebf6a30ffa844fe582f2e (diff) | |
| download | mupdf-8a8114cc9c3ae2f9bc866e15ea9f69778c63c3a3.tar.xz | |
Remove confusing flag define.
What's the difference between PDF_OBJ_FLAG_MARK and PDF_FLAGS_MARKED?
PDF_OBJ_FLAG_MARK is used to flag an xref entry as one that we want
to keep cached with the pdf_mark_xref/pdf_clear_xref_to_mark functions.
PDF_FLAGS_MARKED is used to detect unwanted recursion in PDF structures.
Renaming the xref_entry.flags field to xref_entry.marked should remove this
source of potential confusion.
Diffstat (limited to 'include/mupdf')
| -rw-r--r-- | include/mupdf/pdf/xref.h | 7 |
1 files changed, 1 insertions, 6 deletions
diff --git a/include/mupdf/pdf/xref.h b/include/mupdf/pdf/xref.h index 1924b635..0df1970d 100644 --- a/include/mupdf/pdf/xref.h +++ b/include/mupdf/pdf/xref.h @@ -41,7 +41,7 @@ typedef struct pdf_xref_entry_s pdf_xref_entry; struct pdf_xref_entry_s { char type; /* 0=unset (f)ree i(n)use (o)bjstm */ - unsigned char flags; /* bit 0 = marked */ + unsigned char marked; /* marked to keep alive with pdf_mark_xref */ unsigned short gen; /* generation / objstm index */ int num; /* original object number (for decryption after renumbering) */ int64_t ofs; /* file offset / objstm object number */ @@ -50,11 +50,6 @@ struct pdf_xref_entry_s pdf_obj *obj; /* stored/cached object */ }; -enum -{ - PDF_OBJ_FLAG_MARK = 1, -}; - typedef struct pdf_xref_subsec_s pdf_xref_subsec; struct pdf_xref_subsec_s |