3 ms·
There's no idea that a single class might have two versions and that some bits of the program depend on the old version and some on the new. Why not? Why isn't
by epe 17y ago
There's no idea that a single class might have two versions and that some bits of the program depend on the old version and some on the new. Why not? Why isn't live, running code versioned and transactioned so that we can release a patch of a few classes into a running server without taking it down? It should be possible for the old code to handle all of the existing requests and then get garbage collected when it has no further dependencies.
Isn't this also something that Smalltalk can do?
- aaronblohowiak 17y agoYes. You can even have the new version get the function that called it and change the implementation of the caller so your code re-factors itself. Not that I'd recommend this, but you could do it =)
- avibryant 17y agoIt's also something Ruby can do, when running on MagLev.
- raganwald 17y agoIt is not a coïncidence that MagLev came from the Smalltalk community. See all the other comments here :-)