Craig A. Berry wrote:
I started moving a '__END__' through pack.t to figure out why it wouldn't run. It seemed to be dying without any notice during compilation as only BEGIN blocks would run.At 10:43 PM -0400 7/22/04, Thomas Pfau wrote:
I'll dig into the pack problem a little and see what I can come up with. That one's pretty important to me.There's a high probability the pack problem is floating point related as well.
I was about 2/3rds through the file when it stopped running. I commented out the immediate section of code and was able to run what remained. Uncommenting the section caused it to die again.
In that section of code, there are some large floating point constants (1.36514538e67). The VAX range appears to be about 1.7e38. I get the feeling that these are causing perl to crash but it doesn't even print any messages. I have a perl script that prompts for perl code and executes it. If I enter one of these numbers, the script unceremoniously exits. If I try using very large floating point constants on linux, the variable gets assign 'inf' instead.
Is perl not trapping floating point exceptions properly on VMS?
Anyway, I reconfigured and rebuilt with /G_FLOAT today and op/pack.t passes but some other tests are now failing. On Monday I'll compare the results of the first build with the results of the /G_FLOAT build to see what changed. The tests hadn't completed before I left work today (3:43 to build, will probably take as long to test).
