For me they work differently.

put_string_ref( \(get_string()) ); # pass return value of get_string() put_string_ref( \(&get_string) ); # pass a coderef pointing to &get_s +tring

I guess if we take what tye mentioned in another response, in that we don't need the brackets for this to work, then it looks like the following holds true:

\&func # gives you a reference to a function \func() # gives you a reference to the return value of func

and a quick test verifies this:

sub func { "the string"; } print \&func, "\n"; # prints CODE(0x814d990) print \func(), "\n"; # prints SCALAR(0x813aa8c)

I guess what I've learned here is that there can be a big difference between &func and func(). I used to use them interchangably, but I will be more careful from now on.

Thanks for your help...


In reply to Re: Re: Re: Re: Working with references to scalars by cees
in thread Working with references to scalars by cees

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



  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.