Result:
found more than 1015 distributions - search limited to the first 2001 files matching your query
( run in 1.371 )
Task-Cpanel-Internal
view release on metacpan or search on metacpan
lib/Task/Cpanel/Internal.pm view on Meta::CPAN
=cut
use Storable;
=item L<String::BOM|String::BOM>
simple utilities to check for a BOM and strip a BOM
=cut
use String::BOM;
=item L<String::CRC32|String::CRC32>
Perl interface for cyclic redundency check generation
Task-HTML5
view release on metacpan or search on metacpan
inc/YAML/Tiny.pm view on Meta::CPAN
return $self->_error("Did not provide a string to load");
}
# Byte order marks
# NOTE: Keeping this here to educate maintainers
# my %BOM = (
# "\357\273\277" => 'UTF-8',
# "\376\377" => 'UTF-16BE',
# "\377\376" => 'UTF-16LE',
# "\377\376\0\0" => 'UTF-32LE'
# "\0\0\376\377" => 'UTF-32BE',
# );
if ( $string =~ /^(?:\376\377|\377\376|\377\376\0\0|\0\0\376\377)/ ) {
return $self->_error("Stream has a non UTF-8 BOM");
} else {
# Strip UTF-8 bom if found, we'll just ignore it
$string =~ s/^\357\273\277//;
}
Task-Lingua-Any-Numbers
view release on metacpan or search on metacpan
t/03-basic.t view on Meta::CPAN
#!/usr/bin/env perl -w
# CAVEAT EMPTOR: This file is UTF8 encoded (BOM-less)
# Burak Gürsoy <burak[at]cpan[dot]org>
use strict;
use warnings;
use Test::More qw( no_plan );
Task-Perl-Critic
view release on metacpan or search on metacpan
Debian_CPANTS.txt view on Meta::CPAN
"libfax-hylafax-client-perl", "Fax-Hylafax-Client", "1.02", "0", "0"
"libfcgi-perl", "FCGI", "0.71", "1", "1"
"libfcgi-procmanager-perl", "FCGI-ProcManager", "0.19", "0", "0"
"libfeed-find-perl", "Feed-Find", "0.07", "0", "1"
"libfile-basedir-perl", "File-BaseDir", "0.03", "0", "1"
"libfile-bom-perl", "File-BOM", "0.14", "0", "0"
"libfile-changenotify-perl", "File-ChangeNotify", "0.20", "0", "0"
"libfile-chmod-perl", "File-chmod", "0.32", "0", "0"
"libfile-copy-link-perl", "File-Copy-Link", "0.112", "0", "0"
"libfile-copy-recursive-perl", "File-Copy-Recursive", "0.38", "1", "0"
"libfile-counterfile-perl", "File-CounterFile", "1.04", "0", "0"
Telegram-JsonAPI
view release on metacpan or search on metacpan
(index($4, 'n') >= 0 ? ( nothxarg => 1 ) : ()),
} )
: die "invalid spec: $_" } qw(
AvFILLp|5.004050||p
AvFILL|||
BOM_UTF8|||
BhkDISABLE||5.024000|
BhkENABLE||5.024000|
BhkENTRY_set||5.024000|
BhkENTRY|||
BhkFLAGS|||
Template-Flute
view release on metacpan or search on metacpan
0.0184 Thu Jul 16 09:33:23 2015 CEST
[BUG FIXES]
* Remove BOM when processing files (Marco Pessotto, GH #102, #103).
* Fix lost newlines for textarea values (Marco Pessotto, GH #105, #106).
0.0183 Sun Jul 5 19:06:50 2015 CEST
[BUG FIXES]
Template-Plugin-Decode
view release on metacpan or search on metacpan
lib/Template/Plugin/Decode.pm view on Meta::CPAN
To prevent it, use this module.
This is a one of solutions for this problem.
Use utf-8 template files with BOM and decode parameters that are embedded into it,
and you'll never seen garbled text.
=head1 AUTHOR
Lyo Kato E<lt>kato@lost-season.jpE<gt>
Template-Plugin-Filter-Pipe
view release on metacpan or search on metacpan
t/000-report-versions.t view on Meta::CPAN
return $self->_error("Did not provide a string to load");
}
# Byte order marks
# NOTE: Keeping this here to educate maintainers
# my %BOM = (
# "\357\273\277" => 'UTF-8',
# "\376\377" => 'UTF-16BE',
# "\377\376" => 'UTF-16LE',
# "\377\376\0\0" => 'UTF-32LE'
# "\0\0\376\377" => 'UTF-32BE',
# );
if ( $string =~ /^(?:\376\377|\377\376|\377\376\0\0|\0\0\376\377)/ ) {
return $self->_error("Stream has a non UTF-8 BOM");
} else {
# Strip UTF-8 bom if found, we'll just ignore it
$string =~ s/^\357\273\277//;
}
Template-Plugin-HTMLToJS
view release on metacpan or search on metacpan
t/000-report-versions.t view on Meta::CPAN
return $self->_error("Did not provide a string to load");
}
# Byte order marks
# NOTE: Keeping this here to educate maintainers
# my %BOM = (
# "\357\273\277" => 'UTF-8',
# "\376\377" => 'UTF-16BE',
# "\377\376" => 'UTF-16LE',
# "\377\376\0\0" => 'UTF-32LE'
# "\0\0\376\377" => 'UTF-32BE',
# );
if ( $string =~ /^(?:\376\377|\377\376|\377\376\0\0|\0\0\376\377)/ ) {
return $self->_error("Stream has a non UTF-8 BOM");
}
else {
# Strip UTF-8 bom if found, we'll just ignore it
$string =~ s/^\357\273\277//;
}
Template-Plugin-Haml
view release on metacpan or search on metacpan
t/000-report-versions.t view on Meta::CPAN
return $self->_error("Did not provide a string to load");
}
# Byte order marks
# NOTE: Keeping this here to educate maintainers
# my %BOM = (
# "\357\273\277" => 'UTF-8',
# "\376\377" => 'UTF-16BE',
# "\377\376" => 'UTF-16LE',
# "\377\376\0\0" => 'UTF-32LE'
# "\0\0\376\377" => 'UTF-32BE',
# );
if ( $string =~ /^(?:\376\377|\377\376|\377\376\0\0|\0\0\376\377)/ ) {
return $self->_error("Stream has a non UTF-8 BOM");
} else {
# Strip UTF-8 bom if found, we'll just ignore it
$string =~ s/^\357\273\277//;
}
Template-Provider-Encoding
view release on metacpan or search on metacpan
lib/Template/Provider/Encoding.pm view on Meta::CPAN
[% USE encoding 'utf-8' %]
Here comes utf-8 strings with [% variable %].
=head1 DIFFERNCE WITH OTHER WAYS
=head2 UNICODE option and BOM
Recent TT allows C<UNICODE> option to Template::Provider and by adding
it Provider scans BOM (byte-order mark) to detect UTF-8/UTF-16 encoded
template files. This module does basically the same thing in a
different way, but IMHO adding BOM to template files is a little
painful especially for non-programmers.
=head2 Template::Provider::Encode
L<Template::Provider::Encode> provides a very similar way to detect
Template-Provider-Unicode-Japanese
view release on metacpan or search on metacpan
lib/Template/Provider/Unicode/Japanese.pm view on Meta::CPAN
=head1 DESCRIPTION
If the utf8 flag is different between the template and
the string inserted(such as [% var %]), the output will be unreadable.
We should make all of them utf8 flagged.
However, Template::Provider::_decode_unicode decode only data with BOM.
This provider makes all templates utf8 flagged by Unicode::Japanese.
=head1 SUBROUTINES/METHODS
=head2 _load(@)
Template-ShowStartStop
view release on metacpan or search on metacpan
t/000-report-versions.t view on Meta::CPAN
return $self->_error("Did not provide a string to load");
}
# Byte order marks
# NOTE: Keeping this here to educate maintainers
# my %BOM = (
# "\357\273\277" => 'UTF-8',
# "\376\377" => 'UTF-16BE',
# "\377\376" => 'UTF-16LE',
# "\377\376\0\0" => 'UTF-32LE'
# "\0\0\376\377" => 'UTF-32BE',
# );
if ( $string =~ /^(?:\376\377|\377\376|\377\376\0\0|\0\0\376\377)/ ) {
return $self->_error("Stream has a non UTF-8 BOM");
} else {
# Strip UTF-8 bom if found, we'll just ignore it
$string =~ s/^\357\273\277//;
}
Template-Toolkit
view release on metacpan or search on metacpan
lib/Template/Provider.pm view on Meta::CPAN
}
#------------------------------------------------------------------------
# _decode_unicode
#
# Decodes encoded unicode text that starts with a BOM and
# turns it into perl's internal representation
#------------------------------------------------------------------------
sub _decode_unicode {
my $self = shift;
lib/Template/Provider.pm view on Meta::CPAN
use bytes;
require Encode;
return $string if Encode::is_utf8( $string );
# try all the BOMs in order looking for one (order is important
# 32bit BOMs look like 16bit BOMs)
my $count = 0;
while ($count < @{ $boms }) {
my $enc = $boms->[$count++];
lib/Template/Provider.pm view on Meta::CPAN
file handle or text string.
=head2 ENCODING
The Template Toolkit will automatically decode Unicode templates that
have a Byte Order Marker (BOM) at the start of the file. This option
can be used to set the default encoding for templates that don't define
a BOM.
my $provider = Template::Provider->new({
ENCODING => 'utf8',
});
Term-DNAColor
view release on metacpan or search on metacpan
t/000-report-versions.t view on Meta::CPAN
return $self->_error("Did not provide a string to load");
}
# Byte order marks
# NOTE: Keeping this here to educate maintainers
# my %BOM = (
# "\357\273\277" => 'UTF-8',
# "\376\377" => 'UTF-16BE',
# "\377\376" => 'UTF-16LE',
# "\377\376\0\0" => 'UTF-32LE'
# "\0\0\376\377" => 'UTF-32BE',
# );
if ( $string =~ /^(?:\376\377|\377\376|\377\376\0\0|\0\0\376\377)/ ) {
return $self->_error("Stream has a non UTF-8 BOM");
} else {
# Strip UTF-8 bom if found, we'll just ignore it
$string =~ s/^\357\273\277//;
}
Term-ReadLine-Gnu
view release on metacpan or search on metacpan
BOL_t8_p8|5.033003||Viu
BOL_t8_pb|5.033003||Viu
BOL_tb|5.035004||Viu
BOL_tb_p8|5.033003||Viu
BOL_tb_pb|5.033003||Viu
BOM_UTF8|5.025005|5.003007|p
BOM_UTF8_FIRST_BYTE|5.019004||Viu
BOM_UTF8_TAIL|5.019004||Viu
boolSV|5.004000|5.003007|p
boot_core_builtin|5.035007||Viu
boot_core_mro|5.009005||Viu
boot_core_PerlIO|5.007002||Viu
boot_core_UNIVERSAL|5.003007||Viu
#endif
#endif
#if 'A' == 65
#ifndef BOM_UTF8
# define BOM_UTF8 "\xEF\xBB\xBF"
#endif
#ifndef REPLACEMENT_CHARACTER_UTF8
# define REPLACEMENT_CHARACTER_UTF8 "\xEF\xBF\xBD"
#endif
#elif '^' == 95
#ifndef BOM_UTF8
# define BOM_UTF8 "\xDD\x73\x66\x73"
#endif
#ifndef REPLACEMENT_CHARACTER_UTF8
# define REPLACEMENT_CHARACTER_UTF8 "\xDD\x73\x73\x71"
#endif
#elif '^' == 176
#ifndef BOM_UTF8
# define BOM_UTF8 "\xDD\x72\x65\x72"
#endif
#ifndef REPLACEMENT_CHARACTER_UTF8
# define REPLACEMENT_CHARACTER_UTF8 "\xDD\x72\x72\x70"
#endif
Term-Shell-Enhanced
view release on metacpan or search on metacpan
t/000-report-versions.t view on Meta::CPAN
return $self->_error("Did not provide a string to load");
}
# Byte order marks
# NOTE: Keeping this here to educate maintainers
# my %BOM = (
# "\357\273\277" => 'UTF-8',
# "\376\377" => 'UTF-16BE',
# "\377\376" => 'UTF-16LE',
# "\377\376\0\0" => 'UTF-32LE'
# "\0\0\376\377" => 'UTF-32BE',
# );
if ( $string =~ /^(?:\376\377|\377\376|\377\376\0\0|\0\0\376\377)/ ) {
return $self->_error("Stream has a non UTF-8 BOM");
} else {
# Strip UTF-8 bom if found, we'll just ignore it
$string =~ s/^\357\273\277//;
}
Test-Arrow
view release on metacpan or search on metacpan
requires 'Test::Pod';
requires 'Test::NoTabs';
requires 'Test::Perl::Metrics::Lite';
requires 'Test::Vars';
requires 'File::Find::Rule::ConflictMarker';
requires 'File::Find::Rule::BOM';
};
Test-BOM
view release on metacpan or search on metacpan
lib/Test/BOM.pm view on Meta::CPAN
package Test::BOM;
$Test::BOM::VERSION = '0.001';
# ABSTRACT: Test strings and files for BOM
use strict;
use warnings;
use base qw(Test::Builder::Module);
our @EXPORT = qw(string_has_bom string_hasnt_bom file_has_bom file_hasnt_bom);
# We have subs of the same name, don't import them
use String::BOM qw();
my $CLASS = __PACKAGE__;
my $Tester = $CLASS->builder;
sub string_has_bom {
my ($string) = @_;
my $ok = String::BOM::string_has_bom($string);
$Tester->ok( $ok, q{string has BOM} );
unless ($ok) {
$Tester->diag('String was expected to have a BOM but did not.');
}
return $ok;
}
sub string_hasnt_bom {
my ($string) = @_;
my $ok = String::BOM::string_has_bom($string);
$Tester->ok( !$ok, q{string hasn't BOM} );
if ($ok) {
$Tester->diag('String was expected not to have a BOM but it has.');
}
return !$ok;
}
sub file_has_bom {
my ($string) = @_;
my $ok = String::BOM::file_has_bom($string);
$Tester->ok( $ok, q{file has BOM} );
unless ($ok) {
$Tester->diag('File was expected to have a BOM but did not.');
}
return $ok;
}
sub file_hasnt_bom {
my ($string) = @_;
my $ok = String::BOM::file_has_bom($string);
$Tester->ok( !$ok, q{file has BOM} );
if ($ok) {
$Tester->diag('File was expected to not have a BOM but it has.');
}
return !$ok;
}
lib/Test/BOM.pm view on Meta::CPAN
=encoding UTF-8
=head1 NAME
Test::BOM - Test strings and files for BOM
=head1 VERSION
version 0.001
=head1 SYNOPSIS
use Test::More;
use Test::BOM
string_has_bom("\x00\x00\xfe\xff");
string_hasnt_bom("blargh");
file_has_bom('t/data/foo');
lib/Test/BOM.pm view on Meta::CPAN
about L<Test::More> before preceding. This module uses the L<Test::Builder>
framework.
Byte-order-marks are by definition to be found at the beginning of any content,
so the functions this module provides take a look at the start of either a
string or a file. It does this by using functions from L<String::BOM> and basically just wraps them for use with L<Test::Builder>.
By default the following functions are imported into your namespace: C<string_has_bom>, C<string_hasnt_bom>, C<file_has_bom>, C<file_hasnt_bom>.
=head1 FUNCTIONS
=head2 string_has_bom ($string)
Passes if the string has a BOM, fails if not.
=head2 string_hasnt_bom ($string)
Passes if string doesn't have a BOM, fails if it has.
=head2 file_has_bom ($filename)
Passes if the file has a BOM, fails if it doesn't.
=head2 file_hasnt_bom ($filename)
Passes if the file doesn't have a BOM, fails if it has.
=head1 SEE ALSO
There are some distributions that help you dealing with BOMs in different ways:
=over 4
=item L<String::BOM> is used by this module to check for BOM.
=item L<File::BOM::Utils> contains functions to check for, add and remove BOM
from files.
=item L<File::BOM> can be used to actually read from files that have BOMs as seamlessly as possible.
=item L<PPI::Token::BOM> represents a BOM when using L<PPI> to parse perl.
=item The distribution L<Dist::Zilla::Plugin::Web> contains the module
L<Dist::Zilla::Plugin::Web::StripBOM> that strips BOM from files.
=back
Additional information about BOM and it's usage:
=over 4
=item L<http://www.unicode.org/faq/utf_bom.html#BOM> is the FAQ for the
BOM from the Unicode Consortium.
=item L<https://docs.microsoft.com/de-de/windows/desktop/Intl/using-byte-order-marks>
explains how Microsoft wants the BOM to be used. Since this document dates from
2018 (as of this writing) it's very likely to get in contact with files
containing BOM.
=back
=head1 AUTHOR
Test-Bomb
view release on metacpan or search on metacpan
lib/Test/Bomb.pm view on Meta::CPAN
our @EXPORT = qw/ bomb /;
my @configFiles = (
$ENV{TESTBOMBCONFIG} || '',
'./t/tbc', './t/testbombconfig',
'./.tbc', './.testbombconfig',
'./tbc', './testbombconfig',
($ENV{HOME}||'.').'/.tbc',
($ENV{HOME}||'.').'/.testbombconfig',
lib/Test/Bomb.pm view on Meta::CPAN
all whitespace is ignored. everything on the matching line is used
for the test. Non-matching lines are ignored.
The first file found is used, the first file checked is the environment
variable TESTBOMBCONFIG followed by [.]tbc and [.]testbombconfig in various
places
=item %groups
This variable allow groups to be assigned programatically.
Test-Class-GetoptControl
view release on metacpan or search on metacpan
t/000-report-versions.t view on Meta::CPAN
return $self->_error("Did not provide a string to load");
}
# Byte order marks
# NOTE: Keeping this here to educate maintainers
# my %BOM = (
# "\357\273\277" => 'UTF-8',
# "\376\377" => 'UTF-16BE',
# "\377\376" => 'UTF-16LE',
# "\377\376\0\0" => 'UTF-32LE'
# "\0\0\376\377" => 'UTF-32BE',
# );
if ( $string =~ /^(?:\376\377|\377\376|\377\376\0\0|\0\0\376\377)/ ) {
return $self->_error("Stream has a non UTF-8 BOM");
} else {
# Strip UTF-8 bom if found, we'll just ignore it
$string =~ s/^\357\273\277//;
}
Test-CompanionClasses
view release on metacpan or search on metacpan
t/000-report-versions.t view on Meta::CPAN
return $self->_error("Did not provide a string to load");
}
# Byte order marks
# NOTE: Keeping this here to educate maintainers
# my %BOM = (
# "\357\273\277" => 'UTF-8',
# "\376\377" => 'UTF-16BE',
# "\377\376" => 'UTF-16LE',
# "\377\376\0\0" => 'UTF-32LE'
# "\0\0\376\377" => 'UTF-32BE',
# );
if ( $string =~ /^(?:\376\377|\377\376|\377\376\0\0|\0\0\376\377)/ ) {
return $self->_error("Stream has a non UTF-8 BOM");
} else {
# Strip UTF-8 bom if found, we'll just ignore it
$string =~ s/^\357\273\277//;
}
Test-Excel
view release on metacpan or search on metacpan
1.38 Sat Aug 06 20:00:00 2016
- Updated Copyright year information.
1.37 Tue Feb 17 11:20:00 2015
- Removed BOM from the following test scripts:
- t/30_compare_excel.t
- t/40_unit_test.t
- t/50_spec_test.t
1.36 Sun Feb 15 10:50:00 2015
Test-LocalFunctions
view release on metacpan or search on metacpan
lib/Test/LocalFunctions/PPI.pm view on Meta::CPAN
sub _prune_PPI_tokens {
my $document = shift;
my @surplus_tokens = (
'Operator', 'Number', 'Comment', 'Pod',
'BOM', 'Data', 'End', 'Prototype',
'Separator', 'Quote',
);
foreach my $surplus_token (@surplus_tokens) {
$document->prune( 'PPI::Token::' . $surplus_token );
Test-Mojibake
view release on metacpan or search on metacpan
lib/Test/Mojibake.pm view on Meta::CPAN
my $n = 1;
my %pod = ();
while (my $line = <$fh>) {
if (($n == 1) && $line =~ /^\x{EF}\x{BB}\x{BF}/x) {
$Test->ok(0, $name);
$Test->diag("UTF-8 BOM (Byte Order Mark) found in $file");
return;
} elsif ($line =~ /^=+cut\s*$/x) {
$pod = 0;
} elsif ($line =~ /^=+encoding\s+([\w\-]+)/x) {
my $pod_encoding = lc $1;
lib/Test/Mojibake.pm view on Meta::CPAN
=head1 DESCRIPTION
Many modern text editors automatically save files using UTF-8 codification, however, L<perl> interpreter does not expects it I<by default>. Whereas this does not represent a big deal on (most) backend-oriented programs, Web framework (L<Catalyst|http...
Even worse: if an editor saves BOM (Byte Order Mark, C<U+FEFF> character in Unicode) at the start of the script with executable bit set (on Unix systems), it won't execute at all, due to shebang corruption.
Avoiding codification problems is quite simple:
=over 4
lib/Test/Mojibake.pm view on Meta::CPAN
Do neither of above when saving as ISO-8859-1;
=item *
B<Never> save BOM (not that it's wrong; just avoid it as you'll barely notice it's presence when in trouble).
=back
However, if you find yourself upgrading old code to use UTF-8 or trying to standardize a big project with many developers each one using a different platform/editor, reviewing all files manually can be quite painful. Specially in cases when some file...
lib/Test/Mojibake.pm view on Meta::CPAN
Actually, L<Test::Mojibake> only cares about UTF-8, as it is roughly safe to be detected. So, when UTF-8 characters are detected without preceding declaration, an error is reported. On the other way, non-UTF-8 characters in UTF-8 mode are wrong, eith...
If present, L<Unicode::CheckUTF8> module (XS wrapper) will be used to validate UTF-8 strings, note that it is B<30 times faster> and a lot more Unicode Consortium compliant than the built-in Pure Perl implementation!
UTF-8 BOM (Byte Order Mark) is also detected as an error. While Perl is OK handling BOM, your OS probably isn't. Check out:
./bom.pl: line 1: $'\357\273\277#!/usr/bin/perl': command not found
=head2 Caveats
Test-Perl-Dist
view release on metacpan or search on metacpan
inc/inc_Module-Build/Module/Build/YAML.pm view on Meta::CPAN
return $self->_error("Did not provide a string to load");
}
# Byte order marks
# NOTE: Keeping this here to educate maintainers
# my %BOM = (
# "\357\273\277" => 'UTF-8',
# "\376\377" => 'UTF-16BE',
# "\377\376" => 'UTF-16LE',
# "\377\376\0\0" => 'UTF-32LE'
# "\0\0\376\377" => 'UTF-32BE',
# );
if ( $string =~ /^(?:\376\377|\377\376|\377\376\0\0|\0\0\376\377)/ ) {
return $self->_error("Stream has a non UTF-8 BOM");
} else {
# Strip UTF-8 bom if found, we'll just ignore it
$string =~ s/^\357\273\277//;
}
Test-Pod-Snippets
view release on metacpan or search on metacpan
t/000-report-versions.t view on Meta::CPAN
return $self->_error("Did not provide a string to load");
}
# Byte order marks
# NOTE: Keeping this here to educate maintainers
# my %BOM = (
# "\357\273\277" => 'UTF-8',
# "\376\377" => 'UTF-16BE',
# "\377\376" => 'UTF-16LE',
# "\377\376\0\0" => 'UTF-32LE'
# "\0\0\376\377" => 'UTF-32BE',
# );
if ( $string =~ /^(?:\376\377|\377\376|\377\376\0\0|\0\0\376\377)/ ) {
return $self->_error("Stream has a non UTF-8 BOM");
} else {
# Strip UTF-8 bom if found, we'll just ignore it
$string =~ s/^\357\273\277//;
}
Test-Smoke
view release on metacpan or search on metacpan
t/logs/rtc-126010/smokecurrent.log view on Meta::CPAN
[2018-08-13 08:08:21-0400] [manicheck] Matched cpan/Module-Metadata/t/encoding.t
[2018-08-13 08:08:21-0400] [manicheck] Matched cpan/Module-Metadata/t/lib/ENDPOD.pm
[2018-08-13 08:08:21-0400] [manicheck] Matched cpan/Module-Metadata/t/lib/GeneratePackage.pm
[2018-08-13 08:08:21-0400] [manicheck] Matched cpan/Module-Metadata/t/lib/0_1/Foo.pm
[2018-08-13 08:08:21-0400] [manicheck] Matched cpan/Module-Metadata/t/lib/0_2/Foo.pm
[2018-08-13 08:08:21-0400] [manicheck] Matched cpan/Module-Metadata/corpus/BOMTest/UTF16BE.pm
[2018-08-13 08:08:21-0400] [manicheck] Matched cpan/Module-Metadata/corpus/BOMTest/UTF16LE.pm
[2018-08-13 08:08:21-0400] [manicheck] Matched cpan/Module-Metadata/corpus/BOMTest/UTF8.pm
[2018-08-13 08:08:21-0400] [manicheck] Skipped cpan/Compress-Raw-Bzip2/.gitignore
[2018-08-13 08:08:21-0400] [manicheck] Matched cpan/Compress-Raw-Bzip2/typemap
[2018-08-13 08:08:21-0400] [manicheck] Matched cpan/Compress-Raw-Bzip2/Bzip2.xs
[2018-08-13 08:08:21-0400] [manicheck] Matched cpan/Compress-Raw-Bzip2/Makefile.PL
[2018-08-13 08:08:21-0400] [manicheck] Matched cpan/Compress-Raw-Bzip2/fallback/constants.h
Test-Timer
view release on metacpan or search on metacpan
cpanfile.snapshot view on Meta::CPAN
PPI::Structure::Unknown 1.236
PPI::Structure::When 1.236
PPI::Token 1.236
PPI::Token::ArrayIndex 1.236
PPI::Token::Attribute 1.236
PPI::Token::BOM 1.236
PPI::Token::Cast 1.236
PPI::Token::Comment 1.236
PPI::Token::DashedWord 1.236
PPI::Token::Data 1.236
PPI::Token::End 1.236
Test-UsedModules
view release on metacpan or search on metacpan
lib/Test/UsedModules/PPIDocument.pm view on Meta::CPAN
my @surplus_tokens = (
'Operator',
'Number',
'Comment',
'Pod',
'BOM',
'Data',
'End',
'Prototype',
'Separator',
'Whitespace'
( run in 1.371 second using v1.01-cache-2.11-cpan-e9daa2b36ef )