, though we are rather fond of them for obvious reasons.
Submitted by benabik on Sun, 07/03/2011 - 02:15
So, when I was making my schedule, I didn't know about YAPC. But I made plans, grabbed a friend, and went. Met lots of cool people. But I just now got home from a 16 hour drive so both the blog post about YAPC and the blog post about PAST, POST, and newPOST will have to be delayed until after I catch up on some missing sleep.
Submitted by soh_cah_toa on Sat, 07/02/2011 - 02:32
I must be brief again as 1) I am using my laptop which has a terrible battery and 2) I am writing from the car and this is making me carsick. :-C~
This past week was a little bitter sweet. Bitter because I did not have much time for GSoC work but sweet because I was at YAPC::NA with some of the other Parrot developers. As much as I would like to talk about YAPC (which was awesome sauce), I must limit myself to GSoC-only topics.
Submitted by jkeenan on Sat, 07/02/2011 - 01:33
There is no substitute for face-to-face contact.
Salespeople have to meet their customers in person. Marketing alone will never suffice.
Politicians have to press the flesh. Television ads will never suffice.
Open-source software projects' developers have to meet F2F. IRC will never suffice.
That's the main lesson I draw from YAPC::NA::2011, just concluded in Asheville, North Carolina.
Submitted by rohit_nsit08 on Thu, 06/30/2011 - 15:21
Seems to be the toughest part of the project, providing inbuilt object's support. Thanks to the specification provided by Ecmascript, finally got hold of whole Object thing. Time to speed up my work now..
Submitted by bubaflub on Sun, 06/26/2011 - 03:34
Nothing too glamorous to report again - the test suite continues to grow. All functions are currently covered (and passing) except for functions related to random numbers. These functions are especially tricky because they rely on a special C-struct to both hold the seed and point to which pseudo-random number function we want to use. GMP is flexible in that there are multiple functions a user can choose from - some which favor speed and others which favor randomness - but the code is messy. Furthermore, to handle structs in NCI we need something called a StructView.
Submitted by soh_cah_toa on Sun, 06/26/2011 - 00:27
This week in HBDB-land was very significant. I was finally able to achieve command recognition. I had abandoned work on it for about a week because it was such a nuisance. Instead, I focused on testing which was a pain as well but it got done. Reluctantly, I returned my focus to the command parsing logic and within 5 minutes, I had solved my problem with a single ampersand. This makes me so happy.
Submitted by NotFound on Sat, 06/25/2011 - 15:03
Submitted by benabik on Tue, 06/21/2011 - 21:03
I've lost more time to the bog that is removing Q:PIR blocks. I keep triggering odd little bugs and only have the most complicated bits left. There are 7 Q:PIR blocks, of which 3 are to handle the multiple return values from
post_children(). On bacek's advice, I'm going to just not worry about the last few bits. I'd really like to get rid of them by the end of summer, but at this point it's blocking forward progress.
Also, my pool has a pile of problems. It's green and the pump is broken and and and... I'm sure very few people care, but the repeated trips to the pool store are eating up far more time than I had intended.
Submitted by lucian on Mon, 06/20/2011 - 18:49
Double puffin this week! And that's to (partly) make up for my short 3 day vacation to Scotland, starting tomorrow.
Submitted by soh_cah_toa on Sun, 06/19/2011 - 02:00
Ok, not literally. Though I wonder what code would actually smell like. Burning brain cells, maybe?
Alright, here's the scoop. I'm going to keep things brief as I eagerly want to get back to my adorable little segfaults. :)