openssl/crypto/lhash/num.pl

#!/usr/local/bin/perl

#node     10 ->   4

while (<>)
	{
	next unless /^node/;
	s|\R$||;                # Better chomp
	@a=split;
	$num{$a[3]}++;
	}

@a=sort {$a <=> $b } keys %num;
foreach (0 .. $a[$#a])
	{
	printf "%4d:%4d\n",$_,$num{$_};
	}
Import of old SSLeay release: SSLeay 0.8.1b 1998-12-21 10:52:47 +00:00			`#!/usr/local/bin/perl`

			`#node 10 -> 4`

			`while (<>)`
			`{`
			`next unless /^node/;`
Perl's chop / chomp considered bad, use a regexp instead Once upon a time, there was chop, which somply chopped off the last character of $_ or a given variable, and it was used to take off the EOL character (\n) of strings. ... but then, you had to check for the presence of such character. So came chomp, the better chop which checks for \n before chopping it off. And this worked well, as long as Perl made internally sure that all EOLs were converted to \n. These days, though, there seems to be a mixture of perls, so lines from files in the "wrong" environment might have \r\n as EOL, or just \r (Mac OS, unless I'm misinformed). So it's time we went for the more generic variant and use s\|\R$\|\|, the better chomp which recognises all kinds of known EOLs and chops them off. A few chops were left alone, as they are use as surgical tools to remove one last slash or one last comma. NOTE: \R came with perl 5.10.0. It means that from now on, our scripts will fail with any older version. Reviewed-by: Rich Salz <rsalz@openssl.org> 2016-02-11 20:47:30 +00:00			`s\|\R$\|\|; # Better chomp`
Import of old SSLeay release: SSLeay 0.8.1b 1998-12-21 10:52:47 +00:00			`@a=split;`
			`$num{$a[3]}++;`
			`}`

			`@a=sort {$a <=> $b } keys %num;`
			`foreach (0 .. $a[$#a])`
			`{`
			`printf "%4d:%4d\n",$_,$num{$_};`
			`}`