On Wednesday, July 21, William Michels wrote:
> Sorry for my continuing confusion, but I don't see any use-case for an
> "unspace" at the end of a line in the Raku REPL, or the Jupyter
> kernel.
A use case would be for instance, wanting to call a method
on the next line -- so wanting to unspace
Dear Brian,
Thank you for your analysis! I am particularly intrigued by your
Jupyter comment:
"Note that this is not the same as the raku 'unspace' -- a backslash
followed by a newline will be replaced with a newline before the code
is executed. To create an unspace at the end of the line, you
On Monday, July 19, William Michels via perl6-users wrote:
> I don't see how the Raku REPL knows how to cycle from taking input at its
> prompt and moving to the read/evaluate step.
This currently happens when the parser throws one of these exceptions:
X::Syntax::Missing
X::Comp::FailGoal
Hi Rob!
Thanks for the reply. So what you're saying is the "backslash-newline"
combination tells the REPL that it has received incomplete input? Otherwise
I don't see how the Raku REPL knows how to cycle from taking input at its
prompt and moving to the read/evaluate step.
I took a quick look at
On Wed, Jul 14, 2021 at 08:40:07AM -0700, William Michels via perl6-users wrote:
> > \
> {}
> > \\
> {}
> > \\\
> {}
> Curiously, I seem to create an object in my REPL environment when I enter
> either a single-, double-, or triple-backslash. ...
Your backslash destroys the newline so the
Hi, I've recently updated my Rakudo installation, and I wanted to test
multi-line input in the REPL. By mistake I entered a backslash at the REPL
command line:
user@mbook:$ raku
Welcome to 퐑퐚퐤퐮퐝퐨™ v2021.06.
Implementing the 퐑퐚퐤퐮™ programming language v6.d.
Built on MoarVM version 2021.06.
To
