Re: [Pharo-users] transactions on pharo objects

Hi This research from VPRI may be useful: Worlds: Controlling the Scope of Side Effects and Experiments with Worlds (Alessandro Warth, Yoshiki Ohshima, Ted Kaehler, and Alan Kay) They had a J

Re: [Pharo-users] transactions on pharo objects

El mié., 1 de ago. de 2018 20:52, Richard Sargent < richard.sarg...@gemtalksystems.com> escribió: > Esteban A. Maringolo wrote > > As a general purpose solution if you can do that, you end up > > implementing a mini gemstone in Pharo :) > > > > But what's sure is that you should have a mini object

Re: [Pharo-users] transactions on pharo objects

Esteban A. Maringolo wrote > I think it is a tricky thing to do "in memory transactions", even > without thinking about databases. > You have to define what to keep and where to place the "original" > values (inst. vars.) of the object. > > As a general purpose solution if you can do that, you end

Re: [Pharo-users] transactions on pharo objects

Norbert Hartl wrote: > the biggest problem with a copy approach is that all identity checks fail with the copied objects The scheme I proposed *hides* the (shallow) copies. The only thing ever done with them is to copy their contents back into the original objects. There are therefore no "ident

Re: [Pharo-users] transactions on pharo objects

Hello, A lot of time ago, we have implemented a basic support for STM in Java (it is written in Scala... dark dark dark ages). We have used aspect oriented programming to intercept the reading and writing of the instance variables of the classes that support the transactions. We kept a dictionary

Re: [Pharo-users] transactions on pharo objects

> Am 31.07.2018 um 06:57 schrieb Richard O'Keefe : > > Basically, what you are talking about is Software Transactional Memory. > According to > https://en.wikipedia.org/wiki/Software_transactional_memory#Smalltalk > there *is* STM support for Pharo at > http://source.lukas-renggli.ch/transactio

Re: [Pharo-users] transactions on pharo objects

> Am 30.07.2018 um 16:02 schrieb Sean P. DeNigris : > > Peter Uhnák wrote >> is there some library or approach how to do transactions… directly in >> memory on Pharo >> objects > > Magritte? It uses the Memento pattern to verify all changes before > committing to real object. > This only work

Re: [Pharo-users] transactions on pharo objects

> Am 30.07.2018 um 15:16 schrieb Peter Uhnák : > > Hi, > > is there some library or approach how to do transactions in pharo? > And I don't mean database transactions, but directly in memory on Pharo > objects... e.g. > > p := Person new. > > transaction do: [ > p name: 'Nobody'. > p

Re: [Pharo-users] transactions on pharo objects

Basically, what you are talking about is Software Transactional Memory. According to https://en.wikipedia.org/wiki/Software_transactional_memory#Smalltalk there *is* STM support for Pharo at http://source.lukas-renggli.ch/transactional/ although the last version there is from 2012, and there have b

Re: [Pharo-users] transactions on pharo objects

El lun., 30 jul. 2018 a las 11:03, Sean P. DeNigris () escribió: > > Peter Uhnák wrote > > is there some library or approach how to do transactions… directly in > > memory on Pharo > > objects > > Magritte? It uses the Memento pattern to verify all changes before > committing to real object. But y

Re: [Pharo-users] transactions on pharo objects

Peter Uhnák wrote > is there some library or approach how to do transactions… directly in > memory on Pharo > objects Magritte? It uses the Memento pattern to verify all changes before committing to real object. - Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f13106

Re: [Pharo-users] transactions on pharo objects

Maybe you can have a look to this paper : https://www.sciencedirect.com/science/article/pii/S1477842408000237 On Mon, Jul 30, 2018 at 2:17 PM Peter Uhnák wrote: > Hi, > > is there some library or approach how to do transactions in pharo? > And I don't mean database transactions, but directly in

Re: [Pharo-users] transactions on pharo objects

I think it is a tricky thing to do "in memory transactions", even without thinking about databases. You have to define what to keep and where to place the "original" values (inst. vars.) of the object. As a general purpose solution if you can do that, you end up implementing a mini gemstone in Pha

[Pharo-users] transactions on pharo objects

Hi, is there some library or approach how to do transactions in pharo? And I don't mean database transactions, but directly in memory on Pharo objects... e.g. p := Person new. transaction do: [ p name: 'Nobody'. p age: 70. ] on: Error do: [ transaction rollback. ]. self assert: p na