Hi, > Even in Java this is not completely true, as you have inner classes. > On Fri, 2015-04-03 at 22:32 +0200, Paolo Bonzini wrote:
> On 03/04/2015 13:07, Jan Vrany wrote: > > while playing with GST, I found bit difficult to navigate > > through code. For example, source code for class Exception > > is in file kernel/ExcHandling.st. So I have to grep all the time. > > > > I wonder why is it so? Wouldn't it be better to have one file > > per class name, like in Java? > Indeed, but still, much more predictable. > In GNU Smalltalk most classes have a 1:1 correspondence with files. In > the case of ExcHandling.st, the reason why you have two files is > historical---that file used to have the whole implementation of > instance-based (IBM Smalltalk) exceptions, including bits now in > BlkClosure.st. Splitting it in Exception.st and ExceptionSet.st would > make a lot of sense, and there are probably some similar cases elsewhere. > > When splitting files one could take the occasion for creating > subdirectories of kernel/ as well. > At the same time, I think it would be pointless to split AnsiExcept.st > in 40 or 50 files. Why it would be pointless? > Sure, you can, but the kernel GNU Smalltalk code is > not meant to be edited in a browser, Well, this sort of spoils the whole idea of having smalltalkish IDE... > since it needs to redefine some > methods during initialization and the order of the doits (Evals) is very > important too. Yeah, I feared that there are cases like this. But maybe we can work out a way to solve this... Jan _______________________________________________ help-smalltalk mailing list [email protected] https://lists.gnu.org/mailman/listinfo/help-smalltalk
