tag:blogger.com,1999:blog-17087850.post2175674801387602176..comments2023-10-31T06:50:41.697-04:00Comments on Factor: a practical stack language: Generic resource disposalSlava Pestovhttp://www.blogger.com/profile/02768382790667979877noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-17087850.post-44486878451078073152008-01-31T18:01:00.000-05:002008-01-31T18:01:00.000-05:00I'd like to see more OO languages adopt this patte...I'd like to see more OO languages adopt this pattern. My general feel is that 80/20 rule applies here. You should be able to solve about 80% of your resource lifecycle problems by only reserving the resource for exactly the lifespan of a function call, without having to mangle your code terribly to get there. For the other 20%, you can engage in a little mangling, or simply concentrate your vigilance on those particular parts.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-17087850.post-90974367326842772662008-01-31T15:42:00.000-05:002008-01-31T15:42:00.000-05:00Very nice!Very nice!Anonymousnoreply@blogger.com