Perl 6 - the future is here, just unevenly distributed

IRC log for #perl11, 2015-06-25

| Channels | #perl11 index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
03:07 ilbot2 joined #perl11
03:07 Topic for #perl11 is now Perl5 + Perl6 == Perl11; # http://irclog.perlgeek.de/perl11/
05:05 travis-ci RPerl build errored. Will Braswell says 'Generator, C++ Ops C++ Types, CompileUnit::Module::Class::Generator, Part 1'
05:05 travis-ci https://travis-ci.org/wbraswell/rperl/builds/68267319 https://github.com/wbraswell/rperl/compare/fe44ce17f5c4...5f896f56e88b
08:17 basiliscos joined #perl11
15:57 ToApolytoXaos joined #perl11
18:11 basiliscos joined #perl11
20:33 willthechill joined #perl11
21:13 willthechill ToApolytoXaos: yes I think you have found a typo in the Inline::CPP documentation, good job!
21:13 ToApolytoXaos there are a couple of parts of that code that actually need reimplementation
21:14 ToApolytoXaos use Inline C; does not work under "use strict; use warnings;"
21:14 ToApolytoXaos you have to include C in quotes
21:14 willthechill there are currently some pending RPerl pull requests to be merged into Inline::C and Inline::Filters, so we will wait for those to happen before addressing the Inline::CPP issue
21:14 ToApolytoXaos brilliant
21:14 ToApolytoXaos I was experimenting with Inline::C and Inline::CPP last night
21:14 ToApolytoXaos really interesting
21:15 ToApolytoXaos also, regarding the previous typo, the package name should change as well
21:15 willthechill Inline is one of the key components which makes RPerl possible
21:15 ToApolytoXaos is referred as Foo whereas class name is Baz
21:15 ToApolytoXaos true
21:16 willthechill yes that documentation may have multiple typos
21:16 ToApolytoXaos no worries, as long as we can fix those, we shall be alright :)
21:16 willthechill I wrote the Inline::CPP docs section on the "classes" option I created, but I did not go through the rest of the document combing carefully for typos
21:18 ToApolytoXaos OK, with the first chance I will read it really carefully and if I find anything suspicious, I will report it to you
21:18 ToApolytoXaos have no worries
21:18 ToApolytoXaos Inline::C made me last night so happy and enthusiast that I decided to take Perl rather seriously
21:18 ToApolytoXaos I can combine 3 languages I have the most; C, C++, and Perl
21:19 ToApolytoXaos what else do I want?!
21:19 willthechill what else you want is RPerl
21:19 willthechill because writing Inline::C and Inline::CPP is annoying and time-consuming and tedious
21:19 willthechill that's why RPerl exists, so nobody has to write Inline::C or Inline::CPP any more
21:19 willthechill sure you can do it for fun, but I want to get my software working faster and less effort, so RPerl is best
21:20 willthechill brb
21:21 ToApolytoXaos true; but as far as I know, not all C++ is fully supported yet..but anyway, details :)
21:21 ToApolytoXaos RPerl for the win! ^_^
21:35 willthechill of course not all C++ is supported yet, nor will it ever be, nor need it or SHOULD it ever be
21:35 willthechill we only need enough C and C++ for RPerl to work properly
21:48 basiliscos joined #perl11
21:53 ToApolytoXaos which features are used if I may ask?
21:54 ToApolytoXaos is there a catalog or a table anywhere?
21:55 willthechill the only thing is to read the Inline docs and read the RPerl source code
22:08 ToApolytoXaos now you have confused me lol
22:09 ToApolytoXaos I thought you have stripped unnecessary parts of Inline::* for RPerl's development
22:09 ToApolytoXaos but I guess Inline::C and CPP work as variants and not as literal languages
22:12 willthechill Inline::C and Inline::CPP match the headers of C functions and C++ classes, then create the XS code to bind those C functions and C++ classes into Perl
22:12 willthechill there are many parts of C and C++ which Inline::C and Inline::CPP do not support and will probably never support
22:13 willthechill also, there are some parts of Inline::C and Inline::CPP which RPerl is not currently using, HOWEVER those parts become less-and-less as RPerl matures; in other words, RPerl utilizes a large percentage of the current Inline features

| Channels | #perl11 index | Today | | Search | Google Search | Plain-Text | summary