Jonas Maebe-2 wrote
The internal representation of real numbers has never been changed in
FPC. .
I may have expressed myself incorrectly, but there was the case when records
of real numbers written to disk by a program compiled with fpc 1.0.4 , when
read back by the same program compiled
You seem to know your way around, Bernd, don't you!
Well, I've tried xterm -hold -e /my/program :
the xterm-window pops up and stays with nothing in it at all: no error and
no program output [which should be there]: seems to me that the program
isn't being run at all! That is if it is compiled
On 09 Mar 2012, at 10:24, max wrote:
My general wish for the compiler programmer would be that old
versions would
still be available and installable in the future as new versions
sometimes
show strange behaviours on old prorgams
They generally remain available. However, versions prior to
Am 09.03.2012 10:24, schrieb max:
You seem to know your way around, Bernd, don't you!
Well, I've tried xterm -hold -e /my/program :
the xterm-window pops up and stays with nothing in it at all: no error and
no program output [which should be there]: seems to me that the program
isn't being run
Can you put a sleep behind it to see the error message?
xterm -e ./project1 ; sleep 10
I cannot imagine how the version of the compiler can have any
influence on that. Either the compiled program runs on your system or
it doesn't run at all.
Does your program maybe simply crash because you are
2012/3/4 Bernd prof7...@googlemail.com:
Can you put a sleep behind it to see the error message?
xterm -e ./project1 ; sleep 10
And also do the following:
env env_interactive.txt
xterm -e env env_non_interactive.txt
and then compare the two files. If important environment variables are
Done what you suggested:
program runs again via xterm -e program ; sleep 0 with fpc 2.4.0; however
no error message; same with 'sleep 10' !
So Thank You very much for that, Bernd !
Without the appended '; sleep ' just the flicker.
env: only difference is SHLVL , namely =4 for interactive vs. =5
2012/3/5 Bernd prof7...@googlemail.com:
it was only meant to keep the xterm
open a few more seconds to read any error message that *might* occur
when your program refuses to run.
you can also try the following (more elegant):
xterm -hold -e yourprogram
without the sleep. This would hold the
Thank you for your tips and suggestions.
It seems that FPSYSTEM from rtl-Sysutils is the 1:1 replacement for the old
SHELL function but that made no difference to my problem.
I dug out the previsious fpc version 1.9.4 from archive.debian.org which
fortunately could be installed [for how long?]
