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: 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

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

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.)

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: "put" vs "say"

e and > you'll see what I mean. > > HTH >   - Timo > > On 21/10/2018 18:29, Parrot Raiser wrote: >> "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? >

"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: $? 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...@

$? 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

> 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

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

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?

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).

Documentation for error messages

Where's the best current description of error messages from file "open" commands, and how to control them? (I'm thinking of things like the effect of adding "\n" to "die" messages in P5.)

Re: Is this a bug?

n, Sep 18, 2016 at 16:49 Parrot Raiser <1parr...@gmail.com> wrote: > > say { $_ } was the correct thing to use there. (I'm trying to avoid >> any mention of O-O for the moment.) >> > “Trying to avoid any mention of O-O” seems like a Perl 6 obfuscation or > golf

This seems to be wrong

This code: #! /home/guru/bin/perl6 # Ask for some numbers from 1 - 7 # and verify that they are in range my @names = < fred betty barney dino wilma pebbles bamm-bamm >; my @inputs = lines(); for @inputs { if $_ ~~ 1..7 { say @names[$_-1]; } else { say "$_ out of

Is this a bug?

This code: 1 #! /home/guru/bin/perl6 2 3 # Ask for some lines and output them in reverse 4 # Work out the appropriate EOF symbol for the OS 5 6 my $EOF = "CTRL-" ~ ($*DISTRO.is-win ?? "Z" !! "D"); 7 8 say "Please enter some lines and end them with $EOF"; 9 10 say { for reverse lines() {} }; 11 12

Re: Justification for the "reversed" instruction format

-4850 >> >> >> >> On Tue, Sep 6, 2016 at 12:51 PM, Aaron Sherman <aaronjsher...@gmail.com> >> wrote: >> >>> >>> >>> $ perl6 -e 'my @numbers = 1..100; say [-] @numbers; say [R-] @numbers' >>> -5048 >>> -4850 >&

Help mechanism in REPL?

This isn't a request for a feature, merely a thought experiment. We're still in the phase where it's more important to ensure that existing features work properly than add new ones. How difficult would it be to include a mechanism within the REPL to select either documentation or an example,

Justification for the "reversed" instruction format

I've just stumbled across "reversed operators", e.g. say 4 R/ 12; # 3 in the documentation. I'm curious to know why the language includes them? I'm having trouble understanding where they would be useful.

Re: Exploit the versioning (was Re: Backwards compatibility and release 1.0)

Is this particular change one that could be implemented algorithmically, or at least partially so? (E.g. For all modules check for the presence of a ":D". If it's there, no action. If not, insert a line of code. Run a test. If successful, post change. If not, alert a

Does Perl 6 use $a and $b in sorting?

Because of the the special significance of $a and $b in Perl 5's sort comparison, I always avoid using the names in examples, lest it set a booby-trap for later. I've noticed "a" and "b' being used in some P6 examples. Are they no longer significant, or are they just a poor choice of identifier?

Re: Language design

2015 at 10:32, Michael Zedeler mich...@zedeler.dk wrote: On 06/12/15 15:54, Parrot Raiser wrote: Has somebody been following the discussions on types? http://xkcd.org/1537/ :-)* Perl6 has something similar to example 9. Ranges, hyper-operators as well as the invocation operators

Language design

Has somebody been following the discussions on types? http://xkcd.org/1537/ :-)*

Synopses size and revision state

Without doing too much work, can anyone offer an estimate of the volume of the Perl 6 Synopses? I'm assuming that by now, they are unlikely to undergo serious modification. I'm trying to estimate the cost of rendering them to dead-tree versions for study. (Personal limitation; I can look up a

Re: Jargon

On 6/13/14, Will Coleda w...@coleda.com wrote: See: https://github.com/perl6/specs/blob/master/S99-glossary.pod which is nicely formatted here: http://perlcabal.org/syn/S99.html Great, thanks. Looks as though I was late, not premature.

Jargon

As typically happens with any complex project, Perl 6 development has produced a jargon that is almost impenetrable to outsiders. (It's mostly on top of general Perl parlance, with some CS insertions.) In order to explain 6 to the world in general, a Rosetta Stone is going to be necessary. The

Re: [perl6/specs] 89cc32: Spec Bag.kxxv

1. For the last few years almost all discussion is entirely on #perl6. Which seems to be working extremely well...just not for me. I can't manage to track these discussions (even via the logs). I find the interleaving of multiple threads utterly impossible to cope with. Thank you for saying

Re: Defining Perl 6 for the masses

Minor corrections: may smply be my personal limitations). s/smply/simply/ dumb noob questions. By my fairly harsh definition. with the sage of IBM's attempt to develop One Language To Rule Them All, s/sage/saga/

Defining Perl 6 for the masses

This is related to the conversation on the Synopses, but its sufficiently different that it probably justifies its own thread. I want to start by making it clear that I'm not criticising the design of Perl 6, or any of the people working so hard to make it great. I'm just trying to address what I

Re: Commensurability as Key

Let's get the basics nailed down and working so that we can learn them, before wandering any further into theoretical CS. On 8/18/13, James Bowery jabow...@gmail.com wrote: Of the two key conceptual gaps in current programming language philosophy -- commensurability and change propagation --

Re: Perl 6 in Perl 6?

On Thu, Oct 18, 2012 at 3:59 AM, Moritz Lenz mor...@faui2k3.org wrote: The priorities for most compiler hackers is to provide good compilers over complete bootstrapping, and I guess most users agree with that goal. Agreed. I'm most concerned about a reliable and consistent set of features

The Secret of a Successful Programming Language? A Really Great Beard

http://www.wired.com/wiredenterprise/2012/06/beard-gallery Maybe we should ask Larry to give up shaving for a while?

Re: The trouble with awesome

On Mon, Jun 4, 2012 at 12:01 AM, Peter Scott pe...@psdt.com wrote: We need multiple paths.  The term beginner creates problems I meant beginner with respect to Perl 6, but I think that Peter basically paraphrased my arguments about the problem. Although programming experience is an important

Re: The trouble with awesome

On Wed, May 30, 2012 at 6:00 AM, Moritz Lenz mor...@faui2k3.org wrote: I'd still start with simple script files, because that's what most programmers are most familiar with. I'd do them in Huffman order; the interpreter involves the least typing to start, and it's useful for demonstrating

Re: The trouble with awesome

There are a lot of programmers who know several programming languages already, and who don't want to read a whole page on how to print 'Hello World', 5 pages on if-statements and while-loops and another 10 pages explaining lists and iteration. However experienced a programmer may be,

The trouble with awesome

Perl 6 is awesome. Its design is based on the combined experience of many clever people. It addresses a whole range of contemporary computing problems, in fields as diverse as text processing and compiler development. It's being developed by, and for, some of the smartest people I want to risk

Re: [perl6/specs] a7cfe0: [S32] backtraces overhaul

S19 uses hyphens for all of perl6's long-form command-line flags. Command-line flags and methods are separate sets. Hyphens would be the norm for flags. In S28, we find $*EXECUTABLE_NAME and %*META-ARGS listed within 10 lines of each other. S32-setting-library_IO.pod and

Close($file) required in Perl 6, unlike Perl 5

The following program: my $skeleton = bones\n; my $new_file = grave; my $handle = open($new_file, :w); $handle.print($skeleton); opens the grave file, but leaves it empty. A last line: close($handle);# close() generates an error message. is required to get any contents in the file,

Bug?

When a subroutine is invoked with an empty parameter list, as follows: run_stuff(); sub run_stuff { my ($parm) = @_; say Parameter is $parm; } @_[0] contains Any(). Should it?

Re: CPAN -- moving forward

Part of the tension here may be coming from the attempt to debate too many levels of structure at once. One of the common factors that has contributed to the longevity of Unix (in the generic sense), and the Internet, is their layered architectures. The kernel does its thing, the shell sits on