1. locked source files
- Posted by gertie at visionsix.com
Jun 10, 2003
Why are Eu source files locked for so long after starting exw on them? It
sometimes takes minutes before i can resave a file.
Kat
2. Re: locked source files
On Mon, 9 Jun 2003 20:53:15 -0500, <gertie at visionsix.com> wrote:
>
>
> Why are Eu source files locked for so long after starting exw on them? It
> sometimes takes minutes before i can resave a file.
Don't have that problem on either of my two mahcines. Maybe its a feature
of Win95? 
--
cheers,
Derek Parnell
3. Re: locked source files
gertie at visionsix.com wrote:
> Why are Eu source files locked for so long after starting exw on them? It
> sometimes takes minutes before i can resave a file.
Check your task list (control-alt-delete) to see if you have
any exw.exe processes still running in the background,
maybe waiting for input.
Obviously exw.exe has to open your source files for reading,
and it can't close them until it has finished reading them.
For an include file, that's right after the include is processed.
For the main source file, it's when it reaches the end of the file.
If you start the main processing of your program at the very end
of the main file, e.g. with a call to a main routine, then
the chances are pretty good that exw will have already closed
the main file, having read the last chunk in from the disk.
At one time, I used to close the Euphoria source file after
parsing the last statement, but I changed it to close
immediately after reading in the final (up to) 4K-byte chunk.
That allows me to edit ed.ex using ed.
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
4. Re: locked source files
- Posted by gertie at visionsix.com
Jun 10, 2003
On 10 Jun 2003, at 1:25, Robert Craig wrote:
>
>
> gertie at visionsix.com wrote:
> > Why are Eu source files locked for so long after starting exw on them? It
> > sometimes takes minutes before i can resave a file.
>
> Check your task list (control-alt-delete) to see if you have
> any exw.exe processes still running in the background,
> maybe waiting for input.
Nope. None.
> Obviously exw.exe has to open your source files for reading,
> and it can't close them until it has finished reading them.
Of course, but there are times when it is well into it's own reading and writing
of files, before the source code file is unlocked!
> For an include file, that's right after the include is processed.
> For the main source file, it's when it reaches the end of the file.
Yeas, but these aren't being unlocked till after a webpage has been
processed, for instance.
Kat
