Thanks Richard.
You have described it perfectly. This is exactly what I mean. I was
reading about $*REPO but like you, I am unable to truly grasp how to get at
the information required to make this a reality.
On Sun, Mar 7, 2021 at 7:07 AM Richard Hainsworth
wrote:
> Interesting question.
>
>
Afaik, existing mechanisms (`use`, `zef`, `-I`) support the following:
> Within this namespace, I would ideally designate
> SuperDuperProgram::Modules to be the namespace
> that modules would live under.
> These modules would have their own git repos and
> depend on SuperDuperProgram being instal
Hi Paul,
That's an interesting question, and I have a few thoughts below. Before I get
to those, I wanted
to point out an issue with the way you started your email with "Hey Gents": the
Raku community
includes many talented women, and I'd love to see it include more.
On to the technical quest
> On 7 Mar 2021, at 00:16, Joseph Brenner wrote:
>
> Is there anything like an equivalent of "man perlguts" for Raku/rakudo?
>
> There are things like this, but they seem to be very out-of-date:
>
> https://github.com/rakudo/rakudo/blob/master/docs/architecture.html
That is indeed severely ou
Interesting question.
I would like to know a good way of doing this. But just to refine the
question, so that we don't discuss which directory modules are in
(doesn't matter whether its lib/ or bin/), or whether we use classes and
inheritance, the interesting (for me) question is: how to find
