, though we are rather fond of them for obvious reasons.
Submitted by rohit_nsit08 on Tue, 07/12/2011 - 15:52
hmm.. that was a long delay in blog posts , but I'm glad to inform that corella has started flying , I mean producing output in PIR . though broken in many places but it has started and is getting updated every hour now .
I am planning to have a meeting with coke about the so far delayed test-suite as I'm really feeling the need of that.
As far as object system is concerned, I had meeting with coke few days ago and they will be in code before the end of mid term evaluation.
Submitted by bubaflub on Tue, 07/12/2011 - 02:49
This week I finished implementing VTABLE overrides for Parrot-GMP. This allows us to do things like x = y + z where x, y, and z are all GMP Integer objects. I also have a test suite to ensure that these overrides work. It's not very glamorous work but it's a nice layer of sugar and makes sure that Parrot-GMP plays nice with others.
Submitted by benabik on Sun, 07/10/2011 - 17:56
I want to talk about what I need to do over the next couple weeks, and in order to do that, I'm going to start with a description of the system I'm working on. This was originally a much longer post, but I accidentally overwrote my first draft with something else. This is probably good since the first one read more like a reference manual.
Submitted by soh_cah_toa on Sun, 07/10/2011 - 01:06
Nothing too spectacular went on this past week. It mostly consisted of typical technical work. If I had to pick one thing that was significant, it would be that I was able to eliminate all build warnings/errors in gcc and g++. Eliminating those warnings was incredibly irritating and honestly, I don't really know how I fixed it. Actually, I shouldn't say that. I do know how I fixed it but what I don't understand is why the first method didn't work in the first place but this one does. Oh well...it works.
Submitted by bubaflub on Sun, 07/03/2011 - 02:44
This week many Parrot-teers and Perl hackers (and many of my co-workers) were at YAPC::NA. I originally planned on attending but my car broke down earlier this summer and I had to pay for repairs. While there dukeleto++ (my GSoC mentor) and colomon++ both asked how to install Parrot-GMP. I had been so focused on getting the guts and the test suite together that I had completely neglected my README and had no way of automating an install.
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.