I say ‘Part 1’ with no intention to write Parts 2, 3… n.
A quick Google search for ‘how many lines of code in WordPress’ came up with squat. I came up with over 350,000:
|
1 2 |
[robert@hermes wordpress]$ a=0; for i in `find . -type f`; do a=$(($a + `wc -l $i | awk '{ print $1 }'`)); done; echo $a; 364304 |
Granted, that includes the readme and license, but given the size of this codebase, there has to be some cruft, right? While I was absentmindedly perusing wp-includes/functions.php the other day I stumbled across this gem:
|
1 2 3 4 5 6 7 8 9 10 11 |
/** * Whether input is yes or no. Must be 'y' to be true. * * @since 1.0.0 * * @param string $yn Character string containing either 'y' or 'n' * @return bool True if yes, false on anything else */ function bool_from_yn( $yn ) { return ( strtolower( $yn ) == 'y' ); } |
So, that’s fun. Turns out, it’s not called anywhere else in the WordPress core. There are a number of functions that aren’t called anywhere else- 18, actually, based on getting every function definition in that file (protip: don’t parse like me):
|
1 |
grep "function " wp-includes/functions.php | grep -v "*" | grep -v "\$function" | cut -d "(" -f 1 | cut -d ' ' -f 2 >> out |
… and hashing that out in Perl:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 |
#! /usr/bin/perl use strict; use warnings; my $emptyline = 0; my $function = ''; my @files = (); my %listings = (); open( FILE, '<out' ); while( <FILE> ) { chomp $_; if ( /^\s*$/ ) { $listings{ $function }{ 'occurrences' } = scalar( @files ); $listings{ $function }{ 'files' } = [ @files ] ; $function = ''; @files = (); $emptyline = 0; next; } if ( $emptyline == 0 ) { $function = $_; $emptyline = 1; } else { push( @files, $_ ); } } my $i = 0; foreach my $k ( keys ( %listings ) ) { if ( $listings{ $k }{ 'occurrences' } == 1 ) { print $k, "\n", join( "\n", @{ $listings{ $k }{ 'files' } } ), "\n\n"; ++$i; } } print $i; |
I also found another ancient function that mimics http_build_query() (guess what it’s called- hint: PHP developers love underscores), yet based on WP Trac won’t be removed until WordPress requires PHP 5.4 (which I would hazard a guess will come with WordPress 5.0). So, yay for cruft!
Also, I’d like to point out that WordPress’s use of portable hashes with the PHPass framework is really frustrating- mostly because their implementation of MD5 hash stretching uses binary output that’s difficult to recreate in JS (more on that in a later post). Andrew Moore does a great job of explaining how portable PHPass hashes are generated, and while there was a conversation last year about how WordPress should handle its PHPass implementation, it never seemed to go anywhere (shame, since that would actually have solved my problem- again, I’ll get there next week).