The following code works for me (in teh sense that Object::InsideOut doesn't immediately complain):

#!/usr/bin/perl

package CodeRef; 
use strict;
{
    use Object::InsideOut;

warn sprintf "Using %s version %s", 
    'Object::InsideOut::VERSION',
    $Object::InsideOut::VERSION
    ;

  my @code :Field
           :Std( Name => 'code', Private => 1 )
           :Arg(Name => 'code', Mand =>1 )
           :Type(CODE);

sub call() {
    my $self = shift;
    my $code = $self->get_code();
    return $code->(@_);
  }

}

1;

#=====

package main;

sub sum {
  my $sum =0 ;
  foreach my $num (@_) {
    $sum += $num;
}
  return $sum;
}

my $cref = CodeRef->new( code => \&sum );

__END__

Using Object::InsideOut::VERSION version 3.81 at tmp.pl line 9.

[download]

In reply to Re^3: Object::InsideOut with CODE_REF constructor argument by Corion
in thread Object::InsideOut with CODE_REF constructor argument by nudged

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.