4 ms·
Maybe now he also understands why objects are often preferable. Closures are liked handicapped objects. Names are resolved when the closures is created, not w
by richcollins 18y ago
Maybe now he also understands why objects are often preferable. Closures are liked handicapped objects. Names are resolved when the closures is created, not when it is called. This is not nearly as flexible as an object, where names are resolved when the function is called.
- henning 18y agoOK, have fun implementing an interface just to manipulate a collection when a one-liner would have sufficed.
- richcollins 18y agoWhy do you assume you can't use a one liner in an OO language? Counter example: list(1, 2, 3, 4) map(+(1)) http://iolanguage.com/ http://iolanguage.com/
- khafra 18y agoThe venerable master Qc Na was walking with his student, Anton. Hoping to prompt the master into a discussion, Anton said "Master, I have heard that objects are a very good thing - is this true?" Qc Na looked pityingly at his student and replied, "Foolish pupil - objects are merely a poor man's closures." Chastised, Anton took his leave from his master and returned to his cell, intent on studying closures. He carefully read the entire "Lambda: The Ultimate..." series of papers and its cousins, and implemented a small Scheme interpreter with a closure-based object system. He learned much, and looked forward to informing his master of his progress. On his next walk with Qc Na, Anton attempted to impress his master by saying "Master, I have diligently studied the matter, and now understand that objects are truly a poor man's closures." Qc Na responded by hitting Anton with his stick, saying "When will you learn? Closures are a poor man's object." At that moment, Anton became enlightened.
- swombat 18y agoBrilliant. Just brilliant.
- richcollins 18y agoI've never seen an implementation of closures with dynamic lookups. Perhaps you can't point me in the right direction.