Beefy Boxes and Bandwidth Generously Provided by pair Networks
Think about Loose Coupling
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??

Hello, everybody.

I am still understanding Perl, but what bothers me some examples with open filehandles closing them and the diamond operator with the special $^I variable. What bothers me: why using open for read and write when we can use <> ? The diamod did the better job for me actually.

Update on 28.09.2012

I`ve found an excersise in Lama book on page 168 in which as an extra credit at 4 and 5, I think was the using of the diamond operator. Solving these two ex-es, I`ve found out that diamond has some better feats than open/close ( for text files since you always read and write ( consider you`ve used the -i variable ), however you can miss the --rwx check of the file and try to process a root file or unreadable/writable one. However I think that both are useful for different tasks, I think I`ve solved my mystery about the diamond operator, also I was wondering ( by my assumption the answer is 'NO') if diamond can fseek the file or you can just match with __LINE__ variable... Open/close still puts a fpointer to the file while diamond is some kind of magic using a copy and original files... Maybe this is a strong point if you worry about losing a file. And... I doubt that diamond can open db and binary files, it`s just my guess, I may fail at it too.


In reply to Diamond or Open, Process, Close? by heatblazer

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others rifling through the Monastery: (7)
As of 2024-03-28 14:02 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found