Perl 6 - the future is here, just unevenly distributed

IRC log for #perl6-toolchain, 2016-09-29

| Channels | #perl6-toolchain index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
01:49 ilbot3 joined #perl6-toolchain
01:49 Topic for #perl6-toolchain is now Fire is step THREE! | https://github.com/perl6/toolchain-bikeshed | Channel logs: http://irclog.perlgeek.de/perl6-toolchain/today | useful prior art: https://metacpan.org/pod/CPAN::Meta::Spec
04:04 tony-o joined #perl6-toolchain
05:13 domidumont joined #perl6-toolchain
05:18 domidumont joined #perl6-toolchain
05:57 domidumont joined #perl6-toolchain
16:04 ugexe nine: without having given any other thought to this idea: for :api<> what if you could do `use Inline::Perl5:api<5.22.2>`? And have multiple versions of Perl5 available through the same version (although duplicate installs) of Inline::Perl5?
16:06 nine One would need to set api on installation. Other than that and that you wouldn't be able to load multiple versions at the same time, it should work.
16:07 ugexe oh i was hoping more than 1 version would be able to load at once
16:07 ugexe even if just in different scopes
16:07 mst I don't see how that could work in terms of C level loading conventions and perl5's architecture
16:07 nine what mst said
16:08 nine Same reason why you can't have Python 2 and 3 in the same process
16:08 domidumont joined #perl6-toolchain
16:09 nine Which reminds me of that it's now the third year in which I wonder why they've never figured out that they could run them in different processes.
16:17 mst maybe I need to implement Object::Remote for both p2 and p3
16:17 mst and taunt them with it
17:44 FROGGS joined #perl6-toolchain
18:37 perlpilot_ joined #perl6-toolchain
19:15 perlpilot joined #perl6-toolchain
21:01 tbrowder joined #perl6-toolchain

| Channels | #perl6-toolchain index | Today | | Search | Google Search | Plain-Text | summary