Post closed tickets in your report. | Note: This channel is for our weekly status meetings (Tuesdays at 19:30 UTC); you probably want #parrot instead. | irclog: irclog.perlgeek.de/
Set by moderator on 31 August 2013.
06:42 denisboyun joined 10:32 denis_boyun joined 13:36 bluescreen joined 14:15 darbelo joined 14:27 sa1 joined 14:42 bluescreen joined 16:03 bluescreen joined 16:07 bluescreen joined
sa1 Pre-report 16:16
# Complete index examples
# Added Commit Parsing, Remotes, Tags library functions
# Working on References
# More tests
# Productive week, almost back on schedule.
16:34 pmurias joined
pmurias gsoc prereport: 16:34
Got the nqp/t/qregex tests to pass.
It would be a good idead for me to document how the rules engines of the MoarVM, Parrot, JVM and JavaScript backends work.
They are pretty similiar as it's basically the translation of the same code.
Unfortunately some things get cargo culted. 16:35
Like parrot registers names ending up in MoarVM code.
This means the rules engines implementation is resonably sane.
Incorrect test description caused a lot of confusion.
[link that fixes that]
Had the backend working previously so once hooked it was almost working.
Had to rid of the last pir:: op.
Fixed a multi problem.
Put a nqp-runtime dir in node_modules.
Some bugs got found by running the NQP code.
Like $match<no_such_key> not returning NQPMu.
Fixed those.
nqp::say("Hello World") now works in a standalone NQP (NQP which is compiled to JavaScript )
Need serialization to get the setting to work.
Currently only have deserialization on the JavaScript side.
It's the only big piece missing.
Once we get the setting working the rest should be bugs.
The rest should be bugs.
And some new IO tests which recently got added.
They IO tests are for features which Rakudo uses.
Working on it right now.
17:52 denisboyun joined 18:02 bluescreen joined
denisboyun # Done: 19:19
* HLL is supporting rosella(winxed), rosella(nqp) and perl5 tests
# Doing:
* done api more and more smart(clean old zip project)
* library template need only a perl5 build system
* hll template need to support perl5 build system languages
.end
Util Pre-report: 19:29
Doing: Working on Parrot promo materials for Mentor Summit.
.end
denisboyun Util: hi 19:30
Util Hello, everyone. Who all is in attendance?
sa1 Hello
denisboyun hi 19:31
sa1 So this is the last week, and I think I've roughly caught up in schedule. Considering last week's pace, I'll be able to satisfy original objectives in a week's time I think. 19:32
Util Looking at your reports, it was a good week for all of you.
sa1: excellent!
sa1 Util: I've been working around a lot of problems with the C wrapper.
dukeleto said that it was a good interim solution. 19:33
But in the future, more stuff needs to be done in winxed.
I need to learn how to pass double pointers to C functions, and getting data out of unmanaged structs before that is possible. 19:34
denisboyun Util: i've almost done the project, the last step is supporting perl 5 build system language
Util denisboyun: Great! If you get stuck on that part, I should be able to get you unstuck quickly. 19:35
denisboyun Util: dukeleto hasn't answered on my email about perl 5 build system 19:36
Util: yes i have a one questions
Util denisboyun: What was the date of that email?
denisboyun Util: 29 of August 19:37
sa1 Also even if the C wrapper turns out to be necessary in the end, I should be able to properly package it in a shared library. 19:38
Util sa1: Great! If you need instruction (rather than research) on those two issues, remember that a thorough write-up (with almost-working code) helps us to help you, when you present us with the questions.
sa1 I'll write a proper email describing those things then. 19:39
Util denisboyun: The "buildd" part of that email boils down to: "So what do you think about it? Is it necessary or not?"
denisboyun Util: yes 19:40
Util denisboyun: Please expand that part of the email into a more thorough question. It is unclear what is holding you up there. The expanded email will give dukeleto (and me) a better chance to assist.
denisboyun: What is the other question that you just mentioned? 19:41
sa1: Great; thanks.
denisboyun Util: where I can see the correspondence between(on Winxed pbc_pir key is calling parrot -o...). Can i see that somewhere
? 19:42
Util denisboyun: By "correspondence", do you mean the project documentation, or some email or IRC thread? 19:43
denisboyun Util:If you have a documentation on that it would be cool 19:44
Util: i mean some information about it
Util denisboyun: This is all I see on it: whiteknight.github.io/Rosella/libra...inxed.html 19:45
Search for "pbc_pir".
Beyond that, I am unclear on exactly what you are searching for. Perhaps the Rosella code itself contains the call to `parrot -o...`? 19:46
sa1 Hmm, that rosella setup thing seems to be a replacement for github.com/letolabs/parrot-libgit2...winxed#L79 19:49
denisboyun Util: No. when you compile hll with winxed(for example). when you write var data = {
"pir_winxed" : {
"my_winxed_file.pir" : "my_winxed_file.winxed"
}, winxed know what kind of command called for this instruction
Util: i want to realization that for perl5 19:50
Util denisboyun: Looking...
denisboyun Util: some special module for that, like you are talking me 19:51
Util: winxed, nqp and pir know about this instruction and call the same command for all instruction. 19:55
sa1 denisboyun: are you referring to this? github.com/parrot/parrot/blob/mast...s.pir#L545 19:56
Util denisboyun: Since pir knows about it, you can invoke the code via runtime/parrot/library/distutils.pir
In other words, you can write some code in pir, using distutils, and invoke it in Perl via backticks, or system("parrot my_distutils_wrapper.pir"); 19:58
denisboyun Util: ))))I understand you. 19:59
Util: I falsely thought
Util: thnx 20:00
Util denisboyun: You are welcome. Let us know what else you need. 20:01
Anything else to discuss? (GSoC or not)
sa1 No
denisboyun Util: ok.
No
Util GSoC students: Remember to post to Parrot.org and parrot-dev! 20:02
sa1 yes 20:03
Util sa1: Go ahead.
sa1 Util: That yes was a reply to the 'remember to post'.
Util sa1: Ah, OK.
I thought you meant "yes, something else to discuss". 20:04
Thank you all for participating!
Meeting adjourned.

Powered by Cro and the Raku® Programming Language.

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

Thank you!