1. More floundering
- Posted by "Wallace B. Riley" <wryly at MINDSPRING.COM> Sep 02, 1997
- 578 views
To anybody in general and Robert Pilkington in particular: My Labor Day message "Floundering" solved itself. I slept on it and in the morning I knew the solution. I had made a mistake in defining a function. Robert: Yes, all variables are declared as global at the beginning of the program, after the 'include' list. I got tired of trying to keep track of which variables were global and which ones didn't have to be; I make 'em all global. No, ED.BAT wasn't deleted. Even so, I still have the same (or a similar) problem. I defined a procedure 'alarm' that alerts me when the program stops unexpectedly. Normally, I expect it to run unattended; I don't figure on sitting here staring at the screen. But somehow, where I call for the alarm to sound in the program, Euphoria thinks I am calling a function or something. It expects a word that isn't there, I think it wants to see 'end' but all it sees is a left parenthesis following the word 'alarm'. I am stumped. I don't think sleeping on this one will solve it, but I might be mistaken. Wally Riley wryly at mindspring.com
2. Re: More floundering
- Posted by Robert B Pilkington <bpilkington at JUNO.COM> Sep 02, 1997
- 557 views
>Robert: Yes, all variables are declared as global at the beginning of >the program, after the 'include' list. I got tired of trying to keep >track of which variables were global and which ones didn't have to be; I make >'em all global. I usually don't have any global variables... >No, ED.BAT wasn't deleted. Okay... >Even so, I still have the same (or a similar) problem. I defined a >procedure 'alarm' that alerts me when the program stops unexpectedly. >Normally, I expect it to run unattended; I don't figure on sitting >here staring at the screen. But somehow, where I call for the alarm to >sound in the program, Euphoria thinks I am calling a function or something. >It expects a word that isn't there, I think it wants to see 'end' but all >it sees is a left parenthesis following the word 'alarm'. I am stumped. Is alarm syntatically correct? Make a test program to call alarm and see if it has the same problem. If it does, fix it.. If not, you've got me stumped! If this doesn't work, try a downsized version of your program, one that doesn't do the processing, and will have an 'error' and need to call alarm. (Basically, delete the main processing code, and make sure that alarm is called) If this doesn't work, try sending the test program, so others can see what is wrong.
3. Re: More floundering
- Posted by "Wallace B. Riley" <wryly at MINDSPRING.COM> Sep 03, 1997
- 565 views
At 03:22 PM 9/2/97 -0400, you wrote: >---------------------- Information from the mail header ----------------------- >Sender: Euphoria Programming for MS-DOS <EUPHORIA at >MIAMIU.ACS.MUOHIO.EDU> >Poster: Robert B Pilkington <bpilkington at JUNO.COM> >Subject: Re: More floundering >------------------------------------------------------------------------------- > >>Robert: Yes, all variables are declared as global at the beginning of >>the program, after the 'include' list. I got tired of trying to keep >>track of which variables were global and which ones didn't have to be; I >make >>'em all global. > >I usually don't have any global variables... > >>No, ED.BAT wasn't deleted. > >Okay... > >>Even so, I still have the same (or a similar) problem. I defined a >>procedure 'alarm' that alerts me when the program stops unexpectedly. >>Normally, I expect it to run unattended; I don't figure on sitting >>here staring at the screen. But somehow, where I call for the alarm to >>sound in the program, Euphoria thinks I am calling a function or >something. >It expects a word that isn't there, I think it wants to see >'end' but all >>it sees is a left parenthesis following the word 'alarm'. I am stumped. > >Is alarm syntatically correct? Make a test program to call alarm and see >if it has the same problem. If it does, fix it.. If not, you've got me >stumped! If this doesn't work, try a downsized version of your program, >one that doesn't do the processing, and will have an 'error' and need to >call alarm. (Basically, delete the main processing code, and make sure >that alarm is called) >If this doesn't work, try sending the test program, so others can see >what is wrong. >Good idea. I'll work on it. I have something else going at the moment, so it'll be a day or two. You'll hear from me. Wally Riley wryly at mindspring.com