aboutsummaryrefslogtreecommitdiffstats
path: root/libqpdf/qpdf/Pl_RC4.hh
diff options
context:
space:
mode:
authorJay Berkenbilt <ejb@ql.org>2022-02-08 15:18:08 +0100
committerJay Berkenbilt <ejb@ql.org>2022-02-08 17:51:15 +0100
commitcb769c62e55599e9f980001830bc61d9fcaa64a9 (patch)
tree0bf980c385a61cbc8720cf990762ffc1200f9d6a /libqpdf/qpdf/Pl_RC4.hh
parent716381f65a2b2dc72f8da2426ba71aeab02c507f (diff)
downloadqpdf-cb769c62e55599e9f980001830bc61d9fcaa64a9.tar.zst
WHITESPACE ONLY -- expand tabs in source code
This comment expands all tabs using an 8-character tab-width. You should ignore this commit when using git blame or use git blame -w. In the early days, I used to use tabs where possible for indentation, since emacs did this automatically. In recent years, I have switched to only using spaces, which means qpdf source code has been a mixture of spaces and tabs. I have avoided cleaning this up because of not wanting gratuitous whitespaces change to cloud the output of git blame, but I changed my mind after discussing with users who view qpdf source code in editors/IDEs that have other tab widths by default and in light of the fact that I am planning to start applying automatic code formatting soon.
Diffstat (limited to 'libqpdf/qpdf/Pl_RC4.hh')
-rw-r--r--libqpdf/qpdf/Pl_RC4.hh4
1 files changed, 2 insertions, 2 deletions
diff --git a/libqpdf/qpdf/Pl_RC4.hh b/libqpdf/qpdf/Pl_RC4.hh
index 250ab2b8..33e35d58 100644
--- a/libqpdf/qpdf/Pl_RC4.hh
+++ b/libqpdf/qpdf/Pl_RC4.hh
@@ -13,8 +13,8 @@ class Pl_RC4: public Pipeline
// key_len of -1 means treat key_data as a null-terminated string
QPDF_DLL
Pl_RC4(char const* identifier, Pipeline* next,
- unsigned char const* key_data, int key_len = -1,
- size_t out_bufsize = def_bufsize);
+ unsigned char const* key_data, int key_len = -1,
+ size_t out_bufsize = def_bufsize);
QPDF_DLL
virtual ~Pl_RC4();