When I took up the role of maintaining MC1.5, I did so with the express purpose of integrating all of the MC forks for the benefit of the whole community. If I had known that this idea was conceptually a waste of time then I wouldn't have bothered. I did it because I wanted overrides to actually work, and because I thought people would be enthusiastic for it to actually work. How on earth do you do anything practical with MC1? It drove me nuts.
I have a hard time to trust a system that references 6 undefined variables and that sends twice as many undefined messages (see attached screenshot).
Perhaps you guys are still not understanding what LPF is for.
I honestly do not understand what LPF means. It is probably because I am not a native speaker.
I am just speaking up because I found code in Pier that was not compatible with Squeak, so I worry where this is all going.
I still don't know what kind of problem you encountered with Pier? Please file a bug at <http://code.google.com/p/pier/>. I exclusively use Pharo for the development and deployment of Pier, Seaside and my other public and commercial projects. I know and trust the people that are behind Pharo, they push forward in the right direction. They maintain a good balance between clean-up, new features and building a trustworthy stable system. It obvious that external packages will break sooner or later and that framework developers have to pay attention to portability. At some point there will probably be no way around a Squeak specific platform class, if people want to use Seaside in Squeak? Lukas -- Lukas Renggli http://www.lukas-renggli.ch
