Re^2: Real life uses for closures.

in reply to Re: Real life uses for closures.
in thread Real life uses for closures.

take a loot at Jon Skeet's The Beauty of Closures

Thanks for the link. The content was very interesting; and right on subject for my enquiry.

(That said, now I remember what put me of learning C#. It just as bad a Java for making your source code look like you suffer from Tourette's: Predicate ... predicate ... predicate ... predicate. :)

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

Comment on Re^2: Real life uses for closures.

Replies are listed 'Best First'.
Re^3: Real life uses for closures. by runrig (Abbot) on Feb 13, 2013 at 00:36 UTC
Heh, reading that link, one of the basic things I've used closures for lately is filtering a list in different ways. I had one utility function that goes into a loop parsing email files from a directory (and if successful, finally returning the attachments from the one you want according to some parameters) and skipping files that it's already seen before. Then I found that in some particular case I needed to call the function multiple times and have it remember what it had seen from the previous call. So I turned the filtering function into a parameter, allowing you to maintain the hash of 'seen' email files outside of the loop in the main function (but keeping the original behaviour by default, which is what I want most of the time). Pretty basic example...but there it is.	[reply]

Replies are listed 'Best First'.

Re^3: Real life uses for closures.
by runrig (Abbot) on Feb 13, 2013 at 00:36 UTC

Heh, reading that link, one of the basic things I've used closures for lately is filtering a list in different ways. I had one utility function that goes into a loop parsing email files from a directory (and if successful, finally returning the attachments from the one you want according to some parameters) and skipping files that it's already seen before. Then I found that in some particular case I needed to call the function multiple times and have it remember what it had seen from the previous call. So I turned the filtering function into a parameter, allowing you to maintain the hash of 'seen' email files outside of the loop in the main function (but keeping the original behaviour by default, which is what I want most of the time). Pretty basic example...but there it is.

[reply]

In Section Seekers of Perl Wisdom