Re: [perl #133541] Grammer bug vs

"_" is not an alphabetic character. It's allowed in "alnum" because that is by intent what is \w in other regex implementations, which includes "_". On Thu, Sep 27, 2018 at 10:47 PM Vijayvithal wrote: > # New Ticket Created by Vijayvithal > # Please include the string: [perl #133541] > # in

Re: [perl #133541] Grammer bug vs

"_" is not an alphabetic character. It's allowed in "alnum" because that is by intent what is \w in other regex implementations, which includes "_". On Thu, Sep 27, 2018 at 10:47 PM Vijayvithal wrote: > # New Ticket Created by Vijayvithal > # Please include the string: [perl #133541] > # in

Re: [perl #127682] [OSX] writing more than 8192 bytes to IO::Handle causes it to hang forever

And in the cases where it "works", the buffer is larger. Which runs the risk of consuming all available memory in the worst case, if someone tries to "make it work" with an expanding buffer. The fundamental deadlock between processes blocked on I/O is not solved by buffering. Something needs to

Re: [perl #127682] [OSX] writing more than 8192 bytes to IO::Handle causes it to hang forever

And in the cases where it "works", the buffer is larger. Which runs the risk of consuming all available memory in the worst case, if someone tries to "make it work" with an expanding buffer. The fundamental deadlock between processes blocked on I/O is not solved by buffering. Something needs to

Re: [perl #132441] [SEVERE][WINDOWS][IO] IO::Handle.read-internal cannot handle fancy Unicode chars on TTY handles

On Tue, Dec 26, 2017 at 12:15 AM, Brandon Allbery via RT < perl6-bugs-follo...@perl.org> wrote: > IIRC this is known, and not really fixable. It's not even cmd.exe but a > Windows console mode limitation. > Come to think of it, there should be existing mention of this on the moa

Re: [perl #132441] [SEVERE][WINDOWS][IO] IO::Handle.read-internal cannot handle fancy Unicode chars on TTY handles

On Tue, Dec 26, 2017 at 12:15 AM, Brandon Allbery via RT < perl6-bugs-follo...@perl.org> wrote: > IIRC this is known, and not really fixable. It's not even cmd.exe but a > Windows console mode limitation. > Come to think of it, there should be existing mention of this on the moa

Re: [perl #132441] [SEVERE][WINDOWS][IO] IO::Handle.read-internal cannot handle fancy Unicode chars on TTY handles

On Mon, Dec 25, 2017 at 1:07 AM, Zoffix Znet via RT < perl6-bugs-follo...@perl.org> wrote: > On Thu, 16 Nov 2017 09:53:46 -0800, c...@zoffix.com wrote: > > On 2017.07 on Win7 with 65001 code page enabled, the » char doesn't > > show up at all. Just seems to get removed from the content if I paste

Re: [perl #132441] [SEVERE][WINDOWS][IO] IO::Handle.read-internal cannot handle fancy Unicode chars on TTY handles

On Mon, Dec 25, 2017 at 1:07 AM, Zoffix Znet via RT < perl6-bugs-follo...@perl.org> wrote: > On Thu, 16 Nov 2017 09:53:46 -0800, c...@zoffix.com wrote: > > On 2017.07 on Win7 with 65001 code page enabled, the » char doesn't > > show up at all. Just seems to get removed from the content if I paste

Re: [perl #132283] [REGRESSION] BUILDALL is listed as one of the methods, maybe that's not right (say $foo.^methods)

On Sat, Oct 21, 2017 at 12:12 PM, Brad Gilbert via RT < perl6-bugs-follo...@perl.org> wrote: > On Sat, 21 Oct 2017 08:18:46 -0700, alex.jakime...@gmail.com wrote: > > https://irclog.perlgeek.de/perl6-dev/2017-10-21#i_15334639 > > > > I' think we should test that both are listed, and we can close

Re: [perl #132283] [REGRESSION] BUILDALL is listed as one of the methods, maybe that's not right (say $foo.^methods)

On Sat, Oct 21, 2017 at 12:12 PM, Brad Gilbert via RT < perl6-bugs-follo...@perl.org> wrote: > On Sat, 21 Oct 2017 08:18:46 -0700, alex.jakime...@gmail.com wrote: > > https://irclog.perlgeek.de/perl6-dev/2017-10-21#i_15334639 > > > > I' think we should test that both are listed, and we can close

Re: [perl #132302] Str.trans grabs callers $/ for unknown reason

On Sat, Oct 14, 2017 at 1:15 PM, Zoffix Znet wrote: > 2) Why does Str.trans grabs caller's $/ in the first place? The commit > that added >it seems to claim to fix something that isn't meant to work as tr/// > replaces per >char and doesn't use special regex

Re: [perl #132302] Str.trans grabs callers $/ for unknown reason

On Sat, Oct 14, 2017 at 1:15 PM, Zoffix Znet wrote: > 2) Why does Str.trans grabs caller's $/ in the first place? The commit > that added >it seems to claim to fix something that isn't meant to work as tr/// > replaces per >char and doesn't use special regex

Re: [perl #132268] Floating point anomalies

On Fri, Oct 13, 2017 at 4:59 AM, wrote: > It's bad enough that perl5 and perl6 round to 15 decimal digits of > precision, but at least perl5's printf will give me 17 decimal digits when > I ask it to (and I think perl6 should do the same): > I am wondering if youve

Re: [perl #132268] Floating point anomalies

On Fri, Oct 13, 2017 at 4:59 AM, wrote: > It's bad enough that perl5 and perl6 round to 15 decimal digits of > precision, but at least perl5's printf will give me 17 decimal digits when > I ask it to (and I think perl6 should do the same): > I am wondering if youve

Re: [perl #132268] Floating point anomalies

On Thu, Oct 12, 2017 at 5:31 AM, wrote: > Perl6's printf() function looks a little suspect - though I might be > missing > something here. > > As with perl5's say function, doubles are rounded to 14 decimal digits of > precision, so we get: > > $ perl6 -e 'say

Re: [perl #132242] [BUG] Proc::Async running with yes command returns superfluous output and hangs

On Sat, Oct 7, 2017 at 10:21 PM, Itsuki Toyota wrote: > See the following result: > > $ perl6 -e 'my $proc = Proc::Async.new("yes"); > $proc.stdout.head(1).tap(); await $proc.start;' > > y > y > y > y > y > y > y > y > ... > > > I think tap() should output just a

Re: [perl #132242] [BUG] Proc::Async running with yes command returns superfluous output and hangs

On Sat, Oct 7, 2017 at 10:21 PM, Itsuki Toyota wrote: > See the following result: > > $ perl6 -e 'my $proc = Proc::Async.new("yes"); > $proc.stdout.head(1).tap(); await $proc.start;' > > y > y > y > y > y > y > y > y > ... > > > I think tap() should output just a

Re: [perl #126757] [LTA] error message talks about ~ but there is no ~ in my code (33..126 .pick.chr)

Is it possible to signal to the error handler that it is talking about a value somewhere instead of the program source, at least? Even if you can't reasonably say what value where? On Sat, Oct 7, 2017 at 5:18 PM, Aleks-Daniel Jakimenko-Aleksejev via RT < perl6-bugs-follo...@perl.org> wrote: >

Re: [perl #132194] $*PROGRAM-NAME is not assignable / does not change process's name

On Sun, Oct 1, 2017 at 12:35 PM, Zoffix Znet wrote: > $*PROGRAM-NAME is supposed to be a replacement for Perl 5's $0, but it > doesn't work that way. > > What I'd expect to work: > > use v6; > $*PROGRAM-NAME = 'foo'; > This is not portable and not reliable ---

Re: [perl #132194] $*PROGRAM-NAME is not assignable / does not change process's name

On Sun, Oct 1, 2017 at 12:35 PM, Zoffix Znet wrote: > $*PROGRAM-NAME is supposed to be a replacement for Perl 5's $0, but it > doesn't work that way. > > What I'd expect to work: > > use v6; > $*PROGRAM-NAME = 'foo'; > This is not portable and not reliable ---

Re: [perl #132185] [LTA] file tests and Failure do not interact as expected

On Sat, Sep 30, 2017 at 4:35 PM, Sam S. via RT wrote: > To the extent that you're basing your expectations on the fact that a Perl > 5 `undef` can be used in ways that a Perl 6 `Failure` cannot (without > blowing up), well, that's just a matter of having to unlearn

Re: [perl #132185] [LTA] file tests and Failure do not interact as expected

On Sat, Sep 30, 2017 at 4:35 PM, Sam S. via RT wrote: > To the extent that you're basing your expectations on the fact that a Perl > 5 `undef` can be used in ways that a Perl 6 `Failure` cannot (without > blowing up), well, that's just a matter of having to unlearn

Re: [perl #132148] [RFC] native 'str' type unspecced, undocumented, and ill-defined

Possibly the right thing here is for perl 6 to reserve the name for implementations, and otherwise leave it unspecced. -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs,

Re: [perl #132148] [RFC] native 'str' type unspecced, undocumented, and ill-defined

Possibly the right thing here is for perl 6 to reserve the name for implementations, and otherwise leave it unspecced. -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs,

Re: [perl #132156] [LTA] Suggest polymod for bases > 36 (9123607.base(37))

On Mon, Sep 25, 2017 at 10:53 AM, Aleks-Daniel Jakimenko-Aleksejev via RT < perl6-bugs-follo...@perl.org> wrote: > * add a named arg for the alphabet, so that the user can provide any > character > set he wants > I'm in favor of the original suggestion: point the user to polymod. One way that is

Re: [perl #132156] [LTA] Suggest polymod for bases > 36 (9123607.base(37))

On Mon, Sep 25, 2017 at 10:53 AM, Aleks-Daniel Jakimenko-Aleksejev via RT < perl6-bugs-follo...@perl.org> wrote: > * add a named arg for the alphabet, so that the user can provide any > character > set he wants > I'm in favor of the original suggestion: point the user to polymod. One way that is

Re: [perl #132035] AutoReply: [LTA] temp on an undeclared dynamic variable produces a not very helpful error

Or maybe it's not that tricky after all; seems the Failure is actually a useful one (X::Dynamic:NotFound), so introspection of the Failure would reveal the issue. -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com

Re: [perl #132035] AutoReply: [LTA] temp on an undeclared dynamic variable produces a not very helpful error

Or maybe it's not that tricky after all; seems the Failure is actually a useful one (X::Dynamic:NotFound), so introspection of the Failure would reveal the issue. -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com

Re: [perl #132030] [REGRESSION] Broken Text::CSV tests and possibly other ecosystem fallout

On Tue, Sep 5, 2017 at 5:40 AM, jn...@jnthn.net via RT < perl6-bugs-follo...@perl.org> wrote: > Failing to close output handles has been clearly documented (and yes, > documented well before the recent buffering change) as something that can > cause data loss. Default output buffering just makes

Re: [perl #132030] [REGRESSION] Broken Text::CSV tests and possibly other ecosystem fallout

On Tue, Sep 5, 2017 at 5:40 AM, jn...@jnthn.net via RT < perl6-bugs-follo...@perl.org> wrote: > Failing to close output handles has been clearly documented (and yes, > documented well before the recent buffering change) as something that can > cause data loss. Default output buffering just makes

Re: [perl #131965] Shaped arrays can't have zero size

> Well, what do you mean? Of course you can't put anything into it, and any > attempt to index it will throw. It may seem useless, however, if you can > have > an empty array, why can't you have a shaped empty array? > Only if all dimensions are unindexable. Otherwise you have something with

Re: [perl #131965] Shaped arrays can't have zero size

How exactly do you index such an array? On Sat, Aug 26, 2017 at 8:11 PM, Aleks-Daniel Jakimenko-Aleksejev via RT < perl6-bugs-follo...@perl.org> wrote: > Indeed. The limit was introduced as a response to this ticket: > https://rt.perl.org/Ticket/Display.html?id=126800 > The check is probably too

Re: [perl #131877] [LTA] better error message for exit("hello")

At some point, one has to accept that this language is not Python, not call for one's favorite Python-isms to be incorporated into the core regardless of how it might interact with what is already there. On Thu, Aug 10, 2017 at 8:12 AM, Aleks-Daniel Jakimenko-Aleksejev via RT <

Re: [perl #131877] [LTA] better error message for exit("hello")

At some point, one has to accept that this language is not Python, not call for one's favorite Python-isms to be incorporated into the core regardless of how it might interact with what is already there. On Thu, Aug 10, 2017 at 8:12 AM, Aleks-Daniel Jakimenko-Aleksejev via RT <

Re: [perl #131801] Stranded strings with combiners or ZWJ on borders break my NFG expectations ( (“\x[0305]a” x 2).chars.say )

Combining chars look forward now? This breaks *my* expectations. On Wed, Jul 26, 2017 at 6:36 AM, Aleks-Daniel Jakimenko-Aleksejev < perl6-bugs-follo...@perl.org> wrote: > # New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev > # Please include the string: [perl #131801] > # in the subject

Re: [perl #128062] [BUG] (MoarVM) chdir does not respect group reading privilege

It should not be testing, it should just try to do the operation and complain after if it fails. Race conditions should not be a language 'feature'. On Mon, Jul 17, 2017 at 6:02 PM, Zoffix Znet via RT < perl6-bugs-follo...@perl.org> wrote: > On Mon, 17 Jul 2017 10:26:43 -0700, molecules wrote: >

Re: [perl #128062] [BUG] (MoarVM) chdir does not respect group reading privilege

It should not be testing, it should just try to do the operation and complain after if it fails. Race conditions should not be a language 'feature'. On Mon, Jul 17, 2017 at 6:02 PM, Zoffix Znet via RT < perl6-bugs-follo...@perl.org> wrote: > On Mon, 17 Jul 2017 10:26:43 -0700, molecules wrote: >

Re: [perl #131757] Untodoed evil hack in Backtrace.pm

On Mon, Jul 17, 2017 at 2:49 AM, Joachim Durchholz via RT < perl6-bugs-follo...@perl.org> wrote: > 1) It cannot handle non-runtime code that one might want to filter. > 2) It hardcodes the definition of what's interesting. > 3) You cannot have runtime code that you *want* to be included in the >

Re: [perl #131757] Untodoed evil hack in Backtrace.pm

On Mon, Jul 17, 2017 at 2:49 AM, Joachim Durchholz via RT < perl6-bugs-follo...@perl.org> wrote: > 1) It cannot handle non-runtime code that one might want to filter. > 2) It hardcodes the definition of what's interesting. > 3) You cannot have runtime code that you *want* to be included in the >

Re: [perl #131757] Untodoed evil hack in Backtrace.pm

On Mon, Jul 17, 2017 at 4:20 AM, Joachim Durchholz <j...@durchholz.org> wrote: > Am 17.07.2017 um 09:32 schrieb Brandon Allbery: > > On Mon, Jul 17, 2017 at 2:40 AM, Joachim Durchholz <j...@durchholz.org > > <mailto:j...@durchholz.org>> wrote: > > > >

Re: [perl #131757] Untodoed evil hack in Backtrace.pm

On Mon, Jul 17, 2017 at 4:20 AM, Joachim Durchholz <j...@durchholz.org> wrote: > Am 17.07.2017 um 09:32 schrieb Brandon Allbery: > > On Mon, Jul 17, 2017 at 2:40 AM, Joachim Durchholz <j...@durchholz.org > > <mailto:j...@durchholz.org>> wrote: > > > >

Re: [perl #131757] Untodoed evil hack in Backtrace.pm

On Mon, Jul 17, 2017 at 2:40 AM, Joachim Durchholz wrote: > I think the whole concept of defining what's "interesting" in a backtrace >> by looking at the file name is pretty evil: > > So does Perl 6, actually; there's some discussion in the spec, and possibly in the docs for

Re: [perl #131757] Untodoed evil hack in Backtrace.pm

On Mon, Jul 17, 2017 at 2:40 AM, Joachim Durchholz wrote: > I think the whole concept of defining what's "interesting" in a backtrace >> by looking at the file name is pretty evil: > > So does Perl 6, actually; there's some discussion in the spec, and possibly in the docs for

Re: [perl #131737] [BUG] WindowsOS: IO.dirname strips off drive name

'dirname' represents a component of a path, not a path. I suspect the internal field components should be renamed, though, as people do not generally think in terms of the implementation of the shell's 'dirname', but instead of its effective behavior. (The implementation splits a path into its

Re: [perl #131737] [BUG] WindowsOS: IO.dirname strips off drive name

'dirname' represents a component of a path, not a path. I suspect the internal field components should be renamed, though, as people do not generally think in terms of the implementation of the shell's 'dirname', but instead of its effective behavior. (The implementation splits a path into its

Re: [perl #131695] Confusion in precedence with <<$foo>>[0]

Perhaps this example should be provided somewhere as a 'gotcha'. On Mon, Jul 3, 2017 at 11:09 AM, jn...@jnthn.net via RT < perl6-bugs-follo...@perl.org> wrote: > On Mon, 03 Jul 2017 05:46:46 -0700, comdog wrote: > > It seems that term precedence with << >> gets confused. > > > The << >> quoting

Re: [perl #131695] Confusion in precedence with <<$foo>>[0]

Perhaps this example should be provided somewhere as a 'gotcha'. On Mon, Jul 3, 2017 at 11:09 AM, jn...@jnthn.net via RT < perl6-bugs-follo...@perl.org> wrote: > On Mon, 03 Jul 2017 05:46:46 -0700, comdog wrote: > > It seems that term precedence with << >> gets confused. > > > The << >> quoting

Re: [perl #131583] [BUG] Sort content of ^methods

On Fri, Jun 16, 2017 at 12:41 AM, Gabor Szabo wrote: > Would it be used by people who use the REPL to experiment with the > languages? In that case the listing should be as user friendly as > possible and require as little typing as possible. Having ABC order is > IMHO the

Re: [perl #131583] [BUG] Sort content of ^methods

On Fri, Jun 16, 2017 at 12:41 AM, Gabor Szabo wrote: > Would it be used by people who use the REPL to experiment with the > languages? In that case the listing should be as user friendly as > possible and require as little typing as possible. Having ABC order is > IMHO the

Re: [perl #126732] [RFC] Problem with superscripts when there is no number in front of it (³² == 9)

On Thu, Jun 8, 2017 at 6:22 AM, Zoffix Znet via RT < perl6-bugs-follo...@perl.org> wrote: > > m: sub infix:<2> { $^a + $^b }; say 2 2 2 > rakudo-moar 1ac799: OUTPUT: «4␤» > > Because when an op is expected. There's just one op named `2`. And when > a term is expected, there's just one

Re: [perl #131492] Camelia produces different error message from commandline

On Mon, Jun 5, 2017 at 5:32 PM, Parrot Raiser <1parr...@gmail.com> wrote: > perl6 –e "my \foo = Callable but role:: { };" Something bit you; note that you are not using "-e" but "–e" (U+2013 EN DASH). -- brandon s allbery kf8nh sine nomine associates

Re: [perl #131492] Camelia produces different error message from commandline

On Mon, Jun 5, 2017 at 5:32 PM, Parrot Raiser <1parr...@gmail.com> wrote: > perl6 –e "my \foo = Callable but role:: { };" Something bit you; note that you are not using "-e" but "–e" (U+2013 EN DASH). -- brandon s allbery kf8nh sine nomine associates

Re: [perl #131481] [BUG] No perl6-debug

I would argue that perl6-debug shouldn't exist; if you are debugging, you pretty much need to know the specific backend that's involved. Which is likely why rakudobrew killed the generic one (the directory listing, while mangled, *did* show perl6-debug-m). On Sun, Jun 4, 2017 at 2:12 AM, Zoffix

Re: [perl #131481] [BUG] No perl6-debug

I would argue that perl6-debug shouldn't exist; if you are debugging, you pretty much need to know the specific backend that's involved. Which is likely why rakudobrew killed the generic one (the directory listing, while mangled, *did* show perl6-debug-m). On Sun, Jun 4, 2017 at 2:12 AM, Zoffix

Re: [perl #131398] Feature Request: trait for unimplemented subs/methods

As already mentioned, we have three such stubbers already. You can even put a partial/incomplete implementation after them: just terminate the ... or w/e with a semicolon. What none of them will do for you is allow a syntactically incorrect body. But the proposed feature *also* will not allow

Re: [perl #131363] [LTA] Using dot instead of a semicolon as a statement end (say ‘hello’.)

On Thu, May 25, 2017 at 8:58 AM, Aleks-Daniel Jakimenko-Aleksejev < perl6-bugs-follo...@perl.org> wrote: > Arguably, it can probably figure out that . was used instead of ;. The > problem is that . is interpreted as an infix, and therefore it only blows > up when it sees the next occurrence of

Re: [perl #129843] [LTA] Indexing on a Str throws generic “out of range” message which is less than awesome (“hello”[2])

On Mon, May 8, 2017 at 4:49 PM, Joachim Durchholz wrote: > If the mental model for Perl6 strings is "array of characters" though Perl has never had that mental model, is my point. It's generally imported by folks who come from languages where strings *are* "arrays of

Re: [perl #129843] [LTA] Indexing on a Str throws generic “out of range” message which is less than awesome (“hello”[2])

On Mon, May 8, 2017 at 2:52 PM, Aleks-Daniel Jakimenko-Aleksejev via RT < perl6-bugs-follo...@perl.org> wrote: > Usually I'm against all perl5 error messages This is a Pythonism (and C and other such languages). Older Perl has the same behavior that you can't index a string that way, but must

Re: [perl #131111] [@LARRY] %c = %a, %b and @c = @a, @b should behave similarly

IIRC this hash behavior is deliberate so that hashes can be accumulated. Also, your proposed behavior would require an object hash, not a standard hash; (%a => %b) would necessarily stringify %a. On Thu, Apr 6, 2017 at 4:46 PM, Aleks-Daniel Jakimenko-Aleksejev < perl6-bugs-follo...@perl.org>

Re: [perl #131076] [LTA] Rakudo sees Perl 5 code even if there is none (for $x(42), $x(50) {…})

That *is* Perl 5 syntax, though; it looks like the schema for $var (list) { ... } # the space is not required between the var and the parenthesized list On Wed, Mar 29, 2017 at 9:35 PM, Aleks-Daniel Jakimenko-Aleksejev < perl6-bugs-follo...@perl.org> wrote: > # New Ticket Created by

Re: [perl #131043] [BUG] Binding to `state` variable silently fails

I can't help but think that binding a state variable should be illegal, and doing so will have unexpected effects. On Wed, Mar 22, 2017 at 1:48 PM, Zoffix Znet wrote: > # New Ticket Created by Zoffix Znet > # Please include the string: [perl #131043] > # in the

Re: [perl #131026] Failing to read from IO::Pipe fast enough, apparently loses data

Note that 65535 is the POSIX-specified minimum largest write size that is guaranteed to be atomic (_PIPE_BUF), and derives from the usual size of kernel-side pipe buffers (Linux's are actually larger, but sizes larger than the POSIX minimum _PIPE_BUF are likely to incur portability issues, so

Re: [perl #130982] [PERF] "for $a..$b -> $i { ... }" loops are sometimes much slower than c-style loops

On Sun, Mar 12, 2017 at 12:48 AM, Lloyd Fournier wrote: > perl6-loop: 84.8739988 > c-loop: 67.65849241 (1.25 times faster) > native-loop: 0.4981954 (135.81 times faster) > Still quite a lot of optimization to be done on that front. WRT native int, one of the issues is

Re: [perl #130969] [LTA] more inconsistent coercions for Bool

The discussion I'm thinking of starts around here: http://colabti.org/irclogger/irclogger_log/perl6?date=2017-03-04#l1490 On Thu, Mar 9, 2017 at 4:04 PM, Zefram <zef...@fysh.org> wrote: > Brandon Allbery via RT wrote: > >In any case I am specifically thinking of a discussion

Re: [perl #130969] [LTA] more inconsistent coercions for Bool

, there may actually be some lingering inconsistency left over from when Bool had to be special-cased because it needed to exist in the setting before Enums could be defined.) On Thu, Mar 9, 2017 at 3:41 PM, Zefram <zef...@fysh.org> wrote: > Brandon Allbery via RT wrote: > >This shou

Re: [perl #130969] [LTA] more inconsistent coercions for Bool

On Thu, Mar 9, 2017 at 2:55 PM, Zefram wrote: > The same goes for coercions from other enum types. This should be your hint. Enums *are* numeric, specifically Int. I don't know what language you are trying to force Perl 6 to be, but you might want to consider the

Re: [perl #128526] [CONC] Proc::Async's .write appears to exit when the process run doesn't exist

On Wed, Mar 8, 2017 at 11:33 AM, jn...@jnthn.net via RT < perl6-bugs-follo...@perl.org> wrote: > Fixed and tested in S17-procasync/nonexistent.t. (The change is to default > to ignoring SIGPIPE, since we error-check all operations anyway. Those who > do want to exit on SIGPIPE can write

Re: [perl #130900] [BUG] nul in pathname

On Thu, Mar 2, 2017 at 9:14 AM, Joachim Durchholz wrote: > For the other invalid characters, the error will (well: should) be caught > by the filesystem. > Trying to check that in advance is a security hole in waiting - somebody > might mount or unmount filesystems between

Re: [perl #130900] [BUG] nul in pathname

On Thu, Mar 2, 2017 at 8:56 AM, Brandon Allbery <allber...@gmail.com> wrote: > - the sequence `//` which is specifically undefined by POSIX In the interests of heading off incoming pedanticness, possibly to "defend" the indefensible: this is only undefined as a pre

Re: [perl #130900] [BUG] nul in pathname

To be clear: the POSIX spec does, specifically, disallow NUL. *Only* NUL. Which then leaves: - any character disallowed by specific filesystems (consider CIFS) - the sequence `//` which is specifically undefined by POSIX Among others. Is it correct to disallow NUL and thereby have a special

Re: [perl #130900] [BUG] nul in pathname

On Thu, Mar 2, 2017 at 5:29 AM, Zefram wrote: > It is less than awesome that > Perl 6 accepts "foo\x[0]bar" as a pathname, when it doesn't resemble > any pathname valid on the OS > It's also less than awesome that POSIX, at least, doesn't let you confirm that a

Re: [perl #130870] Some self-referential issue with hash assignment (%h1 = %h1, %h2)

optimizer is *really* clever), and it's on the programmer to accept the resulting deoptimization and if necessary rewrite to avoid it. On Mon, Feb 27, 2017 at 11:08 AM, Brandon Allbery <allber...@gmail.com> wrote: > To unpack this a bit: in this case I understand the comma to be an infix &

Re: [perl #130870] Some self-referential issue with hash assignment (%h1 = %h1, %h2)

ated on the LHS > is a fundamental behaviour in Perl. Changing that, especially in > obscure special circumstances would be bad. > > On 2/27/17, Brandon Allbery <allber...@gmail.com> wrote: > > And yes, I know that it *is* retaining its value as an object pointer, > just > >

Re: [perl #130870] Some self-referential issue with hash assignment (%h1 = %h1, %h2)

And yes, I know that it *is* retaining its value as an object pointer, just not the contents. But if I write something like that, I pretty clearly mean the *contents*. On Mon, Feb 27, 2017 at 10:46 AM, Brandon Allbery <allber...@gmail.com> wrote: > I disagree; this is not Haskell

Re: [perl #130870] Some self-referential issue with hash assignment (%h1 = %h1, %h2)

I disagree; this is not Haskell, if I do something like that then I expect %h2 to retain its original value while the RHS is being evaluated. On Mon, Feb 27, 2017 at 4:35 AM, Elizabeth Mattijsen wrote: > FWIW, this feels like a DIHWIDT case > > > On 27 Feb 2017, at 00:55,

Re: [perl #130834] Is `use v5` still a thing?

It should do *something*; I suspect the intent was to offload that something, since there was at one point the idea of exec()ing a perl 5. At the very least it should throw --- but that might be handled sufficiently by the default. On Wed, Feb 22, 2017 at 8:45 AM, Zoffix Znet

Re: [perl #130723] [BUG] .pick on large ranges gives unexpected results on Windows only

On Mon, Feb 6, 2017 at 3:31 PM, Nicholas Clark wrote: > OK, this is a bit of guessing, and I would like to think that I've guessed > wrongly because someone else *should* have hit this before... > You'd be surprised. Verifying randomness is fairly tricky... and Perl 3 went

Re: [perl #130713] 42.expmod(-1,1) hangs

On Fri, Feb 3, 2017 at 4:33 PM, Elizabeth Mattijsen < perl6-bugs-follo...@perl.org> wrote: > Assume this is a MoarVM issue, as this does not appear to be an issue on > MoarVM. ...which of those was supposed to be something else? -- brandon s allbery kf8nh sine

Re: [perl #130588] [BUG] Feed operators final sub / routine parens

On Thu, Jan 19, 2017 at 6:43 AM, Sam M wrote: > > "my string" ==> reverse > ===SORRY!=== Error while compiling: > Unsupported use of bare "reverse"; in Perl 6 please use .reverse if you > meant $_, or use an explicit invocant or argument, or use to refer > to the

Re: [perl #130460] Can we relax indir's test on the target directory?

On Tue, Jan 3, 2017 at 12:58 AM, Joachim Durchholz wrote: > > indir solves all these things. (Provided it changes the current directory > back even in the face of exceptions.) Edge case: current directory can't be re-entered by path (as with the old MMDF trick: daemon

Re: [perl #130460] Can we relax indir's test on the target directory?

On Fri, Dec 30, 2016 at 5:41 PM, Joachim Durchholz wrote: > > The usual reason would be portability, but at least Windows follows the > Posix path in this regard. But all bets are off if it's a network filesystem. -- brandon s allbery kf8nh

Re: [perl #130443] [REGRESSION] [LTA] Trying to put an infinite range into a native array no longer throws (my int @a = ^Inf)

On Thu, Dec 29, 2016 at 1:43 PM, Zoffix Znet via RT < perl6-bugs-follo...@perl.org> wrote: > I see 16 fail()s in src/core/native_array.pm and I'm unsure what the best > way to do this (lizmat, any idea?) > Is this making moritz's point on IRC yesterday? 2016 Dec 28 18:39:27 I think fail() was a

Re: [perl #130339] make install failure on rakudo star 2016.11

On Wed, Dec 14, 2016 at 8:39 AM, mark carter wrote: > The perl 5 script "prove" was not found. Adding (for me, anyway) > > /usr/bin/core_perl > ...so Red Hat decided too many people had figured out how they broke Perl, and broke it even more to compensate? -- brandon s

Re: [perl #130217] [LTA] No warning when using complex rules as a character class (/<+ident>/)

On Tue, Nov 29, 2016 at 4:53 PM, Aleks-Daniel Jakimenko-Aleksejev < perl6-bugs-follo...@perl.org> wrote: > Obviously, the code above does not make any sense, which is why I think > Perl 6 should be smart enough to give a warning in this case. > Could be something like “attempt to use a complex

Re: [perl #128897] [LTA] [MATH] "-0".Num isn't negative

On Wed, Nov 23, 2016 at 1:53 AM, Zefram wrote: > There is no flag attached to a zero A status flag is not attached to a value, it is a processor status flag. Why would you say I claimed that? -- brandon s allbery kf8nh sine nomine associates

Re: [perl #128897] [LTA] [MATH] "-0".Num isn't negative

And my own misspeaking was a slight mis-description of the relevance of signed zero in the ticket, which I corrected to Zoffix in IRC. On Wed, Nov 23, 2016 at 1:20 AM, Brandon Allbery <allber...@gmail.com> wrote: > > On Wed, Nov 23, 2016 at 1:11 AM, Zefram <zef...@fysh.org> wr

Re: [perl #128897] [LTA] [MATH] "-0".Num isn't negative

On Wed, Nov 23, 2016 at 1:11 AM, Zefram wrote: > In which aspect did I misspeak? iirc underflow doesn't work quite the way either you or Darren said; it's not just the signed zero, it's also a status flag indicating that that signed zero reflects an underflow condition. What

Re: [perl #128897] [LTA] [MATH] "-0".Num isn't negative

Zefrem and I both misspoke on this, but I clarified on IRC and this was iirc already fixed as a result. On Tue, Nov 22, 2016 at 11:33 PM, Darren Duncan wrote: > And here I thought IEEE floats had distinct values to represent overflows > and underflows that were distinct

Re: [perl #128897] [LTA] [MATH] "-0".Num isn't negative

On Thu, Nov 17, 2016 at 10:13 AM, Zoffix Znet via RT < perl6-bugs-follo...@perl.org> wrote: > > The reason we have a negative floating point zero at all is more due to > underlying implementations at whose level such zeros are used to signal > various exceptions. But such usage isn't needed on

Re: [perl #129994] [NATIVECALL][BUG] C functions required to be called once in one thread are hung up

On Tue, Nov 1, 2016 at 12:01 PM, Itsuki Toyota wrote: > I think I properly call the MeCab functions from Perl 6(e.g. > $model.create-tagger, $model.create-lattice) according to the above > instructions. > So I think something is wrong in the NativeCall. > Not sure

Re: [perl #129994] [NATIVECALL][BUG] C functions required to be called once in one thread are hung up

On Tue, Nov 1, 2016 at 12:01 PM, Itsuki Toyota wrote: > I think I properly call the MeCab functions from Perl 6(e.g. > $model.create-tagger, $model.create-lattice) according to the above > instructions. > So I think something is wrong in the NativeCall. > Not sure

Re: [perl #129986] Constraints on ‘our’-scoped variables are not allowed (our Int $x)

On Sat, Oct 29, 2016 at 12:04 PM, Aleks-Daniel Jakimenko-Aleksejev < perl6-bugs-follo...@perl.org> wrote: > This is the commit that added these messages > https://github.com/rakudo/rakudo/commit/bfd8508f5ceee565380da201ef25bd > fb6feb2b3d >

Re: [perl #129830] [BUG] Cannot call .type method on an Array instance

[08 02:06:10] m: class TypeHouse { has Int @.array; }; dd TypeHouse.^attributes[0]; [08 02:06:11] rakudo-moar 2285d3: OUTPUT«Attribute @!array = Attribute.new␤ [08 02:06:11] » [08 02:06:24] m: class TypeHouse { has Int @.array; }; dd TypeHouse.^attributes[0].type; [08 02:06:25] rakudo-moar

Re: [perl #129830] [BUG] Cannot call .type method on an Array instance

[08 02:06:10] m: class TypeHouse { has Int @.array; }; dd TypeHouse.^attributes[0]; [08 02:06:11] rakudo-moar 2285d3: OUTPUT«Attribute @!array = Attribute.new␤ [08 02:06:11] » [08 02:06:24] m: class TypeHouse { has Int @.array; }; dd TypeHouse.^attributes[0].type; [08 02:06:25] rakudo-moar

Re: [perl #129820] [NATIVECALL][LTA] callback returns useless error message

On Thu, Oct 6, 2016 at 1:48 PM, Brandon Allbery via RT < perl6-bugs-follo...@perl.org> wrote: > I believe this is known. and it's difficult to fix: you simply can't map > exceptions across languages, so an exception in a Perl callback from a C > function called from Perl can

Re: [perl #129820] [NATIVECALL][LTA] callback returns useless error message

On Thu, Oct 6, 2016 at 1:48 PM, Brandon Allbery via RT < perl6-bugs-follo...@perl.org> wrote: > I believe this is known. and it's difficult to fix: you simply can't map > exceptions across languages, so an exception in a Perl callback from a C > function called from Perl can

Re: [perl #129820] [NATIVECALL][LTA] callback returns useless error message

On Thu, Oct 6, 2016 at 1:39 PM, Itsuki Toyota wrote: > In the following example, ` my = sub (Int $piyo) ` has wrong > signature (` my = sub (Int $piyo, Num $fuga) ` is a right one)and > it returns the error message of "Internal error: Unwound entire stack and >

Re: [perl #129820] [NATIVECALL][LTA] callback returns useless error message

On Thu, Oct 6, 2016 at 1:39 PM, Itsuki Toyota wrote: > In the following example, ` my = sub (Int $piyo) ` has wrong > signature (` my = sub (Int $piyo, Num $fuga) ` is a right one)and > it returns the error message of "Internal error: Unwound entire stack and >

Re: [perl #122732] [jvm] control operator crossed continuation barrier

On Wed, Sep 21, 2016 at 2:58 PM, Christian Bartolomaeus via RT < perl6-bugs-follo...@perl.org> wrote: > I must admit that I don't understand the purpose of the two lines I > removed from src/vm/jvm/runtime/org/perl6/nqp/runtime/Ops.java. They were > added with nqp commit bfee0177b1 back in 2013.

Re: [perl #129261] accessing a class attribute too early nils it/leaves it uninitialized

On Mon, Sep 12, 2016 at 11:40 PM, Brian S. Julin < perl6-bugs-follo...@perl.org> wrote: > $ perl6 -e 'class A { my $.bar = 42; }; class D { constant bar = > A.bar.say; }; A.bar.say' > (Any) > (Any) > The first one is expected, as the bodies of class definitions run at compile time but

  1   2   >