Beefy Boxes and Bandwidth Generously Provided by pair Networks
Syntactic Confectionery Delight
 
PerlMonks  

comment on

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

No, that makes perfect sense. If I pass in a reference while keeping a local copy then I'm free to alter the reference at will. Put differently - if I pass in an object as a parameter then that object is still free to modify itself independant of what the other enclosing object's needs are.

This is how things are supposed to be, or at least I don't see why things should be different. It works this way if I think if it in terms of C or in terms of perl.

Added: Further, I know that when I know I need to copy an array, I do exactly that. So instead of writing ->new( foo => \ @ary ) I'm likely (assuming I'm thinking clearly) to write ->new( foo => [ @ary ] ). That assumes its a one level array with no further references but I think you get the picture. I explicitly copy when I mean to and references retain all of their associated meaning.

Added again: While I've never found the need for it if I did need a deep copy I understand that Storable's dclone() does this nicely. This of course completely blows lots of XS modules out of the water since they have external non-perl structures that wouldn't be copied. I don't think there is a safe or sane way to copy those beasts.


In reply to Re: On the involuntary encapsulation violation by diotalevi
in thread On the involuntary encapsulation violation by bronto

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 making s'mores by the fire in the courtyard of the Monastery: (6)
As of 2024-03-28 22:46 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found