in reply to Better use of for()
. . . when my teacher stated that you should always avoid the use of <= or >= because using them makes your program do twice the job . . .
Did this teacher of yours happen to know any ASM?
Right out of the Intel Op Codes (external link):
JL == less then JLE == less then or equal
There are similar op codes for > and >=. You'll see similar op codes, often with the same name, in almost any architecture out there. The two pairs of op codes usually take the same ammount of cycles. I see no reason to avoid the use of <= or >=.
----
I wanted to explore how Perl's closures can be manipulated, and ended up creating an object system by accident.
-- Schemer
: () { :|:& };:
Note: All code is untested, unless otherwise stated
|
|---|