I didn't like any of the solutions so far since none of them handle input in the same format as their own output.

#!/usr/bin/perl -w use strict; sub RunLengthEncode { my @out; while( @_ ) { my $next= shift; if( ! ref($next) ) { $next= {count=>1,value=>$next}; } if( @out && $out[$#out]{value} eq $next->{value} ) { $out[$#out]{count} += $next->{count}; } else { push @out, $next; } } return @out; } for( @ARGV ) { print join ",", map { $_->{count}."*".$_->{value} } RunLengthEncode( split /,/, $_ ); print $/; }

But that doesn't define a bunch of rules for "reducing" a problem because, well, it wasn't written in Prolog. (:

        - tye (but my friends call me "Tye")

In reply to Re: PPGA - Prolog-Perl Golf Association: Run-length encoding by tye
in thread PPGA - Prolog-Perl Golf Association: Run-length encoding by princepawn

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.