My approach was slightly different. Since "
The first array always looks the same (ascending numbers from $x to $x + $y)", I decided to ignore the first array completely and just focus on what's wrong in the second. Here's my code:
#!/usr/bin/perl
use strict;
use warnings;
my @array = (1,2,3,6,4,5,7,8,9);
# UPDATED again, numeric sort
my $smallest = (sort {$a <=> $b} @array)[0];
my $stored = shift @array;
# UPDATED per bug report in reply
# if ($stored != $smallest) {
if ($stored != $smallest && $stored + 1 != $array[0]) {
print "$stored appears to be in the wrong position\n";
exit;
}
foreach my $i (0 .. $#array) {
if ($stored != $array[$i] - 1) {
if ($array[$i] + 1 != $array[$i + 1]) {
print "$array[$i] appears to be in the wrong position\n";
last;
}
}
$stored = $array[$i];
}
---
It's all fine and dandy until someone has to look at the code.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.