Re: [Pharo-project] [ANN 1.2] prebuilt core 1.2 final
On Mar 18, 2011, at 7:09 AM, Lukas Renggli wrote:
Ahh, looks like SimpleMorphic has some (probably unintentional) overrides of core methods. Unloading the package pretty much breaks everything :-(
Lukas
On 18 March 2011 07:02, Lukas Renggli <renggli@gmail.com> wrote:
Very good! We then can release the 1.2 Full soon, too. I wonder if we should adopt your OB codebase for that? Or do we wait for 1.2.1?
I would wait a bit. I noticed that the debugger is quite broken. I only get the pre-debug window, but clicking on any button opens another pre-debug window. I don't have time to investigate, is this also in core or some side-effect of loading/unloading packages?
I would not unload packaged. Everything not tested is broken, and so if you do things like that I am sure you will have problems. And nobody ever unloaded anything from Core. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
On 18.03.2011 07:41, Marcus Denker wrote:
On Mar 18, 2011, at 7:09 AM, Lukas Renggli wrote:
Ahh, looks like SimpleMorphic has some (probably unintentional) overrides of core methods. Unloading the package pretty much breaks everything :-(
Lukas
On 18 March 2011 07:02, Lukas Renggli<renggli@gmail.com> wrote:
Very good! We then can release the 1.2 Full soon, too. I wonder if we should adopt your OB codebase for that? Or do we wait for 1.2.1? I would wait a bit. I noticed that the debugger is quite broken. I only get the pre-debug window, but clicking on any button opens another pre-debug window. I don't have time to investigate, is this also in core or some side-effect of loading/unloading packages? I would not unload packaged.
Everything not tested is broken, and so if you do things like that I am sure you will have problems.
And nobody ever unloaded anything from Core.
Marcus I thought the general idea was to remove SimpleMorphic before releases? Think I read so in an issue, or on the list.
Cheers, Henry
I would not unload packaged.
Everything not tested is broken, and so if you do things like that I am sure you will have problems.
And nobody ever unloaded anything from Core.
You must be joking right? In the mission you say "stable and small core", but the numbers say something entirely different: PharoCore 1.0 is 11 MB, PharoCore 1.1 is 14 MB, PharoCore 1.2 is 16 MB. I mentioned it before in this list, but I already had to unload stuff in PharoCore 1.1. Honestly, I don't really see the point of a PharoCore image if it contains more and more not unloadable non-core code. Lukas -- Lukas Renggli www.lukas-renggli.ch
Lukas Marcus is RIGHT. How can we make progress without adding temporarily new libraries and migrating? How can we make progress if people do not use the release candidate phase as it should be? Tell me because we are all ears opened. Stef
I would not unload packaged.
Everything not tested is broken, and so if you do things like that I am sure you will have problems.
And nobody ever unloaded anything from Core.
You must be joking right? In the mission you say "stable and small core", but the numbers say something entirely different: PharoCore 1.0 is 11 MB, PharoCore 1.1 is 14 MB, PharoCore 1.2 is 16 MB. I mentioned it before in this list, but I already had to unload stuff in PharoCore 1.1. Honestly, I don't really see the point of a PharoCore image if it contains more and more not unloadable non-core code.
Lukas
-- Lukas Renggli www.lukas-renggli.ch
participants (4)
-
Henrik Sperre Johansen -
Lukas Renggli -
Marcus Denker -
Stéphane Ducasse