Hangup
Nice try, fellas, but it doesn't work. See my earlier message today about
unwarranted assumptions.
Bob Pilkington: My program has several infinite loops in it, put there on
purpose. They begin with 'while 1 do' and every loop has an 'exit' in it.
The hangup occurred before any of these could have been encountered.
You said the 'allow_break(1)' is the default. I inserted it as the third
line in the main routine, right after the line that identifies the routine
and a 'clear_screen' command. If it is the default, I could have cleared
the hangup with a 'Ctrl-C' from the keyboard, but I couldn't. (The hangup
came immediately after the first request for keyboard input. I suspect it
is something sneaky dreamed up by one of those treacherous 'get' statements.)
I already have 'include machine.e' in the program. I *do* read the manual
and I *did* see this specified.
Art Adamson: You said the correct 'include' file is 'file.e'. You cited
the 2.0 manual. You are assuming that I have Euphoria 2.0; I don't have
it. I have Windows 3.1. Rob Craigsaid I had to have Windows 95 before I
could get Eu 2.0. I'm not going to buy Windows 95 until I know what Windows
98 will require as a prerequisite.
Alan Tu: You made the same assumption as Art. Tsk tsk tsk.
Graeme: Your suggestion, to print something on the screen so that I can see
what's happening if anything, is a possibility. I haven't tried it yet, and
frankly I'm dubious, because of the location of the hangup. I suspect that
the program will never get to the special-print statement.
Thanks again, and no hard feelings.
Wally Riley
wryly at mindspring.com
|
Not Categorized, Please Help
|
|
