This is the mail archive of the guile@cygnus.com mailing list for the guile project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
>>>>> "Michael" == Michael N Livshin <mike@olan.com> writes: Michael> Err... Actually, the problem is not that. Michael> Consider this situation: Michael> Module A defines public class class-A, and specializes Michael> generic some-generic for A. The generic is being called Michael> in some of A's functions, but users of the module A have Michael> know way of knowing this implementation detail. Michael> Now, module B imports A, derives class-B from A and Michael> specializes some-generic for B. Then, A's functions that Michael> use some-generic will behave differently when handed an ^^^^^^^^^^^ But this will also happen without modules ??? Michael> object of class class-B, breaking in many creative ways. ^^^^^^^^ If you do not want this behaviour, some-generic should not be called in A's function, but A's method in some-generic is to be called. I have perhaps missed the point ? -- B. Urban