Bert,
I thought over this for some time (well, actually not longer than the time it took to write the methods ;-)
I have no, absolutely no idea on what and how users of "base" Squeak do something with source file index and pointer. With users I mean, packages which exists out there. I cannot load + test them all.
So as a matter of *reminder* that something changed while the respective packages where NOT in the image, I introduced the "large" message name variants and put the flag on the "old" methods.
If I had just changed the "old" methods to cope with the new scheme, I would have taken *full* responsibility for packages not in the image to work as if nothing happened while they where away, which is beyond my capabilities.
Take for example the prior: keyword recorded with preambles in files, the format of its argument has changed (will be addressed for 3.9 [only!] when completing migration).
Thank you for sharing your concern. Would this be a show stopper?
/Klaus
On Fri, 28 Jul 2006 00:57:13 +0200, Bert Freudenberg wrote:
Am 27.07.2006 um 20:20 schrieb Klaus D. Witzel:
List,
attached are two .cs files which together push the limit from 32MB to 512MB for the .sources file and the .changes file, no problem so far on #7048.
Why do you want to deprecate all the source-pointer related methods? Wouldn't changing them to cope with the new scheme be sufficient?
- Bert -