Front page | perl.perl6.language |
Postings from May 2008
HaloO, Daniel Ruoso wrote: > In fact, it simply means that it's up to that object's metaobject to > answer that, and not to a supra-meta-model to be able to answer to all > of the possible metamodel implementations. Since all three forms are derived from a programmer's declaration involving names the problem is simple lookup, indeed. The fact that N objects share one meta object is just for reducing the memory footprint. You could make every object carry the full meta info around. > You can do that as "shortcuts" and "optimizations" that are indeed > needed in order to actually bootstrap the system, but that's not what > the type system is. Would you be so kind to enlighten me what the type system is, if not a type calculation overlaid over a value calculation? Regards, TSa. -- "The unavoidable price of reliability is simplicity" -- C.A.R. Hoare "Simplicity does not precede complexity, but follows it." -- A.J. Perlis 1 + 2 + 3 + 4 + ... = -1/12 -- Srinivasa RamanujanThread Previous | Thread Next