my proposed solutions for challenge-019, p5 1 & 2

1 files changed, 0 insertions, 40 deletions

diff --git a/challenge-019/daniel-mantovani/perl5/perltidy.LOG b/challenge-019/daniel-mantovani/perl5/perltidy.LOG
deleted file mode 100644
index b5172e3a4d..0000000000
--- a/challenge-019/daniel-mantovani/perl5/perltidy.LOG
+++ /dev/null
@@ -1,40 +0,0 @@
-perltidy version 20180220 log file on a darwin system, OLD_PERL_VERSION=5.028000
-Configuration and command line parameters for this run:
--st -profile=.../.perltidyrc
-To find error messages search for 'WARNING' with your editor
-Indentation will be with 4 spaces
-Line 4 implies starting-indentation-level = 0
-
-########################  WARNING  #########################
-82: my ( $month, $year ) = @( gtime($epoch)[ 4, 5 ] );
-                           -- ^                       
-found bareword where operator expected (previous token underlined)
-############################################################
-
-########################  WARNING  #########################
-There is no previous '(' to match a ')' on line 82
-82: my ( $month, $year ) = @( gtime($epoch)[ 4, 5 ] );
-                                                    ^
-############################################################
-The nesting depths in the table below are at the start of the lines.
-The indicated output line numbers are not always exact.
-ci = levels of continuation indentation; bk = 1 if in BLOCK, 0 if not.
-
-in:out indent c b  nesting   code + messages; (messages begin with >>>)
-lines  levels i k            (code begins with one '.' per indent level)
-------  ----- - - --------   -------------------------------------------
-L50:50   i0:0 0 1            my $epoch = timegm( 0, 0, 12, 1, 0, ....
-L86:86   i0:0 0 1 {{)}       >>>WARNING: Program bug in scan_list: hit nesting error which should have been caught
-No indentation disagreement seen
-
-No lines exceeded 80 characters
-  Maximum output line length was 80 at line 50
-WARNING: To save a full .LOG file rerun with -g
-WARNING: 
-Oops, you seem to have encountered a bug in perltidy.  Please check the
-BUGS file at http://perltidy.sourceforge.net.  If the problem is not
-listed there, please report it so that it can be corrected.  Include the
-smallest possible script which produces this message, along with the
-.LOG file if appropriate.  See the manual pages for contact information.
-Your efforts are appreciated.  
-Thank you!