Stories
Slash Boxes
Comments

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

2shortplanks (968)

2shortplanks
  (email not shown publicly)
http://2shortplanks.com/
AOL IM: trelane2sp (Add Buddy, Send Message)
Yahoo! ID: trelane2sp (Add User, Send Message)

Mark Fowler has never been the same since he was elected leader of the London Perl Mongers. The strain manifests itself mainly in releasing various [cpan.org] modules [cpan.org] to CPAN, giving talks [2shortplanks.com], and use of the Trelane nick on #london.pm for endless procrastination. Doctors are still seeking a cure.
Sunday August 15, 2004
06:13 PM

Have xcode, will cargo cult. DANGER: Thunking ahead.

[ #20419 ]
So, Perl wise, I've made a start on the thunking layer. It now seems to work okay - in the end I did it by polluting the error classes with extra methods. It's all a bit "run it and see if I get the right errors" atm. What I have at the moment in theory is the one I build to throw away (but we all know how often we end up keeping those.)

My next step is to beef up the test suite - the whole things runs out of an Apache::Test environment - so I can check that you can catch all the errors in the right place.

I've also been cargo culting like crazy with SubEthaFari which is a little mac xcode project that you build and shove in the right place in your ~/Library and through some crazy method swizzling (Object-C symbol replacing) it causes Safari to open it's source in SubEthaEdit rather than it's own source code viewer. This would be great, apart from two things. One, I can't use SubEthaEdit at work without either breaching the license terms or paying for it. Secondly, it's not emacs or vi.

So I followed the advice of others and did the two line change that made it work with the carbonised Emacs.app.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.