Re^3: I can crash perl

tmp_7 seems to be a typo. It should have been declared with the others.

I am putting on my thinking cap. I am going to re-write this to be more efficient with memory. I have already made it more memory efficient (A little more) and now it doesn't crash (i.e. run out of memory, if that is in fact what's happening). I need to learn how to use hash tables (if that's even the correct term). I think it's time.

Just so ya-all know where I was coming from, I thought using temp variables would allow me to get memory back after I was done with them. (i.e. undef @tmp_1). Yes I know, peek memory would still be an issue. If anyone wants to give me some guidance on how to go about re-writing this I would accept it.

Comment on Re^3: I can crash perl

Replies are listed 'Best First'.
Re^4: I can crash perl by Anonymous Monk on Apr 07, 2015 at 10:13 UTC
sure, see Understanding the Schwartzian transform. / Re: Understanding the Schwartzian transform. then write `my @sorted = map { $_->[0] } sort { $a->[1] cmp $b->[1]; } ## magicpipe map { [ $_, expensive($_) } @unsorted; sub expensive { ... my $magicpipe = join '\|', $dir_and_file_name, $date_time_mod, $file_size, $encpd, $deleted_file, $has_iden ; return [ $original, lc($magicpipe) ]; }` [download] Also see File::Find::Rule/find rule , Path::Tiny/path tiny, Win32::Unicode	[reply] [d/l]
Re^5: I can crash perl by AnomalousMonk (Archbishop) on Apr 07, 2015 at 12:10 UTC
`map { [ $_, expensive($_) } @unsorted` Note that this expression should be `map { [ $_, expensive($_) ] } @unsorted` (missing right-square-bracket) or even `map [ $_, expensive($_) ], @unsorted` (needs extra comma). Give a man a fish: `<%-(-(-(-<`	[reply] [d/l] [select]