Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 3314194
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 17, 20262026-05-17T22:12:11+00:00 2026-05-17T22:12:11+00:00

I have a Moose object module that should accept a relatively large data structure

  • 0

I have a Moose object module that should accept a relatively large data structure (ds) as one of its constructor arguments. It is used to calculate some of the object’s attributes. However, I do not wish to store ds itself as an attributes — it is only needed during the construction of the object.

I thought of using BUILDARGS but then I’m not sure how to define that ds is a required argument.

How can I work around this?

  • 1 1 Answer
  • 1 View
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-17T22:12:12+00:00Added an answer on May 17, 2026 at 10:12 pm

    I’d be inclined to have a constructor that takes only the calculated values derived from your data structure. Then use a different method to take limited params plus the data structure as args.

    sub generate_foo_from_ds {
        my $class = shift; 
        my %arg = @_;
    
        my $ds = $arg{foo_data};
    
        # Get attributes from args
        my %attrib;
        for (qw(foo bar baz ) {
            croak "Attrib '$_' is required" unless exists $arg{$_};
            $attrib{$_} = $arg{$_};
        }
    
        # calculate some more attributes here.
        $attrib{griz} = $ds->{whee} * $ds->{whoosh} / $ds->{whiz}[12];
    
        my $foo = $class->new( %attrib );
    
        return $foo;
    }
    

    Then make your objects like so:

    my $foo = Foo->generate_foo_from_ds( foo_data => $bar, foo => 1, bar => 2, baz => 2 );
    

    Now you don’t have to worry about weird serialization issues or BUILDARGS or even BUILD. You have a simple method and that is all.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Moose is a fantastic object framework. The trouble is that, taken together with its
I'm building a Perl application that relies on Moose. One task the Moose object
I have a control derived from a CWnd object that has its custom implemented
How should I define a Moose object subroutine after its initialization? I'm writing an
I'm using Moose to write an object module. I currently have a few mandatory
I have written a set of classes and interfaces that are implemented in Moose
I have a series of Moose objects that I'm looking to feed to JSON::XS
I have a Moose class that i would like to store using Apache::Session::File. However,
Here's something weird that I can't figure out. I have a Moose class that
I have a Moose class with an attribute that is an ArrayRef (read-only) and

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.