[Raku/old-design-docs] 07ac3b: rm broken link

Branch: refs/heads/master Home: https://github.com/Raku/old-design-docs Commit: 07ac3bb2ab509a5143e5f99a0e9c32b823828fae https://github.com/Raku/old-design-docs/commit/07ac3bb2ab509a5143e5f99a0e9c32b823828fae Author: librasteve <40125330+librast...@users.noreply.github.com>

Virtualmin and Webmin web hosting control panel are written in Perl 5

Subject: Virtualmin and Webmin web hosting control panel are written in Perl 5 Good day from Singapore, I understand that Virtualmin and Webmin web hosting control panel are written in Perl 5. Source: In which perl framework is webmin written into? Link:

Re: Correct enum incantation?

On Wed, May 5, 2021 at 6:00 PM William Michels via perl6-users < perl6-us...@perl.org> wrote: > Hello, > > I've been reading over an interesting Answer on StackOverflow by wamba: > > https://stackoverflow.com/a/67324175/7270649 > > I started trying to explore enums on my own and quickly realized

Re: Correct enum incantation?

Thank you Fernando! (still on Rakudo 2020.10 here). On Wed, May 5, 2021 at 10:24 AM Fernando Santagata < nando.santag...@gmail.com> wrote: > On Wed, May 5, 2021 at 6:00 PM William Michels via perl6-users < > perl6-us...@perl.org> wrote: > >> Hello, >> >> I've been reading over an interesting

Correct enum incantation?

Hello, I've been reading over an interesting Answer on StackOverflow by wamba: https://stackoverflow.com/a/67324175/7270649 I started trying to explore enums on my own and quickly realized that method calls on enums are different from simple key/value pairs. For enums, calling a `.key` or

Re: Performance of matrix arithmetic in Raku

Hi, raku doesn't have matrix operations built into the language, so you're probably refering to modules out of the ecosystem? Math::Matrix seems to have everything implemented in pure raku, which you should not expect to outperform pure python without some optimization work.

Performance of matrix arithmetic in Raku

There's a post online comparing Python's performance of matrix arithmetic to C, indicating that Python's performance was 100x (yes, 2 orders of magnitude) slower than C's. If I understand it correctly, matrix modules in Raku call GNU code written in C to perform the actual work. Does that make

Re: Checking for nil return

On 2020-12-29 6:26 a.m., Ruud H.G. van Tol wrote: Basically, never mix error-state and return-value. Rather use a different channel/dimension for each. Such a separation can't be absolute though. One needs to be able to user-define routines that implement additional generic Failure related

Re: Checking for nil return

Moving the "can't catch Nil return, why is Nil also a failure?" question to a Raku issue, https://github.com/Raku/doc/issues/3760 This got me going through Raku source code to see where Nil gets passed through; this looks promising. rakudo/src/vm/moar/spesh-plugins.nqp line 308

Re: Checking for nil return

This commit shows where Nil expanded from being "Absence of a value" to, alternatively, "a benign failure". Unfortunately I haven't found discussion on "benign failure" – semantics, use case, prior art, example, that sort of thing – and the commit doesn't elaborate.

Re: Checking for nil return

Basically, never mix error-state and return-value. Rather use a different channel/dimension for each. And any value itself can have special state too, like "absence" and (via its type) "has-default". On that docs-page, my stomach protested against the Nil/default pairing. Now I need to

Re: Checking for nil return

The closest to null is actually an undefined type object On Mon, Dec 28, 2020, 3:36 PM yary wrote: > Been thinking about this, and checked out the Rakudo repository to peek > into the source. > > Allowing Failure as a return always makes sense to me– every block needs > to be capable of passing

Re: Checking for nil return

Been thinking about this, and checked out the Rakudo repository to peek into the source. Allowing Failure as a return always makes sense to me– every block needs to be capable of passing along a failure, that's how the language is designed. On the other hand, Nil is not a Failure. Conceptually

Re: Multiline/embedded comments

> On 12/22/20, Vadim Belman wrote: >> >> You interpret it incorrectly. The problem is in your '#`{' comment On 12/23/20, Parrot Raiser <1parr...@gmail.com> wrote: > Removing the space between the #` and { changes the error message to: > > ===SORRY!=== Error while compiling

Re: Multiline/embedded comments

You interpret it incorrectly. The problem is in your '#`{' comment. You have a space between the backtick and the opening brace. Therefore it's interpreted as a single line comment. Though even if you remove the space the compiler will complain because it wouldn't find closing } due to

Multiline/embedded comments

While playing around with the bounding characters for the #` form, I encountered an unexpected feature, which may or may not be a bug. If the left bounding character (e.g. the { in #`{ occurs unbalanced in the commented text, the compiler apparently treats it as code, searches for the right

Re: Checking for nil return

Nil is always a valid return value regardless of any check. This is because it is the base of all failures. On Sat, Dec 19, 2020, 8:17 PM yary wrote: > Is this a known issue, or my misunderstanding? > > > subset non-Nil where * !=== Nil; > (non-Nil) > > sub out-check($out) returns non-Nil {

Re: Checking for nil return

After writing that email, I remembered a bit of logic from a class long ago, that any assertion made on the empty set is true. Since Nil is a representation of no results, it would make sense to have assertions about it return true. I think this example shows an optimization to skip return type

Re: Checking for nil return

yary wrote: > Is this a known issue, or my misunderstanding? > >> subset non-Nil where * !=== Nil; > (non-Nil) >> sub out-check($out) returns non-Nil { return $out } > >> out-check(44) > 44 >> out-check(Nil) > Nil > > ^ Huh, I expected an exception on "out-check(Nil)" saying the return value >

Checking for nil return

Is this a known issue, or my misunderstanding? > subset non-Nil where * !=== Nil; (non-Nil) > sub out-check($out) returns non-Nil { return $out } > out-check(44) 44 > out-check(Nil) Nil ^ Huh, I expected an exception on "out-check(Nil)" saying the return value failed the "returns" constraint.

[Raku/old-design-docs] 63e44c: S22: Clarify how system specific values work and c...

Branch: refs/heads/master Home: https://github.com/Raku/old-design-docs Commit: 63e44c36351887f1eb76500d7102f0db44848d27 https://github.com/Raku/old-design-docs/commit/63e44c36351887f1eb76500d7102f0db44848d27 Author: niner Date: 2020-10-01 (Thu, 01 Oct 2020) Changed paths:

[Raku/old-design-docs] b13e78: Update dependency specifications in S22

Branch: refs/heads/master Home: https://github.com/Raku/old-design-docs Commit: b13e78fe5b9dc10bfdacb0122ea40a77b6037ac9 https://github.com/Raku/old-design-docs/commit/b13e78fe5b9dc10bfdacb0122ea40a77b6037ac9 Author: Stefan Seifert Date: 2020-09-30 (Wed, 30 Sep 2020)

Fwd: unflattering flat

Migrating this question over from perl6-users : Can someone explain why in the second and third REPL code lines below, line 2 returns a List while line 3 returns a Seq? And is there a general rule to remember which code returns which data structure? 1> my %hash-with-arrays = a => [1,2], b =>

[Raku/old-design-docs]

Branch: refs/heads/zag-patch-1 Home: https://github.com/Raku/old-design-docs

[Raku/old-design-docs] 1a90f9: fix identifier in used context

Branch: refs/heads/master Home: https://github.com/Raku/old-design-docs Commit: 1a90f942619e0d027f9c19228003e20a1997364d https://github.com/Raku/old-design-docs/commit/1a90f942619e0d027f9c19228003e20a1997364d Author: Aliaksandr Zahatski Date: 2020-04-26 (Sun, 26 Apr 2020)

[Raku/old-design-docs] 1a90f9: fix identifier in used context

Branch: refs/heads/zag-patch-1 Home: https://github.com/Raku/old-design-docs Commit: 1a90f942619e0d027f9c19228003e20a1997364d https://github.com/Raku/old-design-docs/commit/1a90f942619e0d027f9c19228003e20a1997364d Author: Aliaksandr Zahatski Date: 2020-04-26 (Sun, 26 Apr

[Raku/old-design-docs]

Branch: refs/heads/design-into-raku Home: https://github.com/Raku/old-design-docs

[perl6/specs] 6390a5: Move the design documents into the Raku era

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 6390a500201b5c26512940b0920cd6e9e5111abf https://github.com/perl6/specs/commit/6390a500201b5c26512940b0920cd6e9e5111abf Author: Elizabeth Mattijsen Date: 2019-11-16 (Sat, 16 Nov 2019) Changed paths:

[perl6/specs] 3d62b9: Move the design documents into the Raku era

Branch: refs/heads/design-into-raku Home: https://github.com/perl6/specs Commit: 3d62b9ea86f586612d5df9ea9460a12239b6ccf2 https://github.com/perl6/specs/commit/3d62b9ea86f586612d5df9ea9460a12239b6ccf2 Author: Elizabeth Mattijsen Date: 2019-11-16 (Sat, 16 Nov 2019) Changed

[perl6/specs] 180b53: Revert "Move the design documents into the Raku era"

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 180b534bd6f012e7576384326f2e915162c496be https://github.com/perl6/specs/commit/180b534bd6f012e7576384326f2e915162c496be Author: Elizabeth Mattijsen Date: 2019-11-16 (Sat, 16 Nov 2019) Changed paths:

[perl6/specs] c5aa24: Remove obsolete file

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: c5aa24071599a46240ba09cd9c91a37749799d7e https://github.com/perl6/specs/commit/c5aa24071599a46240ba09cd9c91a37749799d7e Author: Elizabeth Mattijsen Date: 2019-11-16 (Sat, 16 Nov 2019) Changed paths:

[perl6/specs] 4508e5: correct spelling for "resources" as in current usage

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 4508e535661ccd1366e492960d54aab97be87bbe https://github.com/perl6/specs/commit/4508e535661ccd1366e492960d54aab97be87bbe Author: Tom Browder Date: 2019-10-02 (Wed, 02 Oct 2019) Changed paths: M

Rakudo update due?

The current version of Rakudo* is 2019.03, which makes it 5 months old. Is there likely to be an update soon? (The underlying compiler seems to have had a few fixes.) (No pressure, I just want to stay as up-to-date as possible.)

Re: Diagnostics?

If you think this is a bug you're always welcome to open a ticket at https://github.com/rakudo/rakudo/issues. Even if it eventually would turn out to be not a bug that wouldn't hurt anybody. In either case it would be very welcomed to always include examples paired with output. Best

Diagnostics?

I've been fiddling with multi-line comments and the bounding characters. Naturally-paired characters e.g. #`(...) #`[...] #`{...} all work well, but with other boundary characters like #`@@ or #`!! produce odd, displaced, diagnostic messages. Reproducing them is so easy, I'll leave it as

Re: Announce: french perl workshop (Aka Journées Perl)

Hello Mark, I was thinking about submitting a talk on the P6 Object System, but I could also change it to Grammars (or do both). Cheers, Laurent. Le mar. 21 mai 2019 à 10:30, Marc Chantreux a écrit : > hello perl6 people, > > we hope there will be some events around the French Perl Worshop >

EnumStr necessary for MAIN handling (was Fwd: [rakudo/rakudo] `MAIN`: `Str` arguments do not accept `True` or `False` (#2794))

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

[perl6/specs] e5b176: Fix typo

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: e5b176cae67ba74035dd2be3518dca863f5e780e https://github.com/perl6/specs/commit/e5b176cae67ba74035dd2be3518dca863f5e780e Author: Carl Masak Date: 2019-02-09 (Sat, 09 Feb 2019) Changed paths: M

Submethods in roles

Hello, I'm working on a fix for https://github.com/rakudo/rakudo/issues/2250. While the problem itself is easily tracks down to add_method not reporting a error, the general fix requires clear understanding of what happens to submethods when a role consumes another role. While things are

If anyone has a use for "perl6-contrib" on Github...

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

Announce: Rakudo Star Release 2018.10

Announce: Rakudo Star Release 2018.10 A useful and usable production distribution of Rakudo Perl 6 On behalf of the Rakudo and Perl 6 development teams, I'm pleased to announce the October 2018 release of "Rakudo Star", a useful and usable production distribution of Rakudo. The tarball for this

[perl6/specs] f42464: Update email address

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: f424643a5bd6ac3e3879b89c33c5b266f009dba7 https://github.com/perl6/specs/commit/f424643a5bd6ac3e3879b89c33c5b266f009dba7 Author: Elizabeth Mattijsen Date: 2018-10-29 (Mon, 29 Oct 2018) Changed paths:

Re: $? and $! equivalents

On Fri, 14 Sep 2018 18:15:21 -0400 Brandon Allbery wrote: > Magic variables make multiple threads impossible, which is why perl 5 > is stuck with ithreads: what happens if two threads each "run" > something at around the same time? > > In Perl 6, you have a Proc object for each subprocess, and

Re: "put" vs "say"

Thanks for the suggestions. I ran a couple of tests: my $data_list = 1..1001; say $data_list; produces 1..1000 real0m0.357s user0m0.435s sys 0m0.048s my $data_list = 1..1001; put $data_list; produces the list of integers from 1 to 1001 (obviously a single string). real

Re: "put" vs "say"

put is meant for machines, while say is meant for humans. this is implemented by having say call the .gist method and put calling the .Str method. Try using say and put on a list of a thousand elements or more and you'll see what I mean. HTH   - Timo On 21/10/2018 18:29, Parrot Raiser wrote: >

"put" vs "say"

"put" and "say" seem to be redundant, but I'm sure there's a good reason for having 2 output commands. Would anyone care to comment on how they differ and why, or point to an explanation?

Re: "temp" vs "my"

What you want is OUTER ... my $v = "original"; > { > my $v = OUTER::<$v>; > say $v; > $v = "new one"; > say $v; > } > say $v; It's how you access the outer scope from an inner scope. -Scott On Wed, Oct 3, 2018 at 1:10 AM yary wrote: > Reading and playing with

Re: "temp" vs "my"

Note that OUTER::<$v> only goes up one level. So to go up two levels OUTER::OUTER::<$v> There is also OUTERS::<$v> which will go up as many levels as it needs to find the variable { my $a = 1; my $b = 2; { my $a = 3; { say

Re: "temp" vs "my"

Thanks! Knew I'd seen the concept of OUTER but couldn't remember the keyword. -y On Wed, Oct 3, 2018 at 5:51 AM, Timo Paulssen wrote: > you can refer to the outer $v as OUTER::('$v'), that ought to help :) > On 03/10/2018 08:10, yary wrote: > > Reading and playing with

Re: "temp" vs "my"

you can refer to the outer $v as OUTER::('$v'), that ought to help :) On 03/10/2018 08:10, yary wrote: > Reading and playing with https://docs.perl6.org/routine/temp > > There's an example showing how temp is "dynamic" - that any jump > outside a block restores the value. All well and good. > >

"temp" vs "my"

Reading and playing with https://docs.perl6.org/routine/temp There's an example showing how temp is "dynamic" - that any jump outside a block restores the value. All well and good. Then I thought, what if I want a lexical temporary value- then use "my"- and this is all well and good: my $v =

Re: $? and $! equivalents

OK, different paradigm, different methods. Thanks. Another couple of entries for the "differences" list? Even a note the thing doesn't exist saves fruitless further searching. On 9/14/18, Brad Gilbert wrote: > On Fri, Sep 14, 2018 at 5:08 PM Parrot Raiser <1parr...@gmail.com> wrote: >> >> This

Re: $? and $! equivalents

On Fri, Sep 14, 2018 at 5:08 PM Parrot Raiser <1parr...@gmail.com> wrote: > > This is probably going to be a forehead-slapper, but I can't find a > reference in either perlintro.com or http://docs.perl6.org/ > (5to6-perlfunc or top-down) for the equivalents of $? and $! in > P6.What are they? > >

Re: $? and $! equivalents

Magic variables make multiple threads impossible, which is why perl 5 is stuck with ithreads: what happens if two threads each "run" something at around the same time? In Perl 6, you have a Proc object for each subprocess, and can query it for its status and/or result code; for things like sub

$? and $! equivalents

This is probably going to be a forehead-slapper, but I can't find a reference in either perlintro.com or http://docs.perl6.org/ (5to6-perlfunc or top-down) for the equivalents of $? and $! in P6.What are they? I want to be able to "run" or "shell" programs, then examine return codes and errors.

Re: 3 kinds of yadda

When executed: - ??? is warn.- ... is fail. - !!! is ‘die`. Otherwise, they’re identical (notably, when *not* executed, which is the usual case). You’d use ??? when you’re not implementing something yet but it needs to be callable (say, a debugging function). Given the difference in

Re: 3 kinds of yadda

Semantically !!! is "if control flow hits here, it's an error" ... is "The implementation is elsewhere, or this is not yet implemented" at least that's my impression -y On Mon, Sep 10, 2018 at 12:04 PM, Parrot Raiser <1parr...@gmail.com> wrote: > There are 3 kinds of yadda, yadda operator: >

Re: 3 kinds of yadda

> Bash is treating ! as the history substitution character, and either erroring > out or substituting a previous command line. Thanks; that struck me between the time I hit send and got confirmation. :-)*

3 kinds of yadda

There are 3 kinds of yadda, yadda operator: !!! dies with a message: Stub code executed in block at yad1 line 2 ... dies with an identical message ??? produces the message, but continues operating. The only difference I can find between !!! and ... is that !!! produces bizarre behaviour

Re: 3 kinds of yadda

Bash is treating ! as the history substitution character, and either erroring out or substituting a previous command line. ^ has related behavior at the start of a line. ... is specially recognized by the compiler, for example treating a class stubbed with ... as a forward declaration. I don't

3 kinds of yadda

There are 3 kinds of yadda, yadda operator: !!! dies with a message: Stub code executed in block at yad1 line 2 ... dies with an identical message ??? produces the message, but continues operating. The only difference I can find between !!! and ... is that !!! produces bizarre behaviour

Reading documentaion offline?

What's the simplest way of downloading current language documentation for reading offline?

Best practices?

What would be the criteria for deciding whether to name P6 constants using lower-case or UPPER_CASE names? Generally, system constants and variables use upper-case, so lower-case keeps user variables in a separate name space. Do user-defined constants belong there, or in upper-case to indicate

[perl6/specs] 26266b: Update builder example to use full namespace

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 26266b1bc69cd15b58ab03338af7f3938052b666 https://github.com/perl6/specs/commit/26266b1bc69cd15b58ab03338af7f3938052b666 Author: Nick Logan Date: 2018-08-11 (Sat, 11 Aug 2018) Changed paths: M

Announce: Rakudo Star Release 2018.06

On behalf of the Rakudo and Perl 6 development teams, I'm pleased to announce the June 2018 release of "Rakudo Star", a useful and usable production distribution of Rakudo Perl 6. The tarball for this release is available from . Binaries for macOS and

[perl6/specs] b08407: s/concatenated/appended/

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: b08407beaae81a63dd7fcbf565dad0fcd44b1b1f https://github.com/perl6/specs/commit/b08407beaae81a63dd7fcbf565dad0fcd44b1b1f Author: Elizabeth Mattijsen Date: 2018-05-22 (Tue, 22 May 2018)

Re: Is negative lookbehind behaving here?

Yes, you've encountered a bug. It's got these two tickets: https://rt.perl.org/Public/Bug/Display.html?id=124898 https://rt.perl.org/Public/Bug/Display.html?id=131964 I've got a branch in nqp and rakudo that I'll merge very soon that fixes both of these bugs. Until then you can switch $ and ^,

Is negative lookbehind behaving here?

I want to match something anywhere but at the end of a string in one example, or anywhere but at the start of a string in another example. The "except at start" one has me stumped. Not sure if it's me or if I've tickled a bug. perl6 --version This is Rakudo Star version 2018.01 built on MoarVM

[perl6/specs] cde208: Tweak line number shower

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: cde208bde0f432ee496dabbe556a473c2aa2fcbd https://github.com/perl6/specs/commit/cde208bde0f432ee496dabbe556a473c2aa2fcbd Author: Zoffix Znet Date: 2018-03-20 (Tue, 20

[perl6/specs] 690bf9: Show line number anchors on hover

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 690bf9b60e2a375733ce5508c6aa4cf4999be6af https://github.com/perl6/specs/commit/690bf9b60e2a375733ce5508c6aa4cf4999be6af Author: Zoffix Znet Date: 2018-03-20 (Tue, 20

Re: (default) Real->Rat precision should match what compiler uses for literals

I want an epsilon that doesn't confuse newbies and which also is efficient. epsilon=1/2**(mantissa bits-1) fits the bill. Why I want this- It would be great to have numbers survive round-trip conversions, when feasible. Specifically I have no need to compare Rats and Nums for equality, but I do

Re: (default) Real->Rat precision should match what compiler uses for literals

On Sun, Mar 4, 2018 at 8:49 AM, yary wrote: > In that spirit, I'd expect numeric comparison in general, and epsilon > specifically, to be set so these return True: > > > pi == pi.Rat # Does Num to Rat conversion keep its precision? > False > > pi.Str.Num == pi # Does Num

Re: (default) Real->Rat precision should match what compiler uses for literals

The point of Rats is making Perl6 more correct and less surprising in common cases, such as $ perl6 > 1.1+2.2 3.3 > 1.1+2.2 == 3.3 True > 1.1+2.2 != 3.3 False vs any language using binary floating-point arithmetic DB<1> p 1.1+2.2 3.3 DB<2> p 1.1+2.2 == 3.3 DB<3> p 1.1+2.2 != 3.3 1 In

Re: (default) Real->Rat precision should match what compiler uses for literals

On Sat, Mar 3, 2018 at 3:32 PM, yary wrote: > Or instead of 1/2**(32 or 64), re-asking these questions about epsilon: > > " Why so large? > >Why not zero? " > > What's justification for using 1/100,000 vs. something smaller vs. 0 "max > possible precision?" > The

Re: (default) Real->Rat precision should match what compiler uses for literals

Max precision rapidly becomes more memory requires than your computer has. On Sat, Mar 3, 2018 at 3:32 PM, yary wrote: > Or instead of 1/2**(32 or 64), re-asking these questions about epsilon: > > " Why so large? > >Why not zero? " > > What's justification for using

Re: (default) Real->Rat precision should match what compiler uses for literals

Still thinking this out. Does the default epsilon influence a Rat == Float comparison? If so, for that purpose, the most useful epsilon is one that maximizes its correctness.

Re: (default) Real->Rat precision should match what compiler uses for literals

Or instead of 1/2**(32 or 64), re-asking these questions about epsilon: " Why so large? Why not zero? " What's justification for using 1/100,000 vs. something smaller vs. 0 "max possible precision?"

Re: (default) Real->Rat precision should match what compiler uses for literals

Zeroing in on one point: > > A solution might be to instead provide a pragmatic, rather than > mathematical > > parameter: > > > > :$numbits = 64 > > > > This would say to keep as much precision as possible while making the > result > > fit in 64 bits. For example 2.147483647e0.Rat would

Re: (default) Real->Rat precision should match what compiler uses for literals

On Fri, Mar 2, 2018 at 4:33 PM, Jim Avera wrote: > Hello, > > Using Rakudo 2018.01: > > my Rat $rat-from-literal = 1.23456789; > my Rat $rat-from-str = "1.23456789".Rat; > my Real $real = 1.23456789e0; > my Rat $rat-from-real= $real.Rat;

Re: Naming debate- what's the location for it?

FWIW, Jupyter can also be used with Perl 6, though surely we ought to advertise it more broadly.

Re: Naming debate- what's the location for it?

While I am not an expert in R, My observation about the specific features that I use often in R and its equivalence in Perl is as follows. - The *apply functions, Technically it is similar to Perl's map/grep and friends. - Magrittr: Perl5 has no equivalent function, Perl6 has the pipe

Re: Naming debate- what's the location for it?

A bit of a digression around marketing/evangelizing > When I wanted to learn DataScience, courses using R and Python were > readily available. Even though I had been using Perl for 20 years, I did > not even know where to start in the Perl ecosystem! > I've wondered why PDL isn't more popular,

RE: Naming debate- what's the location for it?

Thank you for your insightful comment Vijay. You’re right. Perl6’s evangelists will typically be current Perlers who are running up against Perl5’s limitations. So I think you’ve circumscribed the issue: what is Perl6 for? * Perl6 could be “better than Go” for microservices – IF it’s

Re: Naming debate- what's the location for it?

Marketing is not only about branding. It is also about finding Evangelists. Perl's traditional base was in - Web Development, - Text Processing, - Bio-Informatics and - As a general glue language among the sys admin and EDA community. How many of these sectors are moving away or have

Re: A proposal for Perl's branding - let's free all the butterflies

On 2018-02-16 11:15 AM, Nigel Hamilton wrote: Here is a suggestion for Perl's branding: http://nigelhamilton.com/perl-branding-proposal.html I like your proposal. But its details would need fleshing out more, particularly at the end, where it says this: Perl

A proposal for Perl's branding - let's free all the butterflies

Here is a suggestion for Perl's branding: http://nigelhamilton.com/perl-branding-proposal.html

Re: Naming debate- what's the location for it?

I'm about to publish some blog posts with using Perl 6 to demonstrate some cryptographic primitives. I was thinking about calling it "rakudo" to at least intrigue people and make them google it. Couldn't we call the language rakudo and the implementation nqp-rakudo? (ie a rakudo implementation in

Re: Naming debate- what's the location for it?

Another 2 or 3 pennies^1 worth of strawman proposing / bikeshedding / flight of marketing fancy about naming etc: Perl's Rapture === Imagine we officially embarked on a year+ long communal process in which we (TPF and Perl community) sort out branding and marketing of Perlish languages.

Re: Naming debate- what's the location for it?

Don't type here. On 2018-02-10 05:16, Parrot Raiser wrote: On 2/10/18, Darren Duncan wrote: I think if we want to keep "Perl" in the name we should use "C" as a precedent. Other related languages keeping "C" include "Objective C", "C#", "C++", Perl++ would work.

Re: Naming debate- what's the location for it?

On 2/10/18, Darren Duncan wrote: > I think if we want to keep "Perl" in the name we should use "C" as a > precedent. > Other related languages keeping "C" include "Objective C", "C#", "C++", > > Perl++ would work.

Re: Naming debate- what's the location for it?

Ok. So here is something revolutionary. Free up "Perl 6" for a future generation of Perl 5 and remove the ceiling on the perl 5 language. Perl 6 has become more than a major iteration, hasn't it? Perl on parrot Perl on jam Perl on mono Lots of space for a five from six once you vacate the lot.

RE: Naming debate- what's the location for it?

I think a name change is too radical. And yet. I think Steve has a point, though I don’t know what to do about it. The developers in my little corner of the world may not be up on the new-language-of-the-week, but even they see Perl as a has-been, write-only language, so when their brain

Re: Naming debate- what's the location for it?

Thought the conversation felt like bikeshedding but... My point still stands. This is a new language targetted at a post php world. The significance of a version number will be lost outside the perl echo chamber and in that context seen as baggage... IMHO... YMMV... On 9 Feb 2018 6:15 pm, "Lucas

Re: Naming debate- what's the location for it?

I doubt the name is "up for discussion" just because there's a blog post about it. The name ain't changing ever, or at least that's how I understand things. But, please, feel free to correct me if I'm wrong. Sure, you can have as many alternative nicknames and aliases as you want (for marketing

Re: Naming debate- what's the location for it?

Looking at possible candidates from a search-engine results and alternative manings test. some possible choices: Mu, (the root object class), Camelia, (the spokesbug taking over), Shesh, (the female form of 6 in Hebrew, but unfortunately also in the Urban Dictionary - look it up for yourself).

Re: Naming debate- what's the location for it?

Well, for what it's worth, as an outsider - IMHO, leaving "perl" behinds a good thing. Love it or loath it, we live in a js/python/jvm leaning world. Perl was great, but it's dated. Why have the baggage? Rakudo is a new language. Treat it as such - best hope for it. In layman's terms an informal

Re: Naming debate- what's the location for it?

My personal favorite resolution is to officially name the language Rakudo, full stop. The implementation that was/is using the name would be renamed to something else so it isn't the same as the language. Then we say "Rakudo" is a sibling language of "Perl", full stop. Then "Perl 6" becomes

RE: Naming debate- what's the location for it?

* What's the counter word for computer languages, anyway? -mai? As an abstraction from paper printouts? From: Brent Laabs [mailto:bsla...@gmail.com] Sent: Thursday, February 08, 2018 2:51 PM To: Aaron Sherman Cc: yary ; Perl6

Re: Naming debate- what's the location for it?

Just Mu would be an amusing Perlish pun based on Muttsu... Making the interpretation either Perl "six" or Perl "most undefined". I like yary's idea too. Frankly, if Perl had an identity, I would not care about the name. I feel like it lacks that right now. -- Aaron Sherman, M.: P:

Re: Naming debate- what's the location for it?

Thanks for the summary of the high points, as there were a large number of low points in previous discussions. Roku is not the only reading for 六 in Japanese, the kun reading is muttsu. So we could become Mupperl. What's the counter word for computer languages, anyway? On Thu, Feb 8, 2018 at

  1   2   3   4   5   6   7   8   9   10   >