[Glass] Alternative commitOnAlmostOutOfMemoryDuring: ?

[Richard Sargent]

>> I find #commitOnAlmostOutOfMemoryDuring:  very useful but it has the
drawback that
>> it might not commit (if there wasn't an almost out of memory exception).

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)


On Fri, Dec 6, 2013 at 9:41 AM, Mariano Martinez Peck <marianopeck at gmail.com
> wrote:

> 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 ?
>
> --
> Mariano
> http://marianopeck.wordpress.com
>
> _______________________________________________
> Glass mailing list
> Glass at lists.gemtalksystems.com
> http://lists.gemtalksystems.com/mailman/listinfo/glass
>
>


-- 
Richard Sargent
Business Development Manager
503-766-4719
richard.sargent at gemtalksystems.comGemTalk Systems
15220 NW Greenbrier Parkway #240
Beaverton, OR 97006
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20131206/204d38e3/attachment-0001.html>