[e-lang] Idea: generic makers for PBC

[Mark S. Miller]

Kevin Reid wrote:
> I therefore propose a separate loader; I have no name for it at the  
> moment. This loader might or might not use the same source/namespace  
> as <import>. Its distinguishing properties are:
> 
>    - It is PassByCopy by way of being an exit (in Data-E terms).
>    - It will return a maker for any name requested.
> 
> If asked for a FQN it doesn't know, it will return a 'generic' object.
> 
> def makeGeneric(uncall) {
>    def generic implements pbc {
>      to __optUncall() { return uncall }
>      match [verb, args] { makeGeneric([generic, verb, args]) }
>    }
> }


I don't understand the proposal. When the loader in question is asked for an 
FQN it doesn't know, it returns a 'generic' object with what uncall triple? 
Where does the uncall argument for the first call to makeGeneric come from?

-- 
Text by me above is hereby placed in the public domain

     Cheers,
     --MarkM