mauke

I agree that the error message is bad. However, `Missing "$" sign` is not correct either, as your program could be made to parse by just adding more code at...

https://gitlab.haskell.org/ghc/ghc/-/issues/25077 seems to have been resolved.

FWIW, my implementation at https://metacpan.org/pod/Quote::Code goes with interpretation 2. It recursively parses embedded code blocks as it scans through the string. This is different from how perl does things, but...

@tonistiigi > `.dockerignore` only applies to transferring local files from client to the daemon. We should make it clear in the docs if it isn't already. Oh, the docs are...

The very first sentence: > Joins the separate **strings** of LIST into a single **string** with fields separated by the value of EXPR, and returns that new **string**. Mentions both...

It's still broken with `-l`. `try.pl`: ```perl use v5.38; say __LINE__; ``` Correct output: ``` $ perl try.pl 3 $ perl -MO=Deparse try.pl | perl try.pl syntax OK 3 ```...

> Consider part of a test script along the lines of: > > { > use warnings; > my ($w, $x, $y); > local $SIG {__WARN__} = sub { $w...

The space is immaterial. As far as C is concerned, `char**e` and `char * * e` are the same token sequence and are parsed the same way.¹ I think this...

This is a typemap error. I haven't bisected it, but I strongly suspect commit 2f4409bf707ec51: > Use alert control character as quoting character in INPUT templates > > This way,...

- `op.c` - `Perl_newATTRSUB_x` Looks like it still treats `'` specially: ```c || memchr(name, ':', namlen) || memchr(name, '\'', namlen) ``` - `op.c` - `Perl_ck_method` This code should go: ```c...