Indeed. Writing your own is more typing, and it's slower as well. About the only reason I can think of is wanting to avoid the loading of POSIX. But if that's significant, you probably want to inline your ceiling functionality anyway.
#!/usr/bin/perl
use strict;
use warnings;
use POSIX 'ceil';
use Benchmark 'cmpthese';
sub my_ceil {
my $n = shift;
int($n) + ($n > int($n))
}
our @tries = map {-100 + rand 50} 1 .. 1_000;
cmpthese -1, {
ceil => '@a = map { ceil($_)} @tries',
own => '@b = map {my_ceil($_)} @tries',
inline => '@c = map {int($_) + ($_ > int($_))} @tries',
};
__END__
Rate own ceil inline
own 355/s -- -52% -54%
ceil 737/s 107% -- -4%
inline 767/s 116% 4% --
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.