Neal H Walfield wrote: > I think that this is a reasonable idea, however, it only addresses a > small part of the problem. I feel that a better solution would be to use > a similar method to perl modules: a hierarchal name space. In fact, we
We'll have better than that :) My tool will have a full package implementation (similar to Ontolingua's) but of course I'll avoid perl syntax at all costs!!! :) The cool part will be that we won't be making the same assumptions as a half-decent OO language. Apologies to perl freaks here, but that's what it is... By assumptions, I mean that symbol import/export will be a general construct in my impl. I think it will have to be as general as CLOS package system but let me finish the design first. Details later.. :) Frankly, I'm thinking of a single colon or a single dot for that... :) Of course the syntax is *totally* irrelevant here. It's the semantics that matters. Thanks, -- Eray (exa) Ozkural Comp. Sci. Dept., Bilkent University, Ankara e-mail: [EMAIL PROTECTED] www: http://www.cs.bilkent.edu.tr/~erayo