Excerpts from Thierry Goubier's message of 2015-12-07 06:42:51 +0100: > > i am interested in the versioning of code and objects. > > the poster makes a good point there. > The traditional, full approach, would have been to use an object > oriented database like GemStone. Anything that can version objects can > version Smalltalk code.
gemstone is proprietary, so that doesn't really work for me. are there alternatives? > > what if i am on a non-networked machine, running pharoNOS or even squeakNOS, > > how would i keep old versions of my code/objects? is there any in-image > > solution for that? > The .changes provides that in a limited form. It would be easy to do > better in memory, if needed. well, i wouldn't need or even want it in memory, so on disk is fine. the problem is more likely management of the same. browsing the changes is not really convenient. ideally i'd like to see versions in the class-browser and in the debugger, where on error i could then take a look at older versions for comparison, and switch to them to see if maybe the last change was the cause of the error. greetings, martin. -- eKita - the online platform for your entire academic life -- chief engineer eKita.co pike programmer pike.lysator.liu.se caudium.net societyserver.org secretary beijinglug.org mentor fossasia.org foresight developer foresightlinux.org realss.com unix sysadmin Martin Bähr working in china http://societyserver.org/mbaehr/
