Alias_, it occurs to me that your PPI6 should mimic the reflection API available in Perl 6 (whatever that is). Then it is just a VM-less reflection API and can be swapped for a VM doing direct reflection.

Hurm... I haven't finished reading the spec yet... I'm about half way through, but it occurs to me that there seems to be the assumption that modules will be imported from a single external location, and there is probably no concept of libraries defined by the underlying VM, vs. libraries defined in .pm files in the library search path

the specific question I am asking is this: when a module is defined by a library source known to the underlying VM, and there exists a library in the filesystem search path which duplicates the namespace / module name, a) how does perl6 decide which to use and b) how does the user over-ride the default decision?

mostly the 4th bullet: (things that terminate a token include...) "Any part of the regex or rule that might match whitespace, including whitespace implicitly matched via :sigspace. (However, token declarations are specifically allowed to recognize whitespace within a token.)"

okay, so what i misunderstood was that "might match whitespace" refers specifically to <ws>. maybe that's explained elsewhere (i read the whole thing yesterday, but it's hard to keep so many things in my head :)