Hello
In VAST there is a class-side method #exiting which can be implemented in an
application and is called just before the image is shut down. I use it to
typically implement clean-up code.
Is there something similar in Pharo?
If I use aBlock ensure: cleanUpBlock, is the cleanUpBlock guarant
Hi Jeff
Is this you from Brisbane? Did you used to come to the meetups at the State
Library?
Well anyway, I used to do something similar to what you describe, by lazy
initializing the connection and also checking to see if it is open.
dbConnection
dbConnection ifNil: [ dbConenction :=
In my code I'm opening a sqlite connection and keeping it open rather than
opening and closing one on each transaction.
Generally it's working well.
I often save and close my image. When I then reopen the image I still have a
connection and it says it's open, but using it gives me an error.
This
Hi Stef,
Didn't knew this project existed: https://github.com/pharo-pkg
Glad to read someone is taking care of it.
In the meantime I will explore about file system workaround with diff-like
tools.
Thank you for your reply.
Cheers,
Hernán
El jue., 12 mar. 2020 a las 4:25, Stéphane Ducasse (<
st
Esteban, if time permits, could you please describe what situations lead to
crashes, and with which images?
Thanks,
Tomaz
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html