Source code of Windows XP (NT5)
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

1676 lines
53 KiB

  1. =head1 NAME
  2. perlfaq4 - Data Manipulation ($Revision: 1.40 $, $Date: 1999/01/08 04:26:39 $)
  3. =head1 DESCRIPTION
  4. The section of the FAQ answers question related to the manipulation
  5. of data as numbers, dates, strings, arrays, hashes, and miscellaneous
  6. data issues.
  7. =head1 Data: Numbers
  8. =head2 Why am I getting long decimals (eg, 19.9499999999999) instead of the numbers I should be getting (eg, 19.95)?
  9. The infinite set that a mathematician thinks of as the real numbers can
  10. only be approximate on a computer, since the computer only has a finite
  11. number of bits to store an infinite number of, um, numbers.
  12. Internally, your computer represents floating-point numbers in binary.
  13. Floating-point numbers read in from a file or appearing as literals
  14. in your program are converted from their decimal floating-point
  15. representation (eg, 19.95) to the internal binary representation.
  16. However, 19.95 can't be precisely represented as a binary
  17. floating-point number, just like 1/3 can't be exactly represented as a
  18. decimal floating-point number. The computer's binary representation
  19. of 19.95, therefore, isn't exactly 19.95.
  20. When a floating-point number gets printed, the binary floating-point
  21. representation is converted back to decimal. These decimal numbers
  22. are displayed in either the format you specify with printf(), or the
  23. current output format for numbers (see L<perlvar/"$#"> if you use
  24. print. C<$#> has a different default value in Perl5 than it did in
  25. Perl4. Changing C<$#> yourself is deprecated.
  26. This affects B<all> computer languages that represent decimal
  27. floating-point numbers in binary, not just Perl. Perl provides
  28. arbitrary-precision decimal numbers with the Math::BigFloat module
  29. (part of the standard Perl distribution), but mathematical operations
  30. are consequently slower.
  31. To get rid of the superfluous digits, just use a format (eg,
  32. C<printf("%.2f", 19.95)>) to get the required precision.
  33. See L<perlop/"Floating-point Arithmetic">.
  34. =head2 Why isn't my octal data interpreted correctly?
  35. Perl only understands octal and hex numbers as such when they occur
  36. as literals in your program. If they are read in from somewhere and
  37. assigned, no automatic conversion takes place. You must explicitly
  38. use oct() or hex() if you want the values converted. oct() interprets
  39. both hex ("0x350") numbers and octal ones ("0350" or even without the
  40. leading "0", like "377"), while hex() only converts hexadecimal ones,
  41. with or without a leading "0x", like "0x255", "3A", "ff", or "deadbeef".
  42. This problem shows up most often when people try using chmod(), mkdir(),
  43. umask(), or sysopen(), which all want permissions in octal.
  44. chmod(644, $file); # WRONG -- perl -w catches this
  45. chmod(0644, $file); # right
  46. =head2 Does Perl have a round() function? What about ceil() and floor()? Trig functions?
  47. Remember that int() merely truncates toward 0. For rounding to a
  48. certain number of digits, sprintf() or printf() is usually the easiest
  49. route.
  50. printf("%.3f", 3.1415926535); # prints 3.142
  51. The POSIX module (part of the standard perl distribution) implements
  52. ceil(), floor(), and a number of other mathematical and trigonometric
  53. functions.
  54. use POSIX;
  55. $ceil = ceil(3.5); # 4
  56. $floor = floor(3.5); # 3
  57. In 5.000 to 5.003 Perls, trigonometry was done in the Math::Complex
  58. module. With 5.004, the Math::Trig module (part of the standard perl
  59. distribution) implements the trigonometric functions. Internally it
  60. uses the Math::Complex module and some functions can break out from
  61. the real axis into the complex plane, for example the inverse sine of
  62. 2.
  63. Rounding in financial applications can have serious implications, and
  64. the rounding method used should be specified precisely. In these
  65. cases, it probably pays not to trust whichever system rounding is
  66. being used by Perl, but to instead implement the rounding function you
  67. need yourself.
  68. To see why, notice how you'll still have an issue on half-way-point
  69. alternation:
  70. for ($i = 0; $i < 1.01; $i += 0.05) { printf "%.1f ",$i}
  71. 0.0 0.1 0.1 0.2 0.2 0.2 0.3 0.3 0.4 0.4 0.5 0.5 0.6 0.7 0.7
  72. 0.8 0.8 0.9 0.9 1.0 1.0
  73. Don't blame Perl. It's the same as in C. IEEE says we have to do this.
  74. Perl numbers whose absolute values are integers under 2**31 (on 32 bit
  75. machines) will work pretty much like mathematical integers. Other numbers
  76. are not guaranteed.
  77. =head2 How do I convert bits into ints?
  78. To turn a string of 1s and 0s like C<10110110> into a scalar containing
  79. its binary value, use the pack() function (documented in
  80. L<perlfunc/"pack">):
  81. $decimal = pack('B8', '10110110');
  82. Here's an example of going the other way:
  83. $binary_string = join('', unpack('B*', "\x29"));
  84. =head2 Why doesn't & work the way I want it to?
  85. The behavior of binary arithmetic operators depends on whether they're
  86. used on numbers or strings. The operators treat a string as a series
  87. of bits and work with that (the string C<"3"> is the bit pattern
  88. C<00110011>). The operators work with the binary form of a number
  89. (the number C<3> is treated as the bit pattern C<00000011>).
  90. So, saying C<11 & 3> performs the "and" operation on numbers (yielding
  91. C<1>). Saying C<"11" & "3"> performs the "and" operation on strings
  92. (yielding C<"1">).
  93. Most problems with C<&> and C<|> arise because the programmer thinks
  94. they have a number but really it's a string. The rest arise because
  95. the programmer says:
  96. if ("\020\020" & "\101\101") {
  97. # ...
  98. }
  99. but a string consisting of two null bytes (the result of C<"\020\020"
  100. & "\101\101">) is not a false value in Perl. You need:
  101. if ( ("\020\020" & "\101\101") !~ /[^\000]/) {
  102. # ...
  103. }
  104. =head2 How do I multiply matrices?
  105. Use the Math::Matrix or Math::MatrixReal modules (available from CPAN)
  106. or the PDL extension (also available from CPAN).
  107. =head2 How do I perform an operation on a series of integers?
  108. To call a function on each element in an array, and collect the
  109. results, use:
  110. @results = map { my_func($_) } @array;
  111. For example:
  112. @triple = map { 3 * $_ } @single;
  113. To call a function on each element of an array, but ignore the
  114. results:
  115. foreach $iterator (@array) {
  116. some_func($iterator);
  117. }
  118. To call a function on each integer in a (small) range, you B<can> use:
  119. @results = map { some_func($_) } (5 .. 25);
  120. but you should be aware that the C<..> operator creates an array of
  121. all integers in the range. This can take a lot of memory for large
  122. ranges. Instead use:
  123. @results = ();
  124. for ($i=5; $i < 500_005; $i++) {
  125. push(@results, some_func($i));
  126. }
  127. =head2 How can I output Roman numerals?
  128. Get the http://www.perl.com/CPAN/modules/by-module/Roman module.
  129. =head2 Why aren't my random numbers random?
  130. If you're using a version of Perl before 5.004, you must call C<srand>
  131. once at the start of your program to seed the random number generator.
  132. 5.004 and later automatically call C<srand> at the beginning. Don't
  133. call C<srand> more than once--you make your numbers less random, rather
  134. than more.
  135. Computers are good at being predictable and bad at being random
  136. (despite appearances caused by bugs in your programs :-).
  137. http://www.perl.com/CPAN/doc/FMTEYEWTK/random, courtesy of Tom
  138. Phoenix, talks more about this.. John von Neumann said, ``Anyone who
  139. attempts to generate random numbers by deterministic means is, of
  140. course, living in a state of sin.''
  141. If you want numbers that are more random than C<rand> with C<srand>
  142. provides, you should also check out the Math::TrulyRandom module from
  143. CPAN. It uses the imperfections in your system's timer to generate
  144. random numbers, but this takes quite a while. If you want a better
  145. pseudorandom generator than comes with your operating system, look at
  146. ``Numerical Recipes in C'' at http://www.nr.com/ .
  147. =head1 Data: Dates
  148. =head2 How do I find the week-of-the-year/day-of-the-year?
  149. The day of the year is in the array returned by localtime() (see
  150. L<perlfunc/"localtime">):
  151. $day_of_year = (localtime(time()))[7];
  152. or more legibly (in 5.004 or higher):
  153. use Time::localtime;
  154. $day_of_year = localtime(time())->yday;
  155. You can find the week of the year by dividing this by 7:
  156. $week_of_year = int($day_of_year / 7);
  157. Of course, this believes that weeks start at zero. The Date::Calc
  158. module from CPAN has a lot of date calculation functions, including
  159. day of the year, week of the year, and so on. Note that not
  160. all businesses consider ``week 1'' to be the same; for example,
  161. American businesses often consider the first week with a Monday
  162. in it to be Work Week #1, despite ISO 8601, which considers
  163. WW1 to be the first week with a Thursday in it.
  164. =head2 How can I compare two dates and find the difference?
  165. If you're storing your dates as epoch seconds then simply subtract one
  166. from the other. If you've got a structured date (distinct year, day,
  167. month, hour, minute, seconds values) then use one of the Date::Manip
  168. and Date::Calc modules from CPAN.
  169. =head2 How can I take a string and turn it into epoch seconds?
  170. If it's a regular enough string that it always has the same format,
  171. you can split it up and pass the parts to C<timelocal> in the standard
  172. Time::Local module. Otherwise, you should look into the Date::Calc
  173. and Date::Manip modules from CPAN.
  174. =head2 How can I find the Julian Day?
  175. Neither Date::Manip nor Date::Calc deal with Julian days. Instead,
  176. there is an example of Julian date calculation that should help you in
  177. Time::JulianDay (part of the Time-modules bundle) which can be found at
  178. http://www.perl.com/CPAN/modules/by-module/Time/.
  179. =head2 How do I find yesterday's date?
  180. The C<time()> function returns the current time in seconds since the
  181. epoch. Take one day off that:
  182. $yesterday = time() - ( 24 * 60 * 60 );
  183. Then you can pass this to C<localtime()> and get the individual year,
  184. month, day, hour, minute, seconds values.
  185. =head2 Does Perl have a year 2000 problem? Is Perl Y2K compliant?
  186. Short answer: No, Perl does not have a Year 2000 problem. Yes, Perl is
  187. Y2K compliant (whatever that means). The programmers you've hired to
  188. use it, however, probably are not.
  189. Long answer: The question belies a true understanding of the issue.
  190. Perl is just as Y2K compliant as your pencil--no more, and no less.
  191. Can you use your pencil to write a non-Y2K-compliant memo? Of course
  192. you can. Is that the pencil's fault? Of course it isn't.
  193. The date and time functions supplied with perl (gmtime and localtime)
  194. supply adequate information to determine the year well beyond 2000
  195. (2038 is when trouble strikes for 32-bit machines). The year returned
  196. by these functions when used in an array context is the year minus 1900.
  197. For years between 1910 and 1999 this I<happens> to be a 2-digit decimal
  198. number. To avoid the year 2000 problem simply do not treat the year as
  199. a 2-digit number. It isn't.
  200. When gmtime() and localtime() are used in scalar context they return
  201. a timestamp string that contains a fully-expanded year. For example,
  202. C<$timestamp = gmtime(1005613200)> sets $timestamp to "Tue Nov 13 01:00:00
  203. 2001". There's no year 2000 problem here.
  204. That doesn't mean that Perl can't be used to create non-Y2K compliant
  205. programs. It can. But so can your pencil. It's the fault of the user,
  206. not the language. At the risk of inflaming the NRA: ``Perl doesn't
  207. break Y2K, people do.'' See http://language.perl.com/news/y2k.html for
  208. a longer exposition.
  209. =head1 Data: Strings
  210. =head2 How do I validate input?
  211. The answer to this question is usually a regular expression, perhaps
  212. with auxiliary logic. See the more specific questions (numbers, mail
  213. addresses, etc.) for details.
  214. =head2 How do I unescape a string?
  215. It depends just what you mean by ``escape''. URL escapes are dealt
  216. with in L<perlfaq9>. Shell escapes with the backslash (C<\>)
  217. character are removed with:
  218. s/\\(.)/$1/g;
  219. This won't expand C<"\n"> or C<"\t"> or any other special escapes.
  220. =head2 How do I remove consecutive pairs of characters?
  221. To turn C<"abbcccd"> into C<"abccd">:
  222. s/(.)\1/$1/g;
  223. =head2 How do I expand function calls in a string?
  224. This is documented in L<perlref>. In general, this is fraught with
  225. quoting and readability problems, but it is possible. To interpolate
  226. a subroutine call (in list context) into a string:
  227. print "My sub returned @{[mysub(1,2,3)]} that time.\n";
  228. If you prefer scalar context, similar chicanery is also useful for
  229. arbitrary expressions:
  230. print "That yields ${\($n + 5)} widgets\n";
  231. Version 5.004 of Perl had a bug that gave list context to the
  232. expression in C<${...}>, but this is fixed in version 5.005.
  233. See also ``How can I expand variables in text strings?'' in this
  234. section of the FAQ.
  235. =head2 How do I find matching/nesting anything?
  236. This isn't something that can be done in one regular expression, no
  237. matter how complicated. To find something between two single
  238. characters, a pattern like C</x([^x]*)x/> will get the intervening
  239. bits in $1. For multiple ones, then something more like
  240. C</alpha(.*?)omega/> would be needed. But none of these deals with
  241. nested patterns, nor can they. For that you'll have to write a
  242. parser.
  243. If you are serious about writing a parser, there are a number of
  244. modules or oddities that will make your life a lot easier. There is
  245. the CPAN module Parse::RecDescent, the standard module Text::Balanced,
  246. the byacc program, the CPAN module Parse::Yapp, and Mark-Jason
  247. Dominus's excellent I<py> tool at http://www.plover.com/~mjd/perl/py/
  248. .
  249. One simple destructive, inside-out approach that you might try is to
  250. pull out the smallest nesting parts one at a time:
  251. while (s//BEGIN((?:(?!BEGIN)(?!END).)*)END/gs) {
  252. # do something with $1
  253. }
  254. A more complicated and sneaky approach is to make Perl's regular
  255. expression engine do it for you. This is courtesy Dean Inada, and
  256. rather has the nature of an Obfuscated Perl Contest entry, but it
  257. really does work:
  258. # $_ contains the string to parse
  259. # BEGIN and END are the opening and closing markers for the
  260. # nested text.
  261. @( = ('(','');
  262. @) = (')','');
  263. ($re=$_)=~s/((BEGIN)|(END)|.)/$)[!$3]\Q$1\E$([!$2]/gs;
  264. @$ = (eval{/$re/},$@!~/unmatched/);
  265. print join("\n",@$[0..$#$]) if( $$[-1] );
  266. =head2 How do I reverse a string?
  267. Use reverse() in scalar context, as documented in
  268. L<perlfunc/reverse>.
  269. $reversed = reverse $string;
  270. =head2 How do I expand tabs in a string?
  271. You can do it yourself:
  272. 1 while $string =~ s/\t+/' ' x (length($&) * 8 - length($`) % 8)/e;
  273. Or you can just use the Text::Tabs module (part of the standard perl
  274. distribution).
  275. use Text::Tabs;
  276. @expanded_lines = expand(@lines_with_tabs);
  277. =head2 How do I reformat a paragraph?
  278. Use Text::Wrap (part of the standard perl distribution):
  279. use Text::Wrap;
  280. print wrap("\t", ' ', @paragraphs);
  281. The paragraphs you give to Text::Wrap should not contain embedded
  282. newlines. Text::Wrap doesn't justify the lines (flush-right).
  283. =head2 How can I access/change the first N letters of a string?
  284. There are many ways. If you just want to grab a copy, use
  285. substr():
  286. $first_byte = substr($a, 0, 1);
  287. If you want to modify part of a string, the simplest way is often to
  288. use substr() as an lvalue:
  289. substr($a, 0, 3) = "Tom";
  290. Although those with a pattern matching kind of thought process will
  291. likely prefer:
  292. $a =~ s/^.../Tom/;
  293. =head2 How do I change the Nth occurrence of something?
  294. You have to keep track of N yourself. For example, let's say you want
  295. to change the fifth occurrence of C<"whoever"> or C<"whomever"> into
  296. C<"whosoever"> or C<"whomsoever">, case insensitively.
  297. $count = 0;
  298. s{((whom?)ever)}{
  299. ++$count == 5 # is it the 5th?
  300. ? "${2}soever" # yes, swap
  301. : $1 # renege and leave it there
  302. }igex;
  303. In the more general case, you can use the C</g> modifier in a C<while>
  304. loop, keeping count of matches.
  305. $WANT = 3;
  306. $count = 0;
  307. while (/(\w+)\s+fish\b/gi) {
  308. if (++$count == $WANT) {
  309. print "The third fish is a $1 one.\n";
  310. # Warning: don't `last' out of this loop
  311. }
  312. }
  313. That prints out: C<"The third fish is a red one."> You can also use a
  314. repetition count and repeated pattern like this:
  315. /(?:\w+\s+fish\s+){2}(\w+)\s+fish/i;
  316. =head2 How can I count the number of occurrences of a substring within a string?
  317. There are a number of ways, with varying efficiency: If you want a
  318. count of a certain single character (X) within a string, you can use the
  319. C<tr///> function like so:
  320. $string = "ThisXlineXhasXsomeXx'sXinXit";
  321. $count = ($string =~ tr/X//);
  322. print "There are $count X charcters in the string";
  323. This is fine if you are just looking for a single character. However,
  324. if you are trying to count multiple character substrings within a
  325. larger string, C<tr///> won't work. What you can do is wrap a while()
  326. loop around a global pattern match. For example, let's count negative
  327. integers:
  328. $string = "-9 55 48 -2 23 -76 4 14 -44";
  329. while ($string =~ /-\d+/g) { $count++ }
  330. print "There are $count negative numbers in the string";
  331. =head2 How do I capitalize all the words on one line?
  332. To make the first letter of each word upper case:
  333. $line =~ s/\b(\w)/\U$1/g;
  334. This has the strange effect of turning "C<don't do it>" into "C<Don'T
  335. Do It>". Sometimes you might want this, instead (Suggested by Brian
  336. Foy):
  337. $string =~ s/ (
  338. (^\w) #at the beginning of the line
  339. | # or
  340. (\s\w) #preceded by whitespace
  341. )
  342. /\U$1/xg;
  343. $string =~ /([\w']+)/\u\L$1/g;
  344. To make the whole line upper case:
  345. $line = uc($line);
  346. To force each word to be lower case, with the first letter upper case:
  347. $line =~ s/(\w+)/\u\L$1/g;
  348. You can (and probably should) enable locale awareness of those
  349. characters by placing a C<use locale> pragma in your program.
  350. See L<perllocale> for endless details on locales.
  351. This is sometimes referred to as putting something into "title
  352. case", but that's not quite accurate. Consdier the proper
  353. capitalization of the movie I<Dr. Strangelove or: How I Learned to
  354. Stop Worrying and Love the Bomb>, for example.
  355. =head2 How can I split a [character] delimited string except when inside
  356. [character]? (Comma-separated files)
  357. Take the example case of trying to split a string that is comma-separated
  358. into its different fields. (We'll pretend you said comma-separated, not
  359. comma-delimited, which is different and almost never what you mean.) You
  360. can't use C<split(/,/)> because you shouldn't split if the comma is inside
  361. quotes. For example, take a data line like this:
  362. SAR001,"","Cimetrix, Inc","Bob Smith","CAM",N,8,1,0,7,"Error, Core Dumped"
  363. Due to the restriction of the quotes, this is a fairly complex
  364. problem. Thankfully, we have Jeffrey Friedl, author of a highly
  365. recommended book on regular expressions, to handle these for us. He
  366. suggests (assuming your string is contained in $text):
  367. @new = ();
  368. push(@new, $+) while $text =~ m{
  369. "([^\"\\]*(?:\\.[^\"\\]*)*)",? # groups the phrase inside the quotes
  370. | ([^,]+),?
  371. | ,
  372. }gx;
  373. push(@new, undef) if substr($text,-1,1) eq ',';
  374. If you want to represent quotation marks inside a
  375. quotation-mark-delimited field, escape them with backslashes (eg,
  376. C<"like \"this\"">. Unescaping them is a task addressed earlier in
  377. this section.
  378. Alternatively, the Text::ParseWords module (part of the standard perl
  379. distribution) lets you say:
  380. use Text::ParseWords;
  381. @new = quotewords(",", 0, $text);
  382. There's also a Text::CSV module on CPAN.
  383. =head2 How do I strip blank space from the beginning/end of a string?
  384. Although the simplest approach would seem to be:
  385. $string =~ s/^\s*(.*?)\s*$/$1/;
  386. This is unnecessarily slow, destructive, and fails with embedded newlines.
  387. It is much better faster to do this in two steps:
  388. $string =~ s/^\s+//;
  389. $string =~ s/\s+$//;
  390. Or more nicely written as:
  391. for ($string) {
  392. s/^\s+//;
  393. s/\s+$//;
  394. }
  395. This idiom takes advantage of the C<foreach> loop's aliasing
  396. behavior to factor out common code. You can do this
  397. on several strings at once, or arrays, or even the
  398. values of a hash if you use a slide:
  399. # trim whitespace in the scalar, the array,
  400. # and all the values in the hash
  401. foreach ($scalar, @array, @hash{keys %hash}) {
  402. s/^\s+//;
  403. s/\s+$//;
  404. }
  405. =head2 How do I pad a string with blanks or pad a number with zeroes?
  406. (This answer contributed by Uri Guttman)
  407. In the following examples, C<$pad_len> is the length to which you wish
  408. to pad the string, C<$text> or C<$num> contains the string to be
  409. padded, and C<$pad_char> contains the padding character. You can use a
  410. single character string constant instead of the C<$pad_char> variable
  411. if you know what it is in advance.
  412. The simplest method use the C<sprintf> function. It can pad on the
  413. left or right with blanks and on the left with zeroes.
  414. # Left padding with blank:
  415. $padded = sprintf( "%${pad_len}s", $text ) ;
  416. # Right padding with blank:
  417. $padded = sprintf( "%${pad_len}s", $text ) ;
  418. # Left padding with 0:
  419. $padded = sprintf( "%0${pad_len}d", $num ) ;
  420. If you need to pad with a character other than blank or zero you can use
  421. one of the following methods.
  422. These methods generate a pad string with the C<x> operator and
  423. concatenate that with the original text.
  424. Left and right padding with any character:
  425. $padded = $pad_char x ( $pad_len - length( $text ) ) . $text ;
  426. $padded = $text . $pad_char x ( $pad_len - length( $text ) ) ;
  427. Or you can left or right pad $text directly:
  428. $text .= $pad_char x ( $pad_len - length( $text ) ) ;
  429. substr( $text, 0, 0 ) = $pad_char x ( $pad_len - length( $text ) ) ;
  430. =head2 How do I extract selected columns from a string?
  431. Use substr() or unpack(), both documented in L<perlfunc>.
  432. If you prefer thinking in terms of columns instead of widths,
  433. you can use this kind of thing:
  434. # determine the unpack format needed to split Linux ps output
  435. # arguments are cut columns
  436. my $fmt = cut2fmt(8, 14, 20, 26, 30, 34, 41, 47, 59, 63, 67, 72);
  437. sub cut2fmt {
  438. my(@positions) = @_;
  439. my $template = '';
  440. my $lastpos = 1;
  441. for my $place (@positions) {
  442. $template .= "A" . ($place - $lastpos) . " ";
  443. $lastpos = $place;
  444. }
  445. $template .= "A*";
  446. return $template;
  447. }
  448. =head2 How do I find the soundex value of a string?
  449. Use the standard Text::Soundex module distributed with perl.
  450. =head2 How can I expand variables in text strings?
  451. Let's assume that you have a string like:
  452. $text = 'this has a $foo in it and a $bar';
  453. If those were both global variables, then this would
  454. suffice:
  455. $text =~ s/\$(\w+)/${$1}/g; # no /e needed
  456. But since they are probably lexicals, or at least, they could
  457. be, you'd have to do this:
  458. $text =~ s/(\$\w+)/$1/eeg;
  459. die if $@; # needed /ee, not /e
  460. It's probably better in the general case to treat those
  461. variables as entries in some special hash. For example:
  462. %user_defs = (
  463. foo => 23,
  464. bar => 19,
  465. );
  466. $text =~ s/\$(\w+)/$user_defs{$1}/g;
  467. See also ``How do I expand function calls in a string?'' in this section
  468. of the FAQ.
  469. =head2 What's wrong with always quoting "$vars"?
  470. The problem is that those double-quotes force stringification,
  471. coercing numbers and references into strings, even when you
  472. don't want them to be. Think of it this way: double-quote
  473. expansion is used to produce new strings. If you already
  474. have a string, why do you need more?
  475. If you get used to writing odd things like these:
  476. print "$var"; # BAD
  477. $new = "$old"; # BAD
  478. somefunc("$var"); # BAD
  479. You'll be in trouble. Those should (in 99.8% of the cases) be
  480. the simpler and more direct:
  481. print $var;
  482. $new = $old;
  483. somefunc($var);
  484. Otherwise, besides slowing you down, you're going to break code when
  485. the thing in the scalar is actually neither a string nor a number, but
  486. a reference:
  487. func(\@array);
  488. sub func {
  489. my $aref = shift;
  490. my $oref = "$aref"; # WRONG
  491. }
  492. You can also get into subtle problems on those few operations in Perl
  493. that actually do care about the difference between a string and a
  494. number, such as the magical C<++> autoincrement operator or the
  495. syscall() function.
  496. Stringification also destroys arrays.
  497. @lines = `command`;
  498. print "@lines"; # WRONG - extra blanks
  499. print @lines; # right
  500. =head2 Why don't my E<lt>E<lt>HERE documents work?
  501. Check for these three things:
  502. =over 4
  503. =item 1. There must be no space after the << part.
  504. =item 2. There (probably) should be a semicolon at the end.
  505. =item 3. You can't (easily) have any space in front of the tag.
  506. =back
  507. If you want to indent the text in the here document, you
  508. can do this:
  509. # all in one
  510. ($VAR = <<HERE_TARGET) =~ s/^\s+//gm;
  511. your text
  512. goes here
  513. HERE_TARGET
  514. But the HERE_TARGET must still be flush against the margin.
  515. If you want that indented also, you'll have to quote
  516. in the indentation.
  517. ($quote = <<' FINIS') =~ s/^\s+//gm;
  518. ...we will have peace, when you and all your works have
  519. perished--and the works of your dark master to whom you
  520. would deliver us. You are a liar, Saruman, and a corrupter
  521. of men's hearts. --Theoden in /usr/src/perl/taint.c
  522. FINIS
  523. $quote =~ s/\s*--/\n--/;
  524. A nice general-purpose fixer-upper function for indented here documents
  525. follows. It expects to be called with a here document as its argument.
  526. It looks to see whether each line begins with a common substring, and
  527. if so, strips that off. Otherwise, it takes the amount of leading
  528. white space found on the first line and removes that much off each
  529. subsequent line.
  530. sub fix {
  531. local $_ = shift;
  532. my ($white, $leader); # common white space and common leading string
  533. if (/^\s*(?:([^\w\s]+)(\s*).*\n)(?:\s*\1\2?.*\n)+$/) {
  534. ($white, $leader) = ($2, quotemeta($1));
  535. } else {
  536. ($white, $leader) = (/^(\s+)/, '');
  537. }
  538. s/^\s*?$leader(?:$white)?//gm;
  539. return $_;
  540. }
  541. This works with leading special strings, dynamically determined:
  542. $remember_the_main = fix<<' MAIN_INTERPRETER_LOOP';
  543. @@@ int
  544. @@@ runops() {
  545. @@@ SAVEI32(runlevel);
  546. @@@ runlevel++;
  547. @@@ while ( op = (*op->op_ppaddr)() ) ;
  548. @@@ TAINT_NOT;
  549. @@@ return 0;
  550. @@@ }
  551. MAIN_INTERPRETER_LOOP
  552. Or with a fixed amount of leading white space, with remaining
  553. indentation correctly preserved:
  554. $poem = fix<<EVER_ON_AND_ON;
  555. Now far ahead the Road has gone,
  556. And I must follow, if I can,
  557. Pursuing it with eager feet,
  558. Until it joins some larger way
  559. Where many paths and errands meet.
  560. And whither then? I cannot say.
  561. --Bilbo in /usr/src/perl/pp_ctl.c
  562. EVER_ON_AND_ON
  563. =head1 Data: Arrays
  564. =head2 What is the difference between a list and an array?
  565. An array has a changeable length. A list does not. An array is something
  566. you can push or pop, while a list is a set of values. Some people make
  567. the distinction that a list is a value while an array is a variable.
  568. Subroutines are passed and return lists, you put things into list
  569. context, you initialize arrays with lists, and you foreach() across
  570. a list. C<@> variables are arrays, anonymous arrays are arrays, arrays
  571. in scalar context behave like the number of elements in them, subroutines
  572. access their arguments through the array C<@_>, push/pop/shift only work
  573. on arrays.
  574. As a side note, there's no such thing as a list in scalar context.
  575. When you say
  576. $scalar = (2, 5, 7, 9);
  577. you're using the comma operator in scalar context, so it evaluates the
  578. left hand side, then evaluates and returns the left hand side. This
  579. causes the last value to be returned: 9.
  580. =head2 What is the difference between $array[1] and @array[1]?
  581. The former is a scalar value, the latter an array slice, which makes
  582. it a list with one (scalar) value. You should use $ when you want a
  583. scalar value (most of the time) and @ when you want a list with one
  584. scalar value in it (very, very rarely; nearly never, in fact).
  585. Sometimes it doesn't make a difference, but sometimes it does.
  586. For example, compare:
  587. $good[0] = `some program that outputs several lines`;
  588. with
  589. @bad[0] = `same program that outputs several lines`;
  590. The B<-w> flag will warn you about these matters.
  591. =head2 How can I extract just the unique elements of an array?
  592. There are several possible ways, depending on whether the array is
  593. ordered and whether you wish to preserve the ordering.
  594. =over 4
  595. =item a) If @in is sorted, and you want @out to be sorted:
  596. (this assumes all true values in the array)
  597. $prev = 'nonesuch';
  598. @out = grep($_ ne $prev && ($prev = $_), @in);
  599. This is nice in that it doesn't use much extra memory, simulating
  600. uniq(1)'s behavior of removing only adjacent duplicates. It's less
  601. nice in that it won't work with false values like undef, 0, or "";
  602. "0 but true" is ok, though.
  603. =item b) If you don't know whether @in is sorted:
  604. undef %saw;
  605. @out = grep(!$saw{$_}++, @in);
  606. =item c) Like (b), but @in contains only small integers:
  607. @out = grep(!$saw[$_]++, @in);
  608. =item d) A way to do (b) without any loops or greps:
  609. undef %saw;
  610. @saw{@in} = ();
  611. @out = sort keys %saw; # remove sort if undesired
  612. =item e) Like (d), but @in contains only small positive integers:
  613. undef @ary;
  614. @ary[@in] = @in;
  615. @out = @ary;
  616. =back
  617. But perhaps you should have been using a hash all along, eh?
  618. =head2 How can I tell whether a list or array contains a certain element?
  619. Hearing the word "in" is an I<in>dication that you probably should have
  620. used a hash, not a list or array, to store your data. Hashes are
  621. designed to answer this question quickly and efficiently. Arrays aren't.
  622. That being said, there are several ways to approach this. If you
  623. are going to make this query many times over arbitrary string values,
  624. the fastest way is probably to invert the original array and keep an
  625. associative array lying about whose keys are the first array's values.
  626. @blues = qw/azure cerulean teal turquoise lapis-lazuli/;
  627. undef %is_blue;
  628. for (@blues) { $is_blue{$_} = 1 }
  629. Now you can check whether $is_blue{$some_color}. It might have been a
  630. good idea to keep the blues all in a hash in the first place.
  631. If the values are all small integers, you could use a simple indexed
  632. array. This kind of an array will take up less space:
  633. @primes = (2, 3, 5, 7, 11, 13, 17, 19, 23, 29, 31);
  634. undef @is_tiny_prime;
  635. for (@primes) { $is_tiny_prime[$_] = 1; }
  636. Now you check whether $is_tiny_prime[$some_number].
  637. If the values in question are integers instead of strings, you can save
  638. quite a lot of space by using bit strings instead:
  639. @articles = ( 1..10, 150..2000, 2017 );
  640. undef $read;
  641. for (@articles) { vec($read,$_,1) = 1 }
  642. Now check whether C<vec($read,$n,1)> is true for some C<$n>.
  643. Please do not use
  644. $is_there = grep $_ eq $whatever, @array;
  645. or worse yet
  646. $is_there = grep /$whatever/, @array;
  647. These are slow (checks every element even if the first matches),
  648. inefficient (same reason), and potentially buggy (what if there are
  649. regexp characters in $whatever?). If you're only testing once, then
  650. use:
  651. $is_there = 0;
  652. foreach $elt (@array) {
  653. if ($elt eq $elt_to_find) {
  654. $is_there = 1;
  655. last;
  656. }
  657. }
  658. if ($is_there) { ... }
  659. =head2 How do I compute the difference of two arrays? How do I compute the intersection of two arrays?
  660. Use a hash. Here's code to do both and more. It assumes that
  661. each element is unique in a given array:
  662. @union = @intersection = @difference = ();
  663. %count = ();
  664. foreach $element (@array1, @array2) { $count{$element}++ }
  665. foreach $element (keys %count) {
  666. push @union, $element;
  667. push @{ $count{$element} > 1 ? \@intersection : \@difference }, $element;
  668. }
  669. =head2 How do I test whether two arrays or hashes are equal?
  670. The following code works for single-level arrays. It uses a stringwise
  671. comparison, and does not distinguish defined versus undefined empty
  672. strings. Modify if you have other needs.
  673. $are_equal = compare_arrays(\@frogs, \@toads);
  674. sub compare_arrays {
  675. my ($first, $second) = @_;
  676. local $^W = 0; # silence spurious -w undef complaints
  677. return 0 unless @$first == @$second;
  678. for (my $i = 0; $i < @$first; $i++) {
  679. return 0 if $first->[$i] ne $second->[$i];
  680. }
  681. return 1;
  682. }
  683. For multilevel structures, you may wish to use an approach more
  684. like this one. It uses the CPAN module FreezeThaw:
  685. use FreezeThaw qw(cmpStr);
  686. @a = @b = ( "this", "that", [ "more", "stuff" ] );
  687. printf "a and b contain %s arrays\n",
  688. cmpStr(\@a, \@b) == 0
  689. ? "the same"
  690. : "different";
  691. This approach also works for comparing hashes. Here
  692. we'll demonstrate two different answers:
  693. use FreezeThaw qw(cmpStr cmpStrHard);
  694. %a = %b = ( "this" => "that", "extra" => [ "more", "stuff" ] );
  695. $a{EXTRA} = \%b;
  696. $b{EXTRA} = \%a;
  697. printf "a and b contain %s hashes\n",
  698. cmpStr(\%a, \%b) == 0 ? "the same" : "different";
  699. printf "a and b contain %s hashes\n",
  700. cmpStrHard(\%a, \%b) == 0 ? "the same" : "different";
  701. The first reports that both those the hashes contain the same data,
  702. while the second reports that they do not. Which you prefer is left as
  703. an exercise to the reader.
  704. =head2 How do I find the first array element for which a condition is true?
  705. You can use this if you care about the index:
  706. for ($i= 0; $i < @array; $i++) {
  707. if ($array[$i] eq "Waldo") {
  708. $found_index = $i;
  709. last;
  710. }
  711. }
  712. Now C<$found_index> has what you want.
  713. =head2 How do I handle linked lists?
  714. In general, you usually don't need a linked list in Perl, since with
  715. regular arrays, you can push and pop or shift and unshift at either end,
  716. or you can use splice to add and/or remove arbitrary number of elements at
  717. arbitrary points. Both pop and shift are both O(1) operations on perl's
  718. dynamic arrays. In the absence of shifts and pops, push in general
  719. needs to reallocate on the order every log(N) times, and unshift will
  720. need to copy pointers each time.
  721. If you really, really wanted, you could use structures as described in
  722. L<perldsc> or L<perltoot> and do just what the algorithm book tells you
  723. to do. For example, imagine a list node like this:
  724. $node = {
  725. VALUE => 42,
  726. LINK => undef,
  727. };
  728. You could walk the list this way:
  729. print "List: ";
  730. for ($node = $head; $node; $node = $node->{LINK}) {
  731. print $node->{VALUE}, " ";
  732. }
  733. print "\n";
  734. You could grow the list this way:
  735. my ($head, $tail);
  736. $tail = append($head, 1); # grow a new head
  737. for $value ( 2 .. 10 ) {
  738. $tail = append($tail, $value);
  739. }
  740. sub append {
  741. my($list, $value) = @_;
  742. my $node = { VALUE => $value };
  743. if ($list) {
  744. $node->{LINK} = $list->{LINK};
  745. $list->{LINK} = $node;
  746. } else {
  747. $_[0] = $node; # replace caller's version
  748. }
  749. return $node;
  750. }
  751. But again, Perl's built-in are virtually always good enough.
  752. =head2 How do I handle circular lists?
  753. Circular lists could be handled in the traditional fashion with linked
  754. lists, or you could just do something like this with an array:
  755. unshift(@array, pop(@array)); # the last shall be first
  756. push(@array, shift(@array)); # and vice versa
  757. =head2 How do I shuffle an array randomly?
  758. Use this:
  759. # fisher_yates_shuffle( \@array ) :
  760. # generate a random permutation of @array in place
  761. sub fisher_yates_shuffle {
  762. my $array = shift;
  763. my $i;
  764. for ($i = @$array; --$i; ) {
  765. my $j = int rand ($i+1);
  766. next if $i == $j;
  767. @$array[$i,$j] = @$array[$j,$i];
  768. }
  769. }
  770. fisher_yates_shuffle( \@array ); # permutes @array in place
  771. You've probably seen shuffling algorithms that works using splice,
  772. randomly picking another element to swap the current element with:
  773. srand;
  774. @new = ();
  775. @old = 1 .. 10; # just a demo
  776. while (@old) {
  777. push(@new, splice(@old, rand @old, 1));
  778. }
  779. This is bad because splice is already O(N), and since you do it N times,
  780. you just invented a quadratic algorithm; that is, O(N**2). This does
  781. not scale, although Perl is so efficient that you probably won't notice
  782. this until you have rather largish arrays.
  783. =head2 How do I process/modify each element of an array?
  784. Use C<for>/C<foreach>:
  785. for (@lines) {
  786. s/foo/bar/; # change that word
  787. y/XZ/ZX/; # swap those letters
  788. }
  789. Here's another; let's compute spherical volumes:
  790. for (@volumes = @radii) { # @volumes has changed parts
  791. $_ **= 3;
  792. $_ *= (4/3) * 3.14159; # this will be constant folded
  793. }
  794. If you want to do the same thing to modify the values of the hash,
  795. you may not use the C<values> function, oddly enough. You need a slice:
  796. for $orbit ( @orbits{keys %orbits} ) {
  797. ($orbit **= 3) *= (4/3) * 3.14159;
  798. }
  799. =head2 How do I select a random element from an array?
  800. Use the rand() function (see L<perlfunc/rand>):
  801. # at the top of the program:
  802. srand; # not needed for 5.004 and later
  803. # then later on
  804. $index = rand @array;
  805. $element = $array[$index];
  806. Make sure you I<only call srand once per program, if then>.
  807. If you are calling it more than once (such as before each
  808. call to rand), you're almost certainly doing something wrong.
  809. =head2 How do I permute N elements of a list?
  810. Here's a little program that generates all permutations
  811. of all the words on each line of input. The algorithm embodied
  812. in the permute() function should work on any list:
  813. #!/usr/bin/perl -n
  814. # tsc-permute: permute each word of input
  815. permute([split], []);
  816. sub permute {
  817. my @items = @{ $_[0] };
  818. my @perms = @{ $_[1] };
  819. unless (@items) {
  820. print "@perms\n";
  821. } else {
  822. my(@newitems,@newperms,$i);
  823. foreach $i (0 .. $#items) {
  824. @newitems = @items;
  825. @newperms = @perms;
  826. unshift(@newperms, splice(@newitems, $i, 1));
  827. permute([@newitems], [@newperms]);
  828. }
  829. }
  830. }
  831. =head2 How do I sort an array by (anything)?
  832. Supply a comparison function to sort() (described in L<perlfunc/sort>):
  833. @list = sort { $a <=> $b } @list;
  834. The default sort function is cmp, string comparison, which would
  835. sort C<(1, 2, 10)> into C<(1, 10, 2)>. C<E<lt>=E<gt>>, used above, is
  836. the numerical comparison operator.
  837. If you have a complicated function needed to pull out the part you
  838. want to sort on, then don't do it inside the sort function. Pull it
  839. out first, because the sort BLOCK can be called many times for the
  840. same element. Here's an example of how to pull out the first word
  841. after the first number on each item, and then sort those words
  842. case-insensitively.
  843. @idx = ();
  844. for (@data) {
  845. ($item) = /\d+\s*(\S+)/;
  846. push @idx, uc($item);
  847. }
  848. @sorted = @data[ sort { $idx[$a] cmp $idx[$b] } 0 .. $#idx ];
  849. Which could also be written this way, using a trick
  850. that's come to be known as the Schwartzian Transform:
  851. @sorted = map { $_->[0] }
  852. sort { $a->[1] cmp $b->[1] }
  853. map { [ $_, uc((/\d+\s*(\S+)/ )[0] ] } @data;
  854. If you need to sort on several fields, the following paradigm is useful.
  855. @sorted = sort { field1($a) <=> field1($b) ||
  856. field2($a) cmp field2($b) ||
  857. field3($a) cmp field3($b)
  858. } @data;
  859. This can be conveniently combined with precalculation of keys as given
  860. above.
  861. See http://www.perl.com/CPAN/doc/FMTEYEWTK/sort.html for more about
  862. this approach.
  863. See also the question below on sorting hashes.
  864. =head2 How do I manipulate arrays of bits?
  865. Use pack() and unpack(), or else vec() and the bitwise operations.
  866. For example, this sets $vec to have bit N set if $ints[N] was set:
  867. $vec = '';
  868. foreach(@ints) { vec($vec,$_,1) = 1 }
  869. And here's how, given a vector in $vec, you can
  870. get those bits into your @ints array:
  871. sub bitvec_to_list {
  872. my $vec = shift;
  873. my @ints;
  874. # Find null-byte density then select best algorithm
  875. if ($vec =~ tr/\0// / length $vec > 0.95) {
  876. use integer;
  877. my $i;
  878. # This method is faster with mostly null-bytes
  879. while($vec =~ /[^\0]/g ) {
  880. $i = -9 + 8 * pos $vec;
  881. push @ints, $i if vec($vec, ++$i, 1);
  882. push @ints, $i if vec($vec, ++$i, 1);
  883. push @ints, $i if vec($vec, ++$i, 1);
  884. push @ints, $i if vec($vec, ++$i, 1);
  885. push @ints, $i if vec($vec, ++$i, 1);
  886. push @ints, $i if vec($vec, ++$i, 1);
  887. push @ints, $i if vec($vec, ++$i, 1);
  888. push @ints, $i if vec($vec, ++$i, 1);
  889. }
  890. } else {
  891. # This method is a fast general algorithm
  892. use integer;
  893. my $bits = unpack "b*", $vec;
  894. push @ints, 0 if $bits =~ s/^(\d)// && $1;
  895. push @ints, pos $bits while($bits =~ /1/g);
  896. }
  897. return \@ints;
  898. }
  899. This method gets faster the more sparse the bit vector is.
  900. (Courtesy of Tim Bunce and Winfried Koenig.)
  901. Here's a demo on how to use vec():
  902. # vec demo
  903. $vector = "\xff\x0f\xef\xfe";
  904. print "Ilya's string \\xff\\x0f\\xef\\xfe represents the number ",
  905. unpack("N", $vector), "\n";
  906. $is_set = vec($vector, 23, 1);
  907. print "Its 23rd bit is ", $is_set ? "set" : "clear", ".\n";
  908. pvec($vector);
  909. set_vec(1,1,1);
  910. set_vec(3,1,1);
  911. set_vec(23,1,1);
  912. set_vec(3,1,3);
  913. set_vec(3,2,3);
  914. set_vec(3,4,3);
  915. set_vec(3,4,7);
  916. set_vec(3,8,3);
  917. set_vec(3,8,7);
  918. set_vec(0,32,17);
  919. set_vec(1,32,17);
  920. sub set_vec {
  921. my ($offset, $width, $value) = @_;
  922. my $vector = '';
  923. vec($vector, $offset, $width) = $value;
  924. print "offset=$offset width=$width value=$value\n";
  925. pvec($vector);
  926. }
  927. sub pvec {
  928. my $vector = shift;
  929. my $bits = unpack("b*", $vector);
  930. my $i = 0;
  931. my $BASE = 8;
  932. print "vector length in bytes: ", length($vector), "\n";
  933. @bytes = unpack("A8" x length($vector), $bits);
  934. print "bits are: @bytes\n\n";
  935. }
  936. =head2 Why does defined() return true on empty arrays and hashes?
  937. The short story is that you should probably only use defined on scalars or
  938. functions, not on aggregates (arrays and hashes). See L<perlfunc/defined>
  939. in the 5.004 release or later of Perl for more detail.
  940. =head1 Data: Hashes (Associative Arrays)
  941. =head2 How do I process an entire hash?
  942. Use the each() function (see L<perlfunc/each>) if you don't care
  943. whether it's sorted:
  944. while ( ($key, $value) = each %hash) {
  945. print "$key = $value\n";
  946. }
  947. If you want it sorted, you'll have to use foreach() on the result of
  948. sorting the keys as shown in an earlier question.
  949. =head2 What happens if I add or remove keys from a hash while iterating over it?
  950. Don't do that.
  951. =head2 How do I look up a hash element by value?
  952. Create a reverse hash:
  953. %by_value = reverse %by_key;
  954. $key = $by_value{$value};
  955. That's not particularly efficient. It would be more space-efficient
  956. to use:
  957. while (($key, $value) = each %by_key) {
  958. $by_value{$value} = $key;
  959. }
  960. If your hash could have repeated values, the methods above will only
  961. find one of the associated keys. This may or may not worry you.
  962. =head2 How can I know how many entries are in a hash?
  963. If you mean how many keys, then all you have to do is
  964. take the scalar sense of the keys() function:
  965. $num_keys = scalar keys %hash;
  966. In void context it just resets the iterator, which is faster
  967. for tied hashes.
  968. =head2 How do I sort a hash (optionally by value instead of key)?
  969. Internally, hashes are stored in a way that prevents you from imposing
  970. an order on key-value pairs. Instead, you have to sort a list of the
  971. keys or values:
  972. @keys = sort keys %hash; # sorted by key
  973. @keys = sort {
  974. $hash{$a} cmp $hash{$b}
  975. } keys %hash; # and by value
  976. Here we'll do a reverse numeric sort by value, and if two keys are
  977. identical, sort by length of key, and if that fails, by straight ASCII
  978. comparison of the keys (well, possibly modified by your locale -- see
  979. L<perllocale>).
  980. @keys = sort {
  981. $hash{$b} <=> $hash{$a}
  982. ||
  983. length($b) <=> length($a)
  984. ||
  985. $a cmp $b
  986. } keys %hash;
  987. =head2 How can I always keep my hash sorted?
  988. You can look into using the DB_File module and tie() using the
  989. $DB_BTREE hash bindings as documented in L<DB_File/"In Memory Databases">.
  990. The Tie::IxHash module from CPAN might also be instructive.
  991. =head2 What's the difference between "delete" and "undef" with hashes?
  992. Hashes are pairs of scalars: the first is the key, the second is the
  993. value. The key will be coerced to a string, although the value can be
  994. any kind of scalar: string, number, or reference. If a key C<$key> is
  995. present in the array, C<exists($key)> will return true. The value for
  996. a given key can be C<undef>, in which case C<$array{$key}> will be
  997. C<undef> while C<$exists{$key}> will return true. This corresponds to
  998. (C<$key>, C<undef>) being in the hash.
  999. Pictures help... here's the C<%ary> table:
  1000. keys values
  1001. +------+------+
  1002. | a | 3 |
  1003. | x | 7 |
  1004. | d | 0 |
  1005. | e | 2 |
  1006. +------+------+
  1007. And these conditions hold
  1008. $ary{'a'} is true
  1009. $ary{'d'} is false
  1010. defined $ary{'d'} is true
  1011. defined $ary{'a'} is true
  1012. exists $ary{'a'} is true (perl5 only)
  1013. grep ($_ eq 'a', keys %ary) is true
  1014. If you now say
  1015. undef $ary{'a'}
  1016. your table now reads:
  1017. keys values
  1018. +------+------+
  1019. | a | undef|
  1020. | x | 7 |
  1021. | d | 0 |
  1022. | e | 2 |
  1023. +------+------+
  1024. and these conditions now hold; changes in caps:
  1025. $ary{'a'} is FALSE
  1026. $ary{'d'} is false
  1027. defined $ary{'d'} is true
  1028. defined $ary{'a'} is FALSE
  1029. exists $ary{'a'} is true (perl5 only)
  1030. grep ($_ eq 'a', keys %ary) is true
  1031. Notice the last two: you have an undef value, but a defined key!
  1032. Now, consider this:
  1033. delete $ary{'a'}
  1034. your table now reads:
  1035. keys values
  1036. +------+------+
  1037. | x | 7 |
  1038. | d | 0 |
  1039. | e | 2 |
  1040. +------+------+
  1041. and these conditions now hold; changes in caps:
  1042. $ary{'a'} is false
  1043. $ary{'d'} is false
  1044. defined $ary{'d'} is true
  1045. defined $ary{'a'} is false
  1046. exists $ary{'a'} is FALSE (perl5 only)
  1047. grep ($_ eq 'a', keys %ary) is FALSE
  1048. See, the whole entry is gone!
  1049. =head2 Why don't my tied hashes make the defined/exists distinction?
  1050. They may or may not implement the EXISTS() and DEFINED() methods
  1051. differently. For example, there isn't the concept of undef with hashes
  1052. that are tied to DBM* files. This means the true/false tables above
  1053. will give different results when used on such a hash. It also means
  1054. that exists and defined do the same thing with a DBM* file, and what
  1055. they end up doing is not what they do with ordinary hashes.
  1056. =head2 How do I reset an each() operation part-way through?
  1057. Using C<keys %hash> in scalar context returns the number of keys in
  1058. the hash I<and> resets the iterator associated with the hash. You may
  1059. need to do this if you use C<last> to exit a loop early so that when you
  1060. re-enter it, the hash iterator has been reset.
  1061. =head2 How can I get the unique keys from two hashes?
  1062. First you extract the keys from the hashes into arrays, and then solve
  1063. the uniquifying the array problem described above. For example:
  1064. %seen = ();
  1065. for $element (keys(%foo), keys(%bar)) {
  1066. $seen{$element}++;
  1067. }
  1068. @uniq = keys %seen;
  1069. Or more succinctly:
  1070. @uniq = keys %{{%foo,%bar}};
  1071. Or if you really want to save space:
  1072. %seen = ();
  1073. while (defined ($key = each %foo)) {
  1074. $seen{$key}++;
  1075. }
  1076. while (defined ($key = each %bar)) {
  1077. $seen{$key}++;
  1078. }
  1079. @uniq = keys %seen;
  1080. =head2 How can I store a multidimensional array in a DBM file?
  1081. Either stringify the structure yourself (no fun), or else
  1082. get the MLDBM (which uses Data::Dumper) module from CPAN and layer
  1083. it on top of either DB_File or GDBM_File.
  1084. =head2 How can I make my hash remember the order I put elements into it?
  1085. Use the Tie::IxHash from CPAN.
  1086. use Tie::IxHash;
  1087. tie(%myhash, Tie::IxHash);
  1088. for ($i=0; $i<20; $i++) {
  1089. $myhash{$i} = 2*$i;
  1090. }
  1091. @keys = keys %myhash;
  1092. # @keys = (0,1,2,3,...)
  1093. =head2 Why does passing a subroutine an undefined element in a hash create it?
  1094. If you say something like:
  1095. somefunc($hash{"nonesuch key here"});
  1096. Then that element "autovivifies"; that is, it springs into existence
  1097. whether you store something there or not. That's because functions
  1098. get scalars passed in by reference. If somefunc() modifies C<$_[0]>,
  1099. it has to be ready to write it back into the caller's version.
  1100. This has been fixed as of perl5.004.
  1101. Normally, merely accessing a key's value for a nonexistent key does
  1102. I<not> cause that key to be forever there. This is different than
  1103. awk's behavior.
  1104. =head2 How can I make the Perl equivalent of a C structure/C++ class/hash or array of hashes or arrays?
  1105. Usually a hash ref, perhaps like this:
  1106. $record = {
  1107. NAME => "Jason",
  1108. EMPNO => 132,
  1109. TITLE => "deputy peon",
  1110. AGE => 23,
  1111. SALARY => 37_000,
  1112. PALS => [ "Norbert", "Rhys", "Phineas"],
  1113. };
  1114. References are documented in L<perlref> and the upcoming L<perlreftut>.
  1115. Examples of complex data structures are given in L<perldsc> and
  1116. L<perllol>. Examples of structures and object-oriented classes are
  1117. in L<perltoot>.
  1118. =head2 How can I use a reference as a hash key?
  1119. You can't do this directly, but you could use the standard Tie::Refhash
  1120. module distributed with perl.
  1121. =head1 Data: Misc
  1122. =head2 How do I handle binary data correctly?
  1123. Perl is binary clean, so this shouldn't be a problem. For example,
  1124. this works fine (assuming the files are found):
  1125. if (`cat /vmunix` =~ /gzip/) {
  1126. print "Your kernel is GNU-zip enabled!\n";
  1127. }
  1128. On some legacy systems, however, you have to play tedious games with
  1129. "text" versus "binary" files. See L<perlfunc/"binmode">, or the upcoming
  1130. L<perlopentut> manpage.
  1131. If you're concerned about 8-bit ASCII data, then see L<perllocale>.
  1132. If you want to deal with multibyte characters, however, there are
  1133. some gotchas. See the section on Regular Expressions.
  1134. =head2 How do I determine whether a scalar is a number/whole/integer/float?
  1135. Assuming that you don't care about IEEE notations like "NaN" or
  1136. "Infinity", you probably just want to use a regular expression.
  1137. if (/\D/) { print "has nondigits\n" }
  1138. if (/^\d+$/) { print "is a whole number\n" }
  1139. if (/^-?\d+$/) { print "is an integer\n" }
  1140. if (/^[+-]?\d+$/) { print "is a +/- integer\n" }
  1141. if (/^-?\d+\.?\d*$/) { print "is a real number\n" }
  1142. if (/^-?(?:\d+(?:\.\d*)?|\.\d+)$/) { print "is a decimal number" }
  1143. if (/^([+-]?)(?=\d|\.\d)\d*(\.\d*)?([Ee]([+-]?\d+))?$/)
  1144. { print "a C float" }
  1145. If you're on a POSIX system, Perl's supports the C<POSIX::strtod>
  1146. function. Its semantics are somewhat cumbersome, so here's a C<getnum>
  1147. wrapper function for more convenient access. This function takes
  1148. a string and returns the number it found, or C<undef> for input that
  1149. isn't a C float. The C<is_numeric> function is a front end to C<getnum>
  1150. if you just want to say, ``Is this a float?''
  1151. sub getnum {
  1152. use POSIX qw(strtod);
  1153. my $str = shift;
  1154. $str =~ s/^\s+//;
  1155. $str =~ s/\s+$//;
  1156. $! = 0;
  1157. my($num, $unparsed) = strtod($str);
  1158. if (($str eq '') || ($unparsed != 0) || $!) {
  1159. return undef;
  1160. } else {
  1161. return $num;
  1162. }
  1163. }
  1164. sub is_numeric { defined &getnum }
  1165. Or you could check out String::Scanf which can be found at
  1166. http://www.perl.com/CPAN/modules/by-module/String/.
  1167. The POSIX module (part of the standard Perl distribution) provides
  1168. the C<strtol> and C<strtod> for converting strings to double
  1169. and longs, respectively.
  1170. =head2 How do I keep persistent data across program calls?
  1171. For some specific applications, you can use one of the DBM modules.
  1172. See L<AnyDBM_File>. More generically, you should consult the FreezeThaw,
  1173. Storable, or Class::Eroot modules from CPAN. Here's one example using
  1174. Storable's C<store> and C<retrieve> functions:
  1175. use Storable;
  1176. store(\%hash, "filename");
  1177. # later on...
  1178. $href = retrieve("filename"); # by ref
  1179. %hash = %{ retrieve("filename") }; # direct to hash
  1180. =head2 How do I print out or copy a recursive data structure?
  1181. The Data::Dumper module on CPAN (or the 5.005 release of Perl) is great
  1182. for printing out data structures. The Storable module, found on CPAN,
  1183. provides a function called C<dclone> that recursively copies its argument.
  1184. use Storable qw(dclone);
  1185. $r2 = dclone($r1);
  1186. Where $r1 can be a reference to any kind of data structure you'd like.
  1187. It will be deeply copied. Because C<dclone> takes and returns references,
  1188. you'd have to add extra punctuation if you had a hash of arrays that
  1189. you wanted to copy.
  1190. %newhash = %{ dclone(\%oldhash) };
  1191. =head2 How do I define methods for every class/object?
  1192. Use the UNIVERSAL class (see L<UNIVERSAL>).
  1193. =head2 How do I verify a credit card checksum?
  1194. Get the Business::CreditCard module from CPAN.
  1195. =head2 How do I pack arrays of doubles or floats for XS code?
  1196. The kgbpack.c code in the PGPLOT module on CPAN does just this.
  1197. If you're doing a lot of float or double processing, consider using
  1198. the PDL module from CPAN instead--it makes number-crunching easy.
  1199. =head1 AUTHOR AND COPYRIGHT
  1200. Copyright (c) 1997-1999 Tom Christiansen and Nathan Torkington.
  1201. All rights reserved.
  1202. When included as part of the Standard Version of Perl, or as part of
  1203. its complete documentation whether printed or otherwise, this work
  1204. may be distributed only under the terms of Perl's Artistic Licence.
  1205. Any distribution of this file or derivatives thereof I<outside>
  1206. of that package require that special arrangements be made with
  1207. copyright holder.
  1208. Irrespective of its distribution, all code examples in this file
  1209. are hereby placed into the public domain. You are permitted and
  1210. encouraged to use this code in your own programs for fun
  1211. or for profit as you see fit. A simple comment in the code giving
  1212. credit would be courteous but is not required.