in reply to Sequential defined-or operators

The second last snippet is much more readable than the last. An alternative is 
my $theme =  $global_config->{modes}{$current_mode}{theme}
          // $theme_config->{current_theme}
          // $default_theme
          // 'none';

[download]

Replies are listed 'Best First'.
Re^2: Sequential defined-or operators
by WoodyWeaver (Monk) on Jan 14, 2008 at 16:44 UTC
    WWCD? (What would Conway Do?)

    ...Break long lines before an operator. That approach ensures that each line of the continued expression will start with an operator, which is unusual in Perl code. That way, as the reader's eye scans down the left margin of the code, its immediately obvious that an indented line is merely the continuation of the previous line, because it starts with an operator.

    The indenting of the second and subsequent lines of the expression is also critical...they should be indented to the starting column of the expression to which they belong.

    Hence, ikegami. (Although Conway likes to put the terminal semi-colon on a line by itself, to signal completion of the multi-line formula.)
[reply]
      That approach ensures that each line of the continued expression will start with an operator
      Another reason I support this style is the starting operators can be made inline with the assignment operator where the line begins. I don't think it's so much unusual in Perl code, at least, it's not strange for me.

      However, I still much prefer (and get used) to break long lines after the operator because the adoption of \ (backslash) usage to break long lines in Unix/Linux convention. Still, both styles sign line continuation as we don't see the statement terminator (;) until the last line of the group.

      Open source softwares? Share and enjoy. Make profit from them if you can. Yet, share and enjoy!

[reply]
Re^2: Sequential defined-or operators
by naikonta (Curate) on Jan 14, 2008 at 09:38 UTC
    It's wonderful, ikegami! My worries disappear right away.

    Open source softwares? Share and enjoy. Make profit from them if you can. Yet, share and enjoy!

[reply]

      Just be careful with precedence. Absent prototypes overriding the default, 

      my $value =  $hash{$arg}
          // func $arg
          // 'default';

      [download]
      means 
      my $value =  $hash{$arg}
          // func($arg // 'default');

      [download]

      Putting parens around the low precedence bit solves the problem. 

      my $value =  $hash{$arg}
          // (func $arg)
          // 'default';

      [download]

      Of course, with functions, you can also do 

      my $value =  $hash{$arg}
          // func($arg)
          // 'default';

      [download]
[reply]
[d/l]
[select]
        Yes, I'm aware about this issue. I wrote related matter sometime ago. So I believe it will be perfectly fine to write: 
        my $value = $hash{$key} // func $arg // 'default';

        [download]
        knowing that func is a unary operator.

        Open source softwares? Share and enjoy. Make profit from them if you can. Yet, share and enjoy!

[reply]
[d/l]

In Section Seekers of Perl Wisdom