--vertical-tightness=2
--weld-nested-containers
+==> b1174.in <==
+# S1
+
+if ( $op and $op eq 'do_search' ) {
+ @{$invoices} =
+ GetInvoices(
+ shipmentdatefrom =>
+ $shipmentdatefrom ? output_pref( {
+ str => $shipmentdatefrom,
+ dateformat => 'iso'
+ } )
+ : undef,
+ publicationyear => $publicationyear,
+ );
+}
+
+# S2
+
+if ( $op and $op eq 'do_search' ) {
+ @{$invoices} =
+ GetInvoices(
+ shipmentdatefrom =>
+ $shipmentdatefrom
+ ? output_pref(
+ {
+ str => $shipmentdatefrom,
+ dateformat => 'iso'
+ }
+ )
+ : undef,
+ publicationyear => $publicationyear,
+ );
+}
+
+==> b1174.par <==
+--extended-continuation-indentation
+--line-up-parentheses
+--maximum-line-length=38
+--variable-maximum-line-length
+--weld-nested-containers
+
==> b1175.in <==
# S1
if ( $rOpts_line_up_parentheses
|| $want_break_before{$type_prev} )
{
- if ( substr( $type_prev, 0, 1 ) eq '=' ) {
+
+ # If there are other sequence items between the start of this line
+ # and the opening token in question, then do not include tokens on
+ # the previous line in length calculations. This check added to
+ # fix case b1174 which had a '?' on the line
+ my $no_previous_seq_item = $Kref == $Kouter_opening
+ || $rLL->[$Kref]->[_KNEXT_SEQ_ITEM_] == $Kouter_opening;
+
+ if ( $no_previous_seq_item
+ && substr( $type_prev, 0, 1 ) eq '=' )
+ {
$Kref = $Kprev;
# Fix for b1144 and b1112: backup to the first nonblank
=over 4
+=item B<Fix possible welding instability in ternary after fat comma>
+
+Random testing produced a case of formatting instability involving welding
+within a ternary expression following a fat comma:
+
+ if ( $op and $op eq 'do_search' ) {
+ @{$invoices} =
+ GetInvoices(
+ shipmentdatefrom =>
+ $shipmentdatefrom ? output_pref( {
+ str => $shipmentdatefrom,
+ dateformat => 'iso'
+ } )
+ : undef,
+ publicationyear => $publicationyear,
+ );
+ }
+
+when the following specific parameters were used
+
+ --extended-continuation-indentation
+ --line-up-parentheses
+ --maximum-line-length=38
+ --variable-maximum-line-length
+ --weld-nested-containers
+
+This update fixes this issue, case b1174.
+
+18 Jul 2021.
+
=item B<Fix mis-tokenization before pointer>
Random testing produced the following case in which formatting was unstable because