What you say is all true when dealing with text files, but when it comes to dealing with non text files (like an mp3, or jpeg), read() is probably going to be your only solution since you really can't read those types of files line by line, and who knows what you'll get in an array. The usefulness of read is best understood when you understand it's compliment function seek() (well to me anyway). With these two functions you can jump around a file and read various amounts of data, without worrying about hitting an unexpected \n.
In reply to Re: read()
in thread read()
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||