Guys,
I find #commitOnAlmostOutOfMemoryDuring: very useful but it has the drawback that it might now commit (if there wasn't an almost out of memory exception). So I was thinking a variant that does:
commitOnAlmostOutOfMemoryDuring: aBlock self almostOutOfMemoryStaticHandlerInstalled ifTrue: [ ^aBlock value ].
[ self installAlmostOutOfMemoryStaticHandler: 75. aBlock value.
System commitTransaction. ] ensure: [ self uninstallAlmostOutOfMemoryStaticHandler ] Notice the added System commitTransaction. would that be useful ? -- http://marianopeck.wordpress.com _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Administrator
|
>> I find #commitOnAlmostOutOfMemoryDuring: very useful but it has the drawback that With a guaranteed commit, the name should be changed to reflect its intent. e.g. #commitDuringAndAfter: (not a very good name, but you get the idea)>> it might not commit (if there wasn't an almost out of memory exception). On Fri, Dec 6, 2013 at 9:41 AM, Mariano Martinez Peck <[hidden email]> wrote:
--
_______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
On Fri, Dec 6, 2013 at 2:51 PM, Richard Sargent <[hidden email]> wrote:
yes!
Mariano http://marianopeck.wordpress.com _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
In reply to this post by Richard Sargent
Sounds good ... From: "Richard Sargent" <[hidden email]> _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Free forum by Nabble | Edit this page |