> whereas this version would need to change to ... <= 0

IMHO for a multiplying approach that's the best check, even for the <=> version.

Simply changing to ... < 0 would check for the open interval excluding the endpoints. And ... == 0 for endpoints only.

But half-open intervals like [$a,$b[ can't be covered with this approach.

So I'd rather stick with

• $a <= $x and $x < $b

or the newer chained version

• $a <= $x < $b

and make sure the endpoints are previously swapped if necessary

• ($a,$b) = ($b,$a) if $b < $a;

update

and swapping can be made non-destructive by localizing it to a scope.

C:\tmp\e>perl
($a,$b) = (7,3);
my $x=5;
my $inside = do {
    local ($a,$b) = ($b,$a) if $b < $a;
    $a <= $x < $b ;
};
print "$x in [$a, $b]? $inside";
__END__
5 in [7, 3]? 1
C:\tmp\e>
[download]

(replace local with my for private vars)

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.