Ok, here is the index-based algorithm: 

use strict;
use warnings;

sub first_idx {
    my( $N, $M ) = @_;
    return ( $N-$M .. $N-1 );
}

sub next_idx {
    my( $N, $M, @idx ) = @_;
    return () if $idx[ -1 ] == $M-1;
    my $i = $M-1;
    $i-- while $i>0 and $idx[$i]-$idx[$i-1]==1;
    return ( @idx[0..$i-1], $idx[ $i ]-1, 
         map { $idx[ $i ] + $N - $idx[ $M - $_+ $i ] } $i+1 .. $M-1);
}

my $N = 5;
my $M = 3;
my @indices = first_idx( $N, $M );
1 while print( "@indices\n"), @indices = next_idx( $N, $M, @indices );

[download]

In reply to Re^5: Odometer pattern iterator (in C). by hdb
in thread Odometer pattern iterator (in C). (Updated.) by BrowserUk

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.