I don't fully see what are the immediate benefits. But as usually happen when you replace something old, limited and "not so well designed" by something better designed from the ground up I guess it will open Pharo to features not yet thought of. Does the new debugger have something "better" than the previous one? Regards! Esteban A. Maringolo 2013/11/21 Tudor Girba <tudor@tudorgirba.com>:
Triple impressive! This is another sample of an apparently tiny change that actually has deep impact on the future of our beloved environment.
Ladies and gentlemen, I know you are busy, but please take the time to acknowledge it :)
Doru
On Thu, Nov 21, 2013 at 12:58 PM, Martin Dias <tinchodias@gmail.com> wrote:
wow, impressive!
On Thu, Nov 21, 2013 at 9:02 AM, Marcus Denker <marcus.denker@inria.fr> wrote:
Hi,
Yesterday Camille did the change to finally remove the old class builder! (just a removal + a small change to NativeBoost to use the new class builder to create anonymous classes).
This means - 1000 Loc of completely un-understandable code removed. - we now 100% run on the new class builder from the Slot Project.
Next on the list (not all for Pharo3):
- remove PackageInfo - old Browser + CodeHolder hierarchy - PseudoClass&Co â> Ring - old AST+Compiler (this in Pharo4)
We already did (all in Pharo3): -> remove URI -> deprecated Url for ZnUrl -> removed HTTPSocket facade -> MIMEType retired for ZnMimeType -> old Debugger is removed -> Class categories are replaced by Protocols
I am quite sure that these cleanups will enable us to build a lot of very interesting things in the future.
Marcus
-- www.tudorgirba.com
"Every thing has its own flow"