Last night I ran into trouble with the new Time::Local, at first thinking it made incorrect epoch assumptions. It didn't do that, but it did make incorrect assumptions about whether or not time_t was signed or unsigned, and whether or not time() was in seconds since the epoch in local time, or in GMT. Yowzers. However, Graham Barr was exceedingly patient and helpful in arriving at a resolution, and now it passes all tests for me.
So once that got fixed, I tried using MacPerl 5.7.3a1 to run my "compare_slash" program, which uses Mac::Glue (and a dozen other modules) to talk to Interarchy and BBEdit and compare my Slash source trees on my Linux dev box and my local Mac box. And it works just fine. No problems at all; Time::Local had been puking on me, but once it was restored, everything Just Worked. I am therefore fairly optimistic about getting MacPerl 5.8 out the door in what should be (to me :-) a reasonable amount of time. I still have a lot of work left to do on it, but far, far less than what it took for 5.6; mostly just a few more configuration tasks, and then the testing.
So at this point, can we expect to see MacPerl 5.8 before 5.8 is released?
Congrats, pudge. It's cool to have MacPerl that up to date.
Re:Leading or lagging?
pudge on 2002-04-25T15:41:50
Heh, no, no MacPerl 5.8 before perl 5.8. It won't be 5.8 until jhi says so.:) Besides, I won't be ready for some time, with all the testing, and I am probably going to take the occasion of perl 5.8 to add some more features to MacPerl (specifically, improvements to the MacPerl built-in editor) which will lengthen the beta process; however, at this point, it is very likely I will release a MacPerl 5.8 alpha within days of perl 5.8's release. Re:Leading or lagging?
jdavidb on 2002-04-27T21:11:40
Of course, MacPerl 5.6.1, as we all remember from the release announcement, is The Most Advanced perl Ever.
:)
