03-06-2006, 07:14 AM
I tried Moneo's suggestion and removed my ON ERROR RESUME NEXT lines, which I used in various places to test for missing files. Then I removed both the compiler flag /E for ON ERROR support and the flag /X for RESUME NEXT support.
Removing /E didn't make any difference, but removing /X gave me over 11,000 bytes, almost a quarter of the work space. Since I've already determined that a 1000 line routine of moderate complexity uses about 1500 bytes of compiler workspace, this should give me enough room to keep working for quite a while.
I still need to go back and code some replacement tests for the ERROR checks that I removed for this test. And I have to verify that I can link with libraries compiled with the error flags (or remove ON ERROR in each library).
I also have to agree with his advice about porting to FB. Unless the port is extremely straightforward (and my database usage makes this unlikely), I've got to treat it like any major porting task. If I'm going to do that much work, both coding and testing, why not bring it up out of the stone age and use a real database? Most of the work in this particular program is procedural, but most of my other programs revolve around data transformations.
Anyway, thank you everyone for your suggestions and willingness to help,
Mark
Removing /E didn't make any difference, but removing /X gave me over 11,000 bytes, almost a quarter of the work space. Since I've already determined that a 1000 line routine of moderate complexity uses about 1500 bytes of compiler workspace, this should give me enough room to keep working for quite a while.
I still need to go back and code some replacement tests for the ERROR checks that I removed for this test. And I have to verify that I can link with libraries compiled with the error flags (or remove ON ERROR in each library).
I also have to agree with his advice about porting to FB. Unless the port is extremely straightforward (and my database usage makes this unlikely), I've got to treat it like any major porting task. If I'm going to do that much work, both coding and testing, why not bring it up out of the stone age and use a real database? Most of the work in this particular program is procedural, but most of my other programs revolve around data transformations.
Anyway, thank you everyone for your suggestions and willingness to help,
Mark