mirror of
https://github.com/qpdf/qpdf.git
synced 2024-11-09 23:00:57 +00:00
cb769c62e5
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.
40 lines
815 B
Perl
40 lines
815 B
Perl
#!/usr/bin/env perl
|
|
require 5.008;
|
|
BEGIN { $^W = 1; }
|
|
use strict;
|
|
|
|
chdir("lzw") or die "chdir testdir failed: $!\n";
|
|
|
|
require TestDriver;
|
|
|
|
my $td = new TestDriver('lzw');
|
|
|
|
cleanup();
|
|
|
|
$td->runtest("decode: early code change",
|
|
{$td->COMMAND => "lzw lzw1.in tmp"},
|
|
{$td->STRING => "",
|
|
$td->EXIT_STATUS => 0});
|
|
|
|
$td->runtest("check output",
|
|
{$td->FILE => "tmp"},
|
|
{$td->FILE => "lzw1.out"});
|
|
|
|
$td->runtest("decode: no early code change",
|
|
{$td->COMMAND => "lzw lzw2.in tmp --no-early-code-change"},
|
|
{$td->STRING => "",
|
|
$td->EXIT_STATUS => 0});
|
|
|
|
$td->runtest("check output",
|
|
{$td->FILE => "tmp"},
|
|
{$td->FILE => "lzw2.out"});
|
|
|
|
cleanup();
|
|
|
|
$td->report(4);
|
|
|
|
sub cleanup
|
|
{
|
|
unlink "tmp";
|
|
}
|