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 #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 #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 #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 #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 #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 #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 #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 #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 4:20 AM, Joachim Durchholz wrote: > Am 17.07.2017 um 09:32 schrieb Brandon Allbery: > > On Mon, Jul 17, 2017 at 2:40 AM, Joachim Durchholz > > wrote: > > > > I think the whole concept of defining

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 #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 #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 #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 #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 #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: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 #129240] [NativeCall] nativesizeof routine returns the different result from sizeof function in C when it takes a CArray object as an argument.

On Sat, Sep 10, 2016 at 10:11 AM, Itsuki Toyota < perl6-bugs-follo...@perl.org> wrote: > $ perl6 -MNativeCall -e 'my $null = Pointer; my $not-null = > CArray[int32].new; $not-null[0] = 1; $not-null[1] = 1; $not-null[2] = 1; > say nativesizeof($not-null)' > 8 > That size looks doubly wrong to me.

Re: [perl #128831] t/spec/S16-io/eof.t is unportably assuming that /proc/1/comm exists

On Wed, Aug 3, 2016 at 3:12 PM, Nicholas Clark wrote: > I don't know what file would be safer. Maybe mem? None of them. There's no guarantee that /proc exists (non-SVR4 commercial Unixes), or that it is in any way compatible with Linux's notion of /proc (FreeBSD,

Re: [perl #128049] [BUG] "Cannot look up attributes in a type object" error has occurred in the context of using NativeCall

On Mon, May 2, 2016 at 9:20 AM, Elizabeth Mattijsen wrote: > > You should probably rename your method “new” to BUILD, so that the default > .new() implementation can find it. Could definition of a method new throw a worry or something, pointing people to BUILD and/or the object

Re: [perl #127482] Compilation check says Syntax OK but program gets error

On Sat, Feb 6, 2016 at 8:24 PM, James E Keenan wrote: > $ perl6 attempted_printf.pl6 > Type check failed in binding $format; expected Cool but got Pair > in block at attempted_printf.pl6 line 5 > The syntax is fine. The semantics aren't, and even simpler cases

Re: [perl #127355] rakudo configuration and build overly dependent on specific version

On Mon, Jan 25, 2016 at 11:00 AM, Will Coleda via RT < perl6-bugs-follo...@perl.org> wrote: > 3) Try the macport version. It's possible that might work, even on your > machine. No promises. > You could also get a modern cURL and git from MacPorts/Homebrew/whatever. Note that your OS certificate

Re: [perl #127308] Configure.pl with moar fails to find C compiler on older Darwin

On Thu, Jan 21, 2016 at 2:29 PM, Tobias Leich via RT < perl6-bugs-follo...@perl.org> wrote: > Can't we do something like this[^1] on darwin also? > > [^1] https://github.com/MoarVM/MoarVM/blob/master/build/setup.pm#L445 > > Like, checking for the existance of clang, and falling back to gcc? >

Re: [perl #127308] Configure.pl with moar fails to find C compiler on older Darwin

On Wed, Jan 20, 2016 at 11:37 AM, Steve Mynott wrote: > My guess is that the PPC version of OS X probably still has the real > GCC as its compiler rather than clang as on more modern systems. > This will also be true of Intel-based Macs with Xcode 3.x or earlier (roughly