Re: same problem in v4 as previous editions
- Posted by useless Aug 28, 2009
- 1710 views
She is saying that because she edited the source code of a running application that her running application crashed.
True, if i lock the file to read-only, as shown howto in previous post, it won't crash. But if i am bebugging, and running just to get a new ex.err file, and add anything to the source file, it likely will crash with a scrambled source file.
Here's how it works:
- Euphoria reads your source code and parses it as it does so. Any error is reported immediately when found.
- The information generated from parsing is converted into the format that the backend uses, and control is passed from the euphoria written front end to the back end
- The backend fixes up some pointers and initializes itself for running
- The backend starts executing your code
- If a runtime error occurs, the error is reported, based on what is in memory.
Note that it's the same code that executes shrouded [bound] code as normal interpreted code. The default for shrouded code is to get rid of all name information. It always removes the text of your source code, so that you get semi-intelligent error messages, but not the full trace that you would get from a regular interpreted error.
Note that the only time any file is read is when it is first included in your program. Once it gets to the end, it's closed and never read again. I don't know what happened to you, but it wasn't that it tried to re-read anything.
Matt
Even if the news.ex launched a new task with the new included file? Even if it did, however, the IL code should not have been scrambled. The scrambling is always of the same form, some source code is offset, as if a selected text block was shifted the amount of the newly written code, and dropped back at the shifted position. Why it's causing a error in the *executing and running* application, if there is no way to generate new IL code, i dunno.
useless
