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 609625
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 13, 20262026-05-13T17:35:12+00:00 2026-05-13T17:35:12+00:00

Possible ways: Using push : my @list; push @list, ‘foo’ if $foo; push @list,

  • 0

Possible ways:

  1. Using push:

    my @list;  
    push @list, 'foo' if $foo;  
    push @list, 'bar' if $bar;  
    
  2. Using the conditional operator:

    my @list = (  
        $foo ? 'foo' : (),    
        $bar ? 'bar' : (),              
    );
    
  3. Using the x!! Boolean list squash operator:

    my @list = (  
        ('foo') x!! $foo,  
        ('bar') x!! $bar,  
    );  
    

Which one is better and why?

  • 1 1 Answer
  • 0 Views
  • 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-13T17:35:12+00:00Added an answer on May 13, 2026 at 5:35 pm

    Well, they all do different things.

    However, all other factors being equal,

    push @list, 'foo' if $foo;
    

    is the statement that conveys its meaning most directly, so it should be preferred.

    If you have to pause and think about statement that supposedly does something as simple as pushing an array element, you are doing something wrong.

    my @list = (
        $foo ? 'foo' : (),
        $bar ? 'bar' : (),
    );
    

    could be OK if this is part of some colossal initialization that is being done elsewhere.

    I think using

    my @list = (
        ('foo') x!! $foo,
        ('bar') x!! $bar,
    ); 
    

    indicates that the programmer has —how can I put this?— issues.

    Incidentally, there is no such thing called the x!! composite operator. The !! is double logical negation. It converts an arbitrary false value to a defined but false value (the empty string) which yields 0 when used where perl expects a number. A true value is converted to a 1. Here, !! operates on $foo and $bar and writing it x!! $foo unnecessarily obfuscates the meaning of the code.

    x is the repetition operator. So,

     ('foo') x !!$foo;
    

    means repeat ('foo') once or not at all, depending on whether $foo is true or false, respectively.

    PS: Of course, it turns out there was a PerlMonks article introducing the so-called boolean list squash operator. I read the article and find it unconvincing.

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

Sidebar

Ask A Question

Stats

  • Questions 384k
  • Answers 384k
  • Best Answers 0
  • User 1
  • Popular
  • Answers
  • Editorial Team

    How to approach applying for a job at a company ...

    • 7 Answers
  • Editorial Team

    What is a programmer’s life like?

    • 5 Answers
  • Editorial Team

    How to handle personal stress caused by utterly incompetent and ...

    • 5 Answers
  • Editorial Team
    Editorial Team added an answer Yes, it is possible. Step 1: Compile the Code Use… May 14, 2026 at 11:11 pm
  • Editorial Team
    Editorial Team added an answer Depends on the grand schema of things (hoping y'all got… May 14, 2026 at 11:11 pm
  • Editorial Team
    Editorial Team added an answer Continuing with my original comment, I would recommend to have… May 14, 2026 at 11:11 pm

Trending Tags

analytics british company computer developers django employee employer english facebook french google interview javascript language life php programmer programs salary

Top Members

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.