Comment #3 on issue 3375 by rydier: PositionableStream remove dependence to Compiler http://code.google.com/p/pharo/issues/detail?id=3375 Ie why not just move both methods to the extension category?

Comment #5 on issue 3375 by Benjamin.VanRyseghem.Pharo: PositionableStream remove dependence to Compiler http://code.google.com/p/pharo/issues/detail?id=3375 @Comment 2 and Comment 3: You're right, here the new cs. @Comment 4 : fileInSilentlyAnnouncing: doesn't invoke methods from *System-Changes. That's true that there is dependencies between Compiler-Kernel and System-Changes, but I can fix dependencies only step by step :) (and I hope I will not be the only Pharo user who will fix such issues) Attachments: Issue3375PositionableStreamRemoveDependenceToCompiler.1.cs 1.6 KB

Comment #7 on issue 3375 by rydier: PositionableStream remove dependence to Compiler http://code.google.com/p/pharo/issues/detail?id=3375 @5: "fileInSilentlyAnnouncing: doesn't invoke methods from *System-Changes." What are you talking about? It uses both nextChunk, checkForPreamble:, and skipStyleChunk

Comment #9 on issue 3375 by rydier: PositionableStream remove dependence to Compiler http://code.google.com/p/pharo/issues/detail?id=3375 No, but other methods which have similar functionality, and have already been moved to *System-Changes, do :P (Like I implied in first comment by mentioning fileIn, fileInAnnouncing: etc.) Why not switch those over as well when you're at it? The reason I mentioned consistency is because the browser is very class-centric. When I now browse PositionableStream, and see the functionality for filing in code randomly distributed between two extension categories, rather than all being in a logically named category like they used to... Let's just say it doesn't always strike me as practical improvements.

Updates: Status: Closed Comment #11 on issue 3375 by stephane...@gmail.com: PositionableStream remove dependence to Compiler http://code.google.com/p/pharo/issues/detail?id=3375 in 13083