|
Fire is step THREE! | github.com/perl6/toolchain-bikeshed | Channel logs: irclog.perlgeek.de/perl6-toolchain/today | useful prior art: metacpan.org/pod/CPAN::Meta::Spec Set by moderator on 28 September 2016. |
|||
|
01:49
ilbot3 joined
|
|||
| moderator | Fire is step THREE! | github.com/perl6/toolchain-bikeshed | Channel logs: irclog.perlgeek.de/perl6-toolchain/today | useful prior art: metacpan.org/pod/CPAN::Meta::Spec | ||
|
04:04
tony-o joined
05:13
domidumont joined
05:18
domidumont joined
05:57
domidumont joined
|
|||
| 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:04 | |
| 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:06 | |
| ugexe | oh i was hoping more than 1 version would be able to load at once | 16:07 | |
| even if just in different scopes | |||
| mst | I don't see how that could work in terms of C level loading conventions and perl5's architecture | ||
| nine | what mst said | ||
| Same reason why you can't have Python 2 and 3 in the same process | 16:08 | ||
|
16:08
domidumont joined
|
|||
| 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:09 | |
| mst | maybe I need to implement Object::Remote for both p2 and p3 | 16:17 | |
| and taunt them with it | |||
|
17:44
FROGGS joined
18:37
perlpilot_ joined
19:15
perlpilot joined
21:01
tbrowder joined
|
|||