t 10:43 AM Veesh Goldman
> wrote:
> >
> > That was one of the most illuminating things I have ever read. Thank you
> for taking the time to write that.
> >
> > On Tue, Jan 28, 2020, 16:12 Trey Ethan Harris
> wrote:
> >>
> >> Oops, rereading what I
Oops, rereading what I sent I see I missed looping back to one detail:
On Tue, Jan 28, 2020 at 08:54 Trey Harris wrote:
> In Perl5, undefinedness meant something that it still _can_ mean, and in
> the course of ordinary “business logic” programming perhaps still most
> often means: a
If one uses MAIN with arguments, one simply cannot get strings like
"Bool::True" and "True" from the command line into the same argument,
regardless of whether one uses no type constraint, a Str, a Str(), or a
slurpy. See the quote below from rakudo #2794
This came up yesterday and I wanted to capture it:
I've been sitting on the name just in case (I grabbed it when it briefly
seemed like we needed an "in-between" place for non-core, non-ecosystem
stuff like editor-support packages).
Right now, https://github.com/perl6-contrib is just sitting
I'm thinking of a Hash-like collection where I can add objects using a
index-less append operation, but then have random access to the elements
based on a key provided by the object. (For instance, imagine a
ProcessTable, where I create the collection telling it to index by the .pid
method, add
It's not only in -e. I just used that for my example. A file with a unit
sub MAIN exhibits the same issue.
On Mon, Mar 28, 2016, 17:39 Elizabeth Mattijsen via RT <
perl6-bugs-follo...@perl.org> wrote:
> Perhaps we should disallow “unit” with -e?
>
> > On 28 Mar 2016, at 20:18,
No, see S06-routines.pod:
As with module and class declarations, a sub declared
with the C declarator (and ending in semicolon) is allowed at the
outermost
file scope if it is the
first such declaration, in which case the rest of the file is the body:
unit sub MAIN
