[forwarded submission from a non-member address -- rjk]


From: Sean Quinlan <[EMAIL PROTECTED]>
Date: Mon, 23 Apr 2001 12:59:21 -0400
Subject: PDL/xs problem
To: [EMAIL PROTECTED]

Greetings all! First off subject line - how did the last meeting go?
Unfortunately I couldn't make it. Any discursion of Parrot or the apocalypse?

Anywho, here's my problem. I have a program that uses some PDL routines
that were we've (in the royal sense, the hard work is not mine to claim)
written. If your not familiar with PDL specifically, please keep reading as
it may not matter for this question, it's just a different way of rolling
some c into your perl, and as I understands it, actually generates some .xs
code when compiled. The program does some analysis on protein sequences
(singly or in groups), and is generally given a very large set of sequences
to try.

We are still working on the project and, as you could easily guess, it
fails now and then. That's fine - I'd be happy to dump some debugging info
alongside the core for later perusal. The problem is it brings my program
to a screeching halt, when there is no reason not to just skip that
sequence set on failure and move on to the next. I've tried encapsulating
it in an eval, but it dies regardless. I'm really hoping I don't have to
write a wrapper around it to restart it when it exits prematurely. _Any_
suggestions or pointers to documentation would be greatly appreciated!

TIA!!

--------------------------------------------------------------------------
Sean P. Quinlan
http://people.ne.mediaone.net/squinlan/index.html
mailto:[EMAIL PROTECTED]

"You can discover more about a person in an hour of play than in a year of
conversation" - Plato

Reply via email to