summaryrefslogtreecommitdiffstats
path: root/libqpdf/Pl_Count.cc
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/Pl_Count.cc
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/Pl_Count.cc')
-rw-r--r--libqpdf/Pl_Count.cc6
1 files changed, 3 insertions, 3 deletions
diff --git a/libqpdf/Pl_Count.cc b/libqpdf/Pl_Count.cc
index b245866c..65fd9e3f 100644
--- a/libqpdf/Pl_Count.cc
+++ b/libqpdf/Pl_Count.cc
@@ -27,9 +27,9 @@ Pl_Count::write(unsigned char* buf, size_t len)
{
if (len)
{
- this->m->count += QIntC::to_offset(len);
- this->m->last_char = buf[len - 1];
- getNext()->write(buf, len);
+ this->m->count += QIntC::to_offset(len);
+ this->m->last_char = buf[len - 1];
+ getNext()->write(buf, len);
}
}