Yup. The problem is that this issue should be solved in a larger context, like integrating Flow...
On 12/19/05, stéphane ducasse ducasse@iam.unibe.ch wrote:
hi File team it seems that this is for you :)
http://bugs.impara.de/view.php?id=2149
Stef
In my opinion this is a very critical bug that will let people decide against the use of Squeak for serious applications in the future. After discovering and identifying it some time ago, I keep on discovering new places where this particular problem causes other bugs. It is still difficult for me to understand how it could remain unfixed for almost 30 years :-/
Lukas
-- Lukas Renggli http://www.lukas-renggli.ch
On 12/19/05, Lukas Renggli renggli@gmail.com wrote:
After discovering and identifying it some time ago, I keep on discovering new places where this particular problem causes other bugs. It is still difficult for me to understand how it could remain unfixed for almost 30 years :-/
Well... file access of course is just there for backwards compatibility with ancient, file-based systems ;)
But seriously: fixing this should probably be done as part of a overhaul of this whole subsystem. With Flow probably being a good candidate.
Cees and others
what could be the little chicken steps to make progress in that direction? Is it a 2 weeks work for a motivated guy? Because again we could do something: pay someone to really fix that.
Stef
On 19 déc. 05, at 19:42, Cees De Groot wrote:
On 12/19/05, Lukas Renggli renggli@gmail.com wrote:
After discovering and identifying it some time ago, I keep on discovering new places where this particular problem causes other bugs. It is still difficult for me to understand how it could remain unfixed for almost 30 years :-/
Well... file access of course is just there for backwards compatibility with ancient, file-based systems ;)
But seriously: fixing this should probably be done as part of a overhaul of this whole subsystem. With Flow probably being a good candidate.
On 12/20/05, stéphane ducasse ducasse@iam.unibe.ch wrote:
what could be the little chicken steps to make progress in that direction?
Err... introduce Flow, lock-stock-and-barrel :). Probably with some renaming to let it live alongside the old stuff.
On 19-Dec-05, at 10:23 AM, Lukas Renggli wrote:
In my opinion this is a very critical bug that will let people decide against the use of Squeak for serious applications in the future. After discovering and identifying it some time ago, I keep on discovering new places where this particular problem causes other bugs. It is still difficult for me to understand how it could remain unfixed for almost 30 years :-/
It hasn't been around for 30 years. Just about every version of Smalltalk has a different way of dealing with files. So far as I can tell the Squeak code originated with the desire to make it only rely upon the ANSI lib functions - a laudable aim - but they are totally inadequate to any serious usage. Time to replace it.
tim -- tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim In computer science, we stand on each other's feet.
squeak-dev@lists.squeakfoundation.org