my $date = '07/04/2001';
$date = join '/', map int, split /\//, $date;
[download]

 
___crazyinsomniac_______________________________________
Disclaimer: Don't blame. It came from inside the void
perl -e "$q=$_;map({chr unpack qq;H*;,$_}split(q;;,q*H*));print;$q/$q;"

I like it. As long as we're going for shorter *and* clearer, you can simplify the first param to split making it one character shorter and slightly more readable.... especially since it now matches the first param of your join.

$date = join '/', map int, split '/', $date;
[download]

-Blake

Clearer? Depends on the audience.

I would drop a bit of sugar here and there to improve comprehension:

  $date = join( '/', map { int } split( '/', $date ));
[download]

I find my style uses more and more parentheses these days. Parentheses are necessary to stop a list-aware function from swallowing the rest of the list, e.g.:

  my $foo = join( '-', @foo );
  print join( ',' => @bar ), "\n";
[download]

You don't need the parentheses in the first statement, but they are vital in the second statement, otherwise join will gobble the \n and stuff it in @bar.

On grounds of consistency, given that I use join in both these ways, I have decided to always use parentheses with join. Consistency is a Good Thing.

--

g r i n d e r