|
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. |
|||
|
07:01
denisboyun joined
15:09
bluescreen joined
16:55
pmurias joined
|
|||
| pmurias | Prereport: | 16:55 | |
| Salvaged a iscclass test from nqp-jvm. | |||
| Stomping bugs popping up in the regex tests. | |||
| Found a bug in how rxtype ws is handled in nqp. | |||
| Fixed NQPMatch.dump in nqp. | |||
| sa1 | Pre-report | 17:33 | |
| * Working on git objects(which was removed two weeks back) | |||
| * Fix case-sensitive folders(Issue 17) | |||
| * Implement ls-tree plumbing | |||
|
18:15
Tene joined
18:28
lizmat joined
18:49
denis_boyun joined
|
|||
| denis_boyun | Pre-report: | 19:16 | |
| # Done: | |||
| * Library is supporting rosella(winxed), rosella(nqp) and perl5 test system languages | |||
| # Doing: | |||
| * done api more and more smart(clean old zip project) | |||
| sa1 | Util: ping | 19:31 | |
| denis_boyun: hello | 19:32 | ||
| denis_boyun | sa1: hi | ||
| Util | Hello! Who all is in attenance? | ||
| sa1 | Hello, Util | ||
| Util has apparently had a alarm failure | 19:33 | ||
| Done: Helped denis_boyun with rosella. Problem resolved! | 19:34 | ||
| denis_boyun | Util: hi' | ||
| Util | .end | ||
| Hello, denis_boyun | |||
| Looks like good progress from everyone. Do you all feel that you have made up the lag from earlier in your projects? | 19:35 | ||
| In other words, are you on schedule now? | |||
| sa1 | I'm sorry for the lack of posts. I've had 2 intern interviews from visiting campus companies this week, and had a couple of crypto assignments too. | 19:36 | |
| I'm not on schedule, no. But its a git api you can work with. | 19:37 | ||
| Util | I was just about to type: "We are missing last week's reports on Parrot.org from pmurias and sa1." | ||
| sa1 | There are a lot of things that are missing, but I guess the the last couple of weeks should be used to polish, make things usable, and keep adding tests. | 19:38 | |
| denis_boyun | Util: Library template has almost done and i'm working on hll template again | 19:39 | |
| Util | FYI: This is something you will find in the commercial world; progress reports are even *more* important when progress has stalled. Annoying, but true. | ||
| denis_boyun: sounds good | |||
| denis_boyun | Util: Yes, I have questions when you are take me some advice i can continue my work | 19:40 | |
| sa1 | Util: I'm looking at the plumbing commands that can be done using whats working. | 19:41 | |
| denis_boyun | Util: i've sent email with question about perl 5 build system languages and hll tests | ||
| sa1 | ls-tree was a simple enumeration of objects | ||
| Util | sa1: In general, I agree that what you have working should be polished so that it is usable by others, rather than adding more features. However, you should verify with dukeleto. | ||
| sa1 | True. | 19:42 | |
| Util | denis_boyun: Do you mean your email from August 29th? | ||
| denis_boyun | Util: yes | 19:44 | |
| Util: How to test a hll-project? | |||
| Util | denis_boyun: To test your HLL, I see two different approaches: | 19:46 | |
| 1. Use a harness program (written in winxed, or Perl 5) to execute `hll.exe test_script_1.abc`, and capture its output, and compare it to the expected output. You would use Winxed's (or Perl 5's) Test libraries for this. | |||
| 2. Have your code write a harness library in the new language, and also provide skeleton test scripts in the new language that will use the harness library. | 19:47 | ||
| I do not know if #2 is too ambitious, since you do not know everything about the generated language until generation-time. | 19:48 | ||
| Also, #1 is more in line with what you are already doing with library testing. | 19:49 | ||
| denis_boyun | Util: yes, #1 like me more than #2 | 19:50 | |
| Util: ok i undestand | |||
| Util | sa1: a perfectly working, well-documented ls-tree will be a great outcome, in my opinion. | 19:51 | |
| sa1 | The index example was more my aim. ls-tree is a small thing really. | ||
| Util | denis_boyun: In your email, you asked dukeleto about whether building the module to provide build utilities was needed or not. I have no new thoughts on that, so I will leave it to dukeleto to give you his answer. | 19:52 | |
| sa1: Do you think you can complete the index example in the timeframe of the project? | 19:53 | ||
| sa1 | I won't consider it successful unless I do that, since I've been working towards it. | 19:54 | |
| I would say yes to that end. | |||
| Util | sa1: Even better. Let me (and dukeleto) know what help you need. | ||
| Any other blockers, from either of you? | 19:55 | ||
| denis_boyun | Util: no | 19:56 | |
| sa1 | No blockers. | ||
| Util | Anything else to discuss? | ||
| sa1 | No | ||
| denis_boyun | no | 19:57 | |
| Util | GSoC students: Remember to post to Parrot.org and parrot-dev. pmurias: This means you too! | ||
| Thank you all for participating! | |||
| Meeting adjourned. | |||
|
21:00
bluescreen joined
|
|||