"Possibly" it finds a different program or libcob than you think. You may could check this when opening dependencies from the non-working environment and see which cobcrun/libcob it points to.
An executable created by cobc -x will do the explicit initialization as cobcrun also does before the COBOL module is started. I guess you use one of those ways to start the test program.
As noted before: it is totally possible to swap pdcurses,dll's to swap between the ports as long as:
all ports were build from the same PDCurses[Mod] version
all ports were build using the identical defines
As the whole initscr-hidden-rename-feature was done to ensure this and I see no reason why that should not work, you're likely "safe here" with PDCursesMod431.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The problem demonstrated itself as follows - I have a batch file that compiles a particular program and then directly runs the .exe - this worked fine.
I 'can ' then go later & just run the .exe & this is what didn't work.
Why something got screwed up that rebooting the machine fixed I'll prob never know.
All ports wincom & vt (possible cause of problem) were built from same pdc431 with identical defines - so go figure. Case closed I hope.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Deleted this post - Rebooted the PC & all came good - why ?? - who cares ??.
As Roy from ' The IT Crowd ' would have said:
"Have you tried turning it off and on again?"
Last edit: David Wall 2021-12-07
"Possibly" it finds a different program or libcob than you think. You may could check this when opening dependencies from the non-working environment and see which cobcrun/libcob it points to.
An executable created by
cobc -xwill do the explicit initialization ascobcrunalso does before the COBOL module is started. I guess you use one of those ways to start the test program.As noted before: it is totally possible to swap pdcurses,dll's to swap between the ports as long as:
As the whole initscr-hidden-rename-feature was done to ensure this and I see no reason why that should not work, you're likely "safe here" with PDCursesMod431.
The problem demonstrated itself as follows - I have a batch file that compiles a particular program and then directly runs the .exe - this worked fine.
I 'can ' then go later & just run the .exe & this is what didn't work.
Why something got screwed up that rebooting the machine fixed I'll prob never know.
All ports wincom & vt (possible cause of problem) were built from same pdc431 with identical defines - so go figure. Case closed I hope.