I am using croak in my XS when a value passed in
or something else is wrong to exit my XS.

But his presents a problem with the .t files I'm writing
for testing.  If I pass a bad value to my xs routine expecting
it to fail, then croak will exit. and the make test will fail.

I think I need to avoid using croak to allow better testing.

Any thought on how to exit a routine cleanly without causing
program to fail?

Do I need to make every xs routine a boolean and pass in
all values to be set as pointers?  THis seems nasty.

my xs file is currently 32k+ lines and rebuilding would be a 
hassle.  I suppose I could just not make function fail where
I need to it in testing, but this doesn't seem right for complete
test coverage :(

Reply via email to