»ö« Welcome to Perl 6! | perl6.org/ | evalbot usage: 'p6: say 3;' or /msg camelia p6: ... | irclog: irc.perl6.org or colabti.org/irclogger/irclogger_log/perl6 | UTF-8 is our friend! 🦋
Set by Zoffix on 25 July 2018.
jdv79 wow, my bench for perf got worse 01:37
timotimo that's the one with the matchers? even worse? :( :(
jdv79 the one with the a lot of regex "eval" 01:38
timotimo ok, i'm thinking of the right one
do you have a rough number for how much worse, and since what previous measurement?
hm, i think we actually had a gist that had the complete code in it for benchmarking 01:39
jdv79 hmm. interesting. i had a rakudo from a few days ago and it was running about 4.5s. then i just installed head and it was 6.5s for a few runs a little bit ago. but i just tried it now and its back down to 4.5s 01:40
idk. yay not worse...
nevermind then 01:41
timotimo phew!
Garland_g[m] Maybe it had to recompile the code with the new version?
timotimo still, thanks for checking in regularly
jdv79 where's the precomp files these days? 01:42
timotimo Garland_g[m]: "for a few runs" suggests that's not it; perhaps the computer was thermal-throttled, or there was more I/O than usual, or too much pressure on RAM or anything really
Garland_g[m] Ah. I missed the "for a few runs"
jdv79 yeah. i didn't check into system state at the time.
timotimo i've been trying to improve performance for things ever since i joined the perl6 project and let me tell you, measurements can frustrate the heck out of you :) 01:44
jdv79 what's holding back eval? everything? 01:45
timotimo it's hard for me to say 01:53
i know that spesh has a whole lot of work to do because with so many evals, large parts of the compiler that are normally only called three or four times are now hot enough to be considered for speshing
and if the code that gets generated also gets hot enough while running the matchers against the data, those will also get specialization 01:54
now i lost my train of thought
buggable New CPAN upload: AttrX-Mooish-v0.3.0.tar.gz by VRURG modules.perl6.org/dist/AttrX::Mooish:cpan:VRURG 02:42
rindolf hi all 05:31
masak \o 05:45
lookatme_q o/ rindolf 05:53
rindolf masak: sup? 05:55
lookatme_q: hi
lookatme_q :) 06:09
xinming_ m: sub t (*, $var) { $var.say; }; t('a', "Hello"); 06:17
camelia 5===SORRY!5=== Error while compiling <tmp>
Missing block
at <tmp>:1
------> 3sub t (*7⏏5, $var) { $var.say; }; t('a', "Hello")
xinming_ m: sub t ($, $var) { $var.say; }; t('a', "Hello"); 06:18
camelia Hello
xinming_ m: sub t ($, $var) { $var.say; }; t(*, "Hello");
camelia Hello
xinming_ for the sub part, is the use of $ right here?
I mean use it as a placeholder
m: sub t ($, $var) { $var.say; }; t(*, *, "Hello");
camelia 5===SORRY!5=== Error while compiling <tmp>
Calling t(Whatever, Whatever, Str) will never work with declared signature ($, $var)
at <tmp>:1
------> 3sub t ($, $var) { $var.say; }; 7⏏5t(*, *, "Hello");
xinming_ m: sub t ($, $, $var) { $var.say; }; t(*, *, "Hello"); 06:19
camelia Hello
xinming_ m: sub t(:good) { "Good".say; }; t(:good); 07:17
camelia 5===SORRY!5=== Error while compiling <tmp>
Missing block
at <tmp>:1
------> 3sub t(:7⏏5good) { "Good".say; }; t(:good);		 07:18
xinming_ m: multi sub t(:good) { "Good".say; }; t(:good);
camelia 5===SORRY!5=== Error while compiling <tmp>
Missing block
at <tmp>:1
------> 3multi sub t(:7⏏5good) { "Good".say; }; t(:good);
Geth doc: aaa34a8788 | (JJ Merelo)++ | 2 files
Clarifies time for constants, closes #2279
xinming_ m: sub t(:$good) { "Good".say; }; t(:good);
camelia Good
xinming_ m: multi sub t(:$good) { "Good".say; }; t(:good);
camelia Good
xinming_ m: multi sub t(:$good) { "Good".say; }; multi sub t(:!$good) { "Not good".say }; t(:good); 07:19
camelia 5===SORRY!5=== Error while compiling <tmp>
Missing block
at <tmp>:1
------> 3t(:$good) { "Good".say; }; multi sub t(:7⏏5!$good) { "Not good".say }; t(:good);
xinming_ m: multi sub t(:$good) { "Good".say; }; multi sub t(:!good) { "Not good".say }; t(:!good);
camelia 5===SORRY!5=== Error while compiling <tmp>
Missing block
at <tmp>:1
------> 3t(:$good) { "Good".say; }; multi sub t(:7⏏5!good) { "Not good".say }; t(:!good);
xinming_ m: multi sub t(:$good) { "Good".say; }; multi sub t(:!$good) { "Not good".say }; t(:!good);
camelia 5===SORRY!5=== Error while compiling <tmp>
Missing block
at <tmp>:1
------> 3t(:$good) { "Good".say; }; multi sub t(:7⏏5!$good) { "Not good".say }; t(:!good);
xinming_ m: multi sub t(:$good) { "Good".say; }; multi sub t(!:$good) { "Not good".say }; t(:!good);
camelia 5===SORRY!5=== Error while compiling <tmp>
Missing block
at <tmp>:1
------> 3 t(:$good) { "Good".say; }; multi sub t(7⏏5!:$good) { "Not good".say }; t(:!good)
xinming_ hmm, any idea how I can make this work? :-)
m: multi sub t(:$good) { "Good".say; }; multi sub t(:$good where { False }) { "Not good".say }; t(:!good); 07:20
camelia Good
xinming_ m: multi sub t(:$good) { "Good".say; }; multi sub t(:$good where { $_ ~~ False }) { "Not good".say }; t(:!good);
camelia Potential difficulties:
Smartmatch against False always fails; if you mean to test the topic for truthiness, use :!so or *.not or !* instead
at <tmp>:1
------> 3ay; }; multi sub t(:$good where { $_ ~~ 7⏏5False }) { "Not good".sa…
xinming_ m: multi sub t(:$good) { "Good".say; }; multi sub t(:$good where { not so $_ }) { "Not good".say }; t(:!good);
camelia Good
xinming_ m: multi sub t(:$good where { so $_ }) { "Good".say; }; multi sub t(:$good where { not so $_ }) { "Not good".say }; t(:!good); 07:21
camelia Not good
xinming_ m: multi sub t(:$good) { "Good".say; }; multi sub t(:$good where { not so $_ }) { "Not good".say }; t(:good);
camelia Good
xinming_ For my example, Is there a easier way to write signatures?
lookatme_q m: multi sub t(:$good!) { "Good".say; }; multi sub t(:$good) { "Not good".say }; t(:good); 07:40
camelia Good
lookatme_q m: multi sub t(:$good!) { "Good".say; }; multi sub t(:$good) { "Not good".say }; t();
camelia Not good
lookatme_q xinming_, how about this way ? ^^
m: multi sub t(:$good!) { "Good".say; }; multi sub t() { "Not good".say }; t(); 07:41
camelia Not good
lookatme_q m: multi sub t(:$good!) { "Good".say; }; multi sub t() { "Not good".say }; t(good => False);
camelia Good
lookatme_q hmm, seems like not what you want
m: multi sub t(:$good where :so) { "Good".say; }; multi sub t($good where :!so) { "Not good".say }; t(good => False); 07:44
camelia Cannot resolve caller t(:!good); none of these signatures match:
(:$good where { ... })
($good where { ... })
in block <unit> at <tmp> line 1
lookatme_q m: multi sub t(:$good where :so) { "Good".say; }; multi sub t(:$good where :!so) { "Not good".say }; t(good => False);
camelia Not good
lookatme_q xinming_, Find it, I am using this way ^^
m: multi sub t(:$good where :so) { "Good".say; }; multi sub t(:$good where :!so) { "Not good".say }; t(:good);
camelia Good
lookatme_q m: multi sub t(:$good where :so) { "Good".say; }; multi sub t(:$good where :!so) { "Not good".say }; t();
camelia Not good
xinming_ what is the whole idea behind the where :so? 07:46
!$good where { so => $_ }?
$good where { so => $_ }? 07:47
lookatme_q xinming_, I forget it now :)
xinming_ I mean, Why :so worked like this. :-)
lookatme_q xinming_, wait me try to find it in documents 07:48
xinming_ Ok, THanks. :-)
lookatme_q m: multi sub t(:$good where .so) { "Good".say; }; multi sub t(:$good where !.so) { "Not good".say }; t(); 07:49
camelia Not good
lookatme_q And xinming_, this way it's easy to understand 07:50
xinming_ lookatme_q: I can undersstand this 07:51
something like where .so = *.so
But why :so worked?
CIAvash[m] xinming_: docs.perl6.org/routine/ACCEPTS#(Pa...od_ACCEPTS 07:52
xinming_ Thanks
lookatme_q m: multi sub t(:$good where so) { "Good".say; }; multi sub t(:$good where !so) { "Not good".say }; t(); 07:53
camelia 5===SORRY!5=== Error while compiling <tmp>
Prefix so requires an argument, but no valid term found
at <tmp>:1
------> 3multi sub t(:$good where so7⏏5) { "Good".say; }; multi sub t(:$good wh
expecting any of:
prefix
lookatme_q m: multi sub t(:$good where so) { "Good".say; }; t();
camelia 5===SORRY!5=== Error while compiling <tmp>
Prefix so requires an argument, but no valid term found
at <tmp>:1
------> 3multi sub t(:$good where so7⏏5) { "Good".say; }; t();
expecting any of:
prefix
lookatme_q xinming_, I using it in my module, I am not remember where I found it :) 07:54
xinming_ m: multi sub t(:$good where .so) { "Good".say; }; multi sub t(:$good where !.so) { "Not good".say }; t();
camelia Not good
xinming_ m: multi sub t(:$good where .so) { "Good".say; }; multi sub t(:$good where !.so) { "Not good".say }; t(:good);
camelia Good
xinming_ m: multi sub t(:$good where .so) { "Good".say; }; multi sub t(:$good where !.so) { "Not good".say }; t(:!good);
camelia Not good
lookatme_q this way is easy to understand and writing 07:54
xinming_ .so is easier to understand, But :so is also understandable 07:55
after read the doc
I think perl6 will spend my lifetime to learn it.
lookatme_q xinming_, haha yeah, Perl 6 is so many things like Perl does 08:10
lizmat .tell AlexDaniel fixed the QuantHash tests in 6.c-errata 09:21
yoleaux lizmat: I'll pass your message to AlexDaniel.
AlexDaniel . 09:22
yoleaux 09:21Z <lizmat> AlexDaniel: fixed the QuantHash tests in 6.c-errata
AlexDaniel just in time, woke up 10 mins ago :)
lizmat :-)
sarna hey, bannerbot broke 10:04
it didn't tell me not to send messages :^( 10:05
nine timotimo: not...yet, no. I've never written a Python extension module. Also I feel like I'm already neglecting Inline::Python 10:08
xinming_ for samewith, Do we need to also pass the self as the first arg to it? 10:26
lizmat no. The whole point is that it will call the same method with the same invocant, but with different parameters 10:31
xinming_ Thanks, got it 10:36
so, we need self when we call with nextcallee 10:37
lizmat xinming_: don't think so, according to docs.perl6.org/routine/nextcallee 10:58
jnthn I suspect you would have to pass it explicitly to nextcallee, since that gives you the code object of the next thing that would be called
lizmat hmmm... or maybe so
jnthn well, not to nextcallee, but to the thing that nextcallee returns to you 10:59
lizmat perhaps a doc issue would be in order here
xinming_ yea, I do mean, with the sub returned by nextcallee, We need to pass self to it. 11:00
thanks
I'm still testing something
trying something
xinming_ termbin.com/7ukx 11:08
m: termbin.com/7ukx 11:09
camelia 5===SORRY!5=== Error while compiling <tmp>
Confused
at <tmp>:1
------> 3http:7⏏5//termbin.com/7ukx
expecting any of:
colon pair
xinming_ I think bot should be able to eval the content via url. :>
BTW, focus to the question, Is this a bug?
it should match the "third", But actually, it match the first one.
I think, the third arg :!good hides the $good anyway. 11:10
lizmat xinming_: also try changing the order of the candidates
xinming_ Ok~~~ change the order worked, 11:25
seems we'll have to make the "default" last.
lizmat: Do you think wether there is a better version for my example instead of chaning the order of multi methods? 11:26
lizmat the way I understand MMD is that all "where" clauses are tie-breaking, so the first one that matches, will fire 11:28
lizmat sightseeing& 11:35
scimon So if an attribute has a type like Positional[Int] is there an easy way to get the Int 12:00
jnthn m: say Positional[Int].^role_arguments[0] 12:02
camelia (Int)
scimon Cheers :) 12:03
scimon (I'm extending Trait::Env so you can have Array attributes because the more I look at it the more I think it's going to be useful with Docker) 12:06
Luneburg p6: return True if "0291" ~~ /a*/; 12:07
camelia Attempt to return outside of any Routine
in block <unit> at <tmp> line 1
jnthn Ah, it'll split the env var on some delimiter? 12:07
Luneburg return "Match" if "0291" ~~ /a*/; 12:08
p6: say "Match" if "0291" ~~ /a*/;
camelia Match
Luneburg Why does that match?
AlexDaniel because it matched zero a's 12:09
p6: say "Match" if "0291" ~~ /a+/;
camelia ( no output )
AlexDaniel or
p6: say "Match" if "0291" ~~ /^a*$/;
camelia ( no output )
scimon So if I say has @.name is env it will look for all %*ENV keys that match ^NAME.*$ order them lexically and put the values in the array. 12:10
Luneburg Ah, that makes sense. Thanks
jnthn scimon: Oh...that's an interesting convention :)
scimon Well. I figure I can allow for others. But it'll do for me.
jnthn :)
scimon Plus I have other plans for a hash version. 12:11
Trying to work around the limitations of ENV to make setting up Docker config super easy. Plus I'm just enjoy noddling around with Traits.
scimon Right. Best I get back to work. Trait::Env doing more stuff. 13:32
buggable New CPAN upload: Trait-Env-0.2.0.tar.gz by SCIMON modules.perl6.org/dist/Trait::Env:cpan:SCIMON 13:42
uzl Good morning, #perl6. I'm failing to conceptualize the following line: 14:02
yoleaux 22 Aug 2018 20:02Z <b2gills> uzl: tio.run/##Tc5PC4JAEAXw@36KhyisIBIe...tZmFsWl6Aw
uzl "Within methods, $.origin works the same as self.origin, however the colon-syntax for method arguments is only supported for method calls using self, not the shortcut."
doc: docs.perl6.org/language/objects#self
m: 14:03
class A { method origin(:$number) { $number }; method get-originA { self.origin(number => 5) }; method get-originB { $.origin(:number(5)) } }; my $x = A.new(); say $x.get-originA(), " ", $x.get-originB();
evalable6 5 5
uzl I wonder why I am able to $.origin with colon-syntax inside the get-originB method. That sentence in the doc says it isn't supported with the shortcut to self.method() 14:05
jnthn I think it means you can't do `$.foo: $arg` 14:06
uzl jnthn: I haven't seen that form before. I'd appreciate if you could provide me with a short example. ;) 14:10
jnthn m: $*OUT.say: 'hello' 14:12
camelia hello
jnthn It's especially useful with cases like
$lock.protect: { ...code... }
Because then you don't have to worry about putting a closing ) after the } 14:13
uzl Yeah, I've seen it been used with map, sort, etc. I just didn't realize it was the same thing. Thanks! 14:14
uzl .tell b2gills Thanks! I just noticed there was an example in the doc all this time. I'll have to pay more attention when reading the doc :). 14:17
yoleaux uzl: I'll pass your message to b2gills.
uzl class A { method origin($number) { $number }; method get-originA { self.origin: 5 }; method get-originB { $.origin: 5 }; my $x = A.new(); say $x.get-originA(), " ", $x.get-originB(); 14:25
uzl m: class A { method origin($number) { $number }; method get-originA { self.origin: 5 } }; A.new.get-originA(); 14:33
camelia ( no output )
uzl m: class A { method origin($number) { $number }; method get-originA { self.origin: 5 } }; say A.new.get-originA();
camelia 5
uzl m: class A { method origin(:$number) { $number }; method get-originA { self.origin: number => 5 } }; say A.new.get-originA();
camelia 5
uzl m: class A { method origin(:$number) { $number }; method get-originA { self.origin: :number(5) } }; say A.new.get-originA();
camelia 5
SmokeMachine m: class A { method origin(:$number) { $number }; method get-originA { self.origin: :5number } }; say A.new.get-originA(); 14:52
camelia 5
scimon Waiting on code review. Added :sep to Trait::Env now you can say `has @.path is env(:sep<:>)` and it's work :) 15:59
it'll even
buggable New CPAN upload: Trait-Env-0.2.1.tar.gz by SCIMON modules.perl6.org/dist/Trait::Env:cpan:SCIMON 16:02
TimToady "env" is one of those overloaded words comp sci is full of...
scimon Yeah... well I can change it. is from-env could work? 16:08
jnthn is env-var might be clearer :) 16:09
benjikun I don't mind `env` in itself, but ^ this seems nicer
jnthn otoh, we call it %*ENV in Perl 6, `env` is somewhat guessible
Nice module idea, btw. :)
scimon Right now I just like the idea of being able to easily specify a bunch of things come from the Environment for my docker files. Plus I'm having fun getting my head around Traits and how they tie into stuff.
jnthn could imagine using that now and then 16:10
scimon Well it *was* your's :)
jnthn oh!
I forgot...hah :)
benjikun lol
scimon Plus I nicked some stuff from lizmat for make exportable traits.
making even.
scimon I think I want for env *because* it's called %*ENV 16:11
benjikun understandable
scimon Of course the nice thing with versioned modules if I *do* decide to change the name people can just pin the old one.
TimToady I guess the thing that bugged me was more that it was unclear on shallow inspection how :sep<:> relates to actual environment variables 16:12
TimToady so I wasn't sure env related to ENV 16:12
but I guess if you actually learn the language, it becomes more understandable :) 16:13
scimon I think I picked it because the PATH variable tends to be ':' seperated. I'm thinking I may allow :seperator<:> as well.
I am trying :)
TimToady I meant, me learning the language of 'is env' :) 16:14
scimon Ah :D
TimToady I have no qualm about using "env" if it really does relate to ENV
scimon Again. I'm basing it partly off what I'm using.
TimToady the non-ENV-looking :sep just made me think it wasn't 16:15
scimon Well there's other bits `has $.path is env` would just put the PATH variable into the string.
I'm trying to give it some good docs too. I really hate coming to a module and the docs don't exist. 16:16
skids FWIW I was talking to a fellow old-school coder about Perl6; one of the things he balked at was hyphens in identifiers. I've never liked them, and personally I think they should be used sparingly. 16:17
benjikun skids: I've heard other perl6-ers love them for some reason
jnthn
.oO( Did you mean old_school coder? )
scimon I love them :) but I like mixing things up.
oldSchool maybe? 16:18
skids jnthn: haha.
benjikun We had some discussion about hyphens vs _ vs likeThis at some other point previously
TimToady hyphens are really easy to get used to, if you don't have an ax to grind already :)
jnthn skids: Was it a gut reaction, or more an "won't there be confusion with infix:<->" reaction? 16:19
TimToady yes, there was quite a lengthy discussion in the backlog
scimon The one thing I'm doing is converting them to _ when mapping attribute name to ENV var (as well as going upper case) to match the general standards for this.
skids jnthn: paraphrasing "yeah I know parsing technology has caught up... but, please no."
benjikun Another language, Nim actually makes `someFunction` do the same thing as `some_function` regardless of what it was defined as 16:20
scimon Anyway I have a dumb love of * * * being a valid language construct. I'm hardly going to complain about -
TimToady probably from someone who was raised in the age where you had to leave all spaces out to fit into memory :)
as was I, but I got over it 16:21
skids (Underscores can be overused as well... both can lead to shirking the process of pondering whether there's an appropriately huffmanized alternative.)
scimon I spend too much time dealing with Python devs. My Perl 5|6 code tends to be interspersed with spaces where they would wince. 16:22
TimToady anyway, Perl 6 very intentionally encourages people to put spaces around most binary operators
benjikun if it works, it works heh 16:23
scimon Side note. Is there any plans for making it easier to export traits? The trick I nicked of lizmat works but it's a bit of a cludge.
TimToady so we grudgingly allow $i-1 to be an expression, not a COBOL-style variable 16:24
skids Meh, extra spaces never bothered me. Heck, I tend to put superstitious parens whenever the precedence gets too far above newbie level just for clarity 16:25
TimToady exporting all sorts of stuff will probably get easier when we get more macro stuff going
scimon :)
jnthn scimon: Hm, you can't just mark the trait_mod with `is export`? 16:26
sarna what's the p6y version of this regex: /\b\w/ ? 16:26
TimToady /«/ 16:27
sarna oh my.
TimToady or /<</
scimon jnthn: I'm afraid not.
TimToady it's like \< in other re
but \< is against Perl policy
sarna thanks :^) 16:28
TimToady scimon: I'd consider that a bug, really
failure to export a syntax category, more or less 16:29
jnthn scimon: Odd, I'm sure I've got code doing so...
scimon I think it's to do with it not correctly handling exported traits and others so you can chain is exported-trait is rw 16:31
I'll try it again. I have to head off now. 16:32
lex_ Why does this >>> say "27.36.1.255 FAIL > 77 999.569.22.40".match(/ \d ** 1..3 <?{ $/ < 256}> /, :global); splits the numbers larger than 256 into two numbers? 17:44
lex_ Output : (｢27｣ ｢36｣ ｢1｣ ｢255｣ ｢77｣ ｢99｣ ｢9｣ ｢56｣ ｢9｣ ｢22｣ ｢40｣) 17:45
TimToady because of backtracking 17:47
either use :r or put « » around the "word"
TimToady well, :r might not work given .match is "backtracking forward" the start position 17:48
if you're looking for well-formed IP addresses though, you probably want to fail the whole thing if any of the components are > 255 17:49
lex_ Yes 17:50
Greater than 22
255
I was going to do a range. I have run out of time. brb
TimToady m: say "27.36.1.255 FAIL > 77 999.569.22.40".match(/ ( « \d+ » ) ** 4 % '.' <?{ $0.all < 256}> /, :global); 17:52
camelia (｢27.36.1.255｣
0 => ｢27｣
0 => ｢36｣
0 => ｢1｣
0 => ｢255｣)
rindolf hi all 18:44
benjikun rindolf: howdy 18:54
masak rindolf: greetings, earthling 19:15
rindolf masak: sup? 19:16
benjikun lol
tyil heh 19:37
does anyone know why Niecza on wikipedia redirects to Perl 6?
en.wikipedia.org/w/index.php?title...edirect=no
benjikun github.com/sorear/niecza 19:38
Guess someone set it to a long time ago 19:39
masak rindolf: busy. looking forward to being less so. 19:40
rindolf: et tu?
rindolf masak: refactoring some gnumake code 19:41
tyil benjikun: heh, interesting
masak today I realized Slip() is a wee bit more powerful than JS's array spread 19:43
because the latter is syntactic, and can only occur inside array literals
whereas the former is first-class and can be passed around
m: say [1, 2, 3].map(-> $e { Slip(["$e$e", "$e $e"]) }).perl 19:45
camelia ("11", "1 1", "22", "2 2", "33", "3 3").Seq
masak AFAIU, the Slip "deploys" when it gets placed in the resulting Seq 19:46
scimon So yeah... is export on the traits seems to work fine . Hmmmm 20:47
pk_ HELP perl6 21:35
Is there a support for TK in Perl6?
El_Che I only see gtk modules 21:36
pk_ thank you ... 21:37
vrurg "Missing serialize REPR function for REPR VMIter (BOOTIter)" - what could it be?? 22:56
timotimo some object that landed in precompilation kept an iterator around but we don't support precompiling them (yet?) 22:57
vrurg Heh, it doesn't make my life easier. Ok, thanks! 22:58
timotimo something you started iterating over, but have not finished? 23:00
vrurg There is no my modules in the stack trace. Though it gives me some idea... 23:02
timotimo: Thanks!
pk_ I am trying to include inline:perl5 module like below 23:03
perl6 -I Inline-Perl5-master/lib
timotimo Inline::Perl5 relies on a compilation step during installation, so if you're not installing it with zef, it will probably not work 23:04
pk_ and then at prompt use Inline::Perl5;
===SORRY!=== Error while compiling /u/kprabha/Inline-Perl5-master/lib/Inline/Perl5/Interpreter.pm6 (Inline::Perl5::Interpreter) An exception occurred while evaluating a constant at /u/kprabha/Inline-Perl5-master/lib/Inline/Perl5/Interpreter.pm6 (Inline::Perl5::Interpreter):12 Exception details: ===SORRY!=== Error while compiling Cannot locate native library '/u/kprabha/Inline-Perl5-master/resources/libraries/libp5helper.so': /u/kprab 23:05
timotimo that's the result of compiling what it compiles during installation
timotimo the p5helper library 23:05
pk_ could you let me know how to install it properly?
timotimo "zef install Inline::Perl5"; can you tell us your perl6 --version, too? 23:08
pk_ Rakudo Star version 2018.06 built on MoarVM version 2018.06 23:10
I do not have zef ... I use centos 23:11
timotimo did you install rakudo star from centos' provided packages?
pk_ I usually download modules, build and use it ...
yes
timotimo OK, you can git clone github.com/ugexe/zef 23:12
timotimo it has a readme file that explains how to install it, but it's basically "perl6 -I lib bin/zef install ." or something similar 23:12
you may also have to include a specific path in your $PATH for "zef" to become available without the full path
pk_ sure ... I will try that 23:13
pk_ zef install Inline::Perl5 giving below error 23:34
===> Searching for: Inline::Perl5 ===> Updating cpan mirror: raw.githubusercontent.com/ugexe/Pe...cpan1.json !!!> Failed to update cpan mirror: raw.githubusercontent.com/ugexe/Pe...cpan1.json ===> Updating cpan mirror: raw.githubusercontent.com/ugexe/Pe.../cpan.json !!!> Failed to update cpan mirror: raw.githubusercontent.com/ugexe/Pe...ystems/mas
AlexDaniel pk_: hmm, could it be an issue with ipv6 or something like that? 23:46
pk_ +AlexDaniel : Not getting how to fix that ... any ideas? 23:49
AlexDaniel pk_: can you access these URLs via your browser? 23:52
pk_: for example raw.githubusercontent.com/ugexe/Pe...cpan1.json
pk_: by any chance, is github blocked in your country?
pk_ I can access the link ... I don't think it is blocked 23:54
jnthn Proxy perhaps? Not sure how zef handles that off hand.

Powered by Cro and the Raku® Programming Language.

Please report any issues / comments / feature requests as an issue on App::Raku::Log.

Thank you!