Perl 6 - the future is here, just unevenly distributed

IRC log for #perl11, 2015-05-21

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

All times shown according to UTC.

Time Nick Message
01:00 davido___ joined #perl11
01:05 davido___ joined #perl11
03:31 willthechill joined #perl11
05:05 travis-ci RPerl build passed. Will Braswell says 'Generator, Perl Ops Perl Types, OperatorVoid::Named::Return, Part 2'
05:05 travis-ci http://travis-ci.org/wbraswell/rperl/builds/63434269 https://github.com/wbraswell/rperl/compare/7924c757f895...d0cb65652db9
06:28 willthechill cool
09:46 basiliscos joined #perl11
09:52 basiliscos joined #perl11
10:23 travis-ci RPerl build failed. Will Braswell says 'Generator, Perl Ops Perl Types, OperatorVoid::Named::Return, Part 3'
10:23 travis-ci http://travis-ci.org/wbraswell/rperl/builds/63464615 https://github.com/wbraswell/rperl/compare/d0cb65652db9...49b00cc36562
10:23 willthechill oops
11:06 travis-ci RPerl build passed. Will Braswell says 'Generator, Perl Ops Perl Types, OperatorVoid::Named::Return, Part 4'
11:06 travis-ci http://travis-ci.org/wbraswell/rperl/builds/63468091 https://github.com/wbraswell/rperl/compare/49b00cc36562...c4e6c9e909f3
12:23 willthechill nice
12:26 basiliscos joined #perl11
12:34 basiliscos joined #perl11
12:52 basiliscos joined #perl11
12:59 basiliscos joined #perl11
13:04 basiliscos joined #perl11
13:17 basiliscos joined #perl11
13:20 basiliscos joined #perl11
13:29 basiliscos joined #perl11
13:37 basiliscos joined #perl11
13:47 basiliscos joined #perl11
13:55 basiliscos joined #perl11
14:38 basiliscos joined #perl11
14:47 basiliscos joined #perl11
15:06 basiliscos joined #perl11
16:27 basiliscos joined #perl11
18:38 ToApolytoXaos joined #perl11
20:23 willthechill joined #perl11
20:35 ToApolytoXaos greetings willthechill and thank you for the reply today
20:35 ToApolytoXaos i did not know it was Inline::CPP's job to create _Inline anywhere rperl would be called
20:38 willthechill hello my friend!
20:38 willthechill RPerl is not responsible for the _Inline folder, that is automatically created by Inline::CPP
20:38 ToApolytoXaos i have tried to read the entire code (the C++ part) and got lost lol
20:38 willthechill it is the build folder for Inline's automatically-created XS code
20:38 willthechill read the C++ part of what code?
20:39 ToApolytoXaos of the one that did not exist, but thought it existed LOL!
20:39 willthechill I'm sorry, I don't understand
20:40 ToApolytoXaos I thought there was a place somewhere inside the source code, in the form of heredoc
20:40 ToApolytoXaos like the samples from official inline::CPP documentation
20:41 ToApolytoXaos but that was not the case
20:42 ToApolytoXaos basically i was trying to understand why would anyone want to include a .cpp file as a header. i got shocked when i did not find any main() function anywhere
20:42 willthechill I have implemented all possible examples from the Inline::CPP documentation in t/02_inline_c.t and t/03_inline_cpp.t
20:42 ToApolytoXaos oh cool!
20:43 ToApolytoXaos i forgot to check those
20:43 willthechill we currently have no main() function because I am only compiling *.pm Perl modules first, then I will add *.pl Perl programs next
20:44 ToApolytoXaos brilliant!
20:44 willthechill the reason why we include *.cpp files is because of the weird way we have #ifdefs and how Inline::CPP works
20:44 willthechill you keep thinking this is normal C++ code, I have to keep reminding you it is not
20:44 willthechill but that's okay!  :)
20:44 ToApolytoXaos yeah, indeed Inline::CPP is very weird
20:45 ToApolytoXaos yeah, now I know!
20:45 ToApolytoXaos so, basically all I need to care about is the t folder
20:45 ToApolytoXaos and the tests in it
20:45 ToApolytoXaos how they are implemented
20:47 willthechill yes you are correct, it is probably best to start in the t/ folder and go from there
20:47 ToApolytoXaos awesome
20:47 willthechill trying to understand Perl or RPerl core internals from the inside-out is kindof impossible  ;P
20:47 ToApolytoXaos i see you use "using namespace std;" in those tests. is there a reason?
20:48 willthechill I have disabled namespace std to avoid pollution in the main RPerl code
20:48 ToApolytoXaos yeah, i said to myself today to continue with Perl and eventually it will become a necessity to me to learn the internals
20:48 willthechill if it is in use in some t/02 or t/03 then that's fine
20:48 ToApolytoXaos yep, https://github.com/wbraswell/rperl/blob/master/t/03_inline_cpp.t#L102
20:48 ToApolytoXaos it's in t/03
20:49 willthechill that code comes from Inline::CPP docs, not from me
20:49 willthechill I just put it into runnable test format
20:49 willthechill to make sure Inline::C and Inline::CPP can pass their own doc test code before RPerl tests start running
20:50 ToApolytoXaos ah I see
20:50 ToApolytoXaos very nice!
20:55 ToApolytoXaos so, in other words the generated binary file is built around Perl's internals, am I correct?
21:00 willthechill yes
21:01 willthechill the final output of Inline::CPP includes XS code, which is a special intermediary/glue language to bind C or C++ code into the Perl 5 core internals which are also written in C
21:01 willthechill that is why RPerl is a REAL Perl compiler, because it generates exactly equivalent C/C++ code which is then linked back into Perl itself
21:05 ToApolytoXaos absolutely brilliant!
21:05 ToApolytoXaos is it possible though in the future to allow the production of a generic binary file?
21:06 ToApolytoXaos without the use of Perl's internals?
21:09 willthechill yes
21:10 willthechill especially in CPP ops & CPP types mode
21:10 willthechill in CPP ops & PERL types mode, we are very much bound to perl.h
21:10 willthechill in CPP/CPP mode, we are not so much bound to perl.h
21:10 willthechill so in CPP/CPP mode it would be easier to make a stand-alone binary file with no links to perl.h whatsoever
21:10 ToApolytoXaos that's what i wanted to hear!
21:10 willthechill that is the plan
21:11 willthechill that has always been the plan
21:11 ToApolytoXaos i'm very happy right now :D
21:11 willthechill yes you should be
21:11 willthechill that is why I can say RPerl is a REAL compiler!
21:11 ToApolytoXaos i wanted to use my existing Perl knowledge to extend my backend development in no time
21:13 ToApolytoXaos oh man, this means many enthusiasts will use RPerl to develop things like web servers, ala starman and other middleware
21:14 ToApolytoXaos i see a bright future with RPerl
21:15 willthechill haha yes indeed
21:15 willthechill the sky is the limit
21:15 ToApolytoXaos something like that :D
21:15 willthechill nobody will need to write C or C++ any more if they don't want to
21:15 ToApolytoXaos true
21:16 ToApolytoXaos anyway mate, it's time for me to say goodnight.
21:16 ToApolytoXaos see you hopefully tomorrow
21:16 ToApolytoXaos cheers
22:14 bulk88_3 joined #perl11
22:16 d4l3k_ joined #perl11

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