> > Yes. Filenames and URLs are particularly problematic. Fortunately > they > tend to be O(100) in size, as opposed to O(1000) in size. Thus, the > less demanding path of just hashing the characters is efficient enough > for the cases I've seen so far. > >> IMO, we should not let Array hash ~= Interval hash coexist with >> Array = Interval >> Because it's like putting some traps on programmers path. >> > > Yes, I agree. I'd vote on breaking #=, with the caveat that chances > are > some code will be broken. Does Pharo have a release strategy that > allows more fundamental changes to go in, as opposed to > maintenance/improvement fixes?
yes we talk then we summarize and describe a bug entry and Now I'm thinking that it would be good to have a page with important changes per version I would put there the discussions about the float changes we did in 1.0. Stef _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
