That's OK with me.
Ken
On 9/15/2011 5:28 PM, Michael Haberler wrote:
> Ken -
>
> thanks for the explanation. It was unclear from the code what this was for,
> and I didnt find it in the docs.
>
> Am 15.09.2011 um 18:51 schrieb Kenneth Lerman:
>
>> The reason USE_LAZY_CLOSE was originally put in
Ken -
thanks for the explanation. It was unclear from the code what this was for, and
I didnt find it in the docs.
Am 15.09.2011 um 18:51 schrieb Kenneth Lerman:
> The reason USE_LAZY_CLOSE was originally put in the code was so that
> after loading a file, it would not be closed until another
The reason USE_LAZY_CLOSE was originally put in the code was so that
after loading a file, it would not be closed until another one was
opened. That way, MDI code could call subroutines in the (still open) file.
I haven't followed how things have changed since I originally
implemented that klud
Michael Haberler wrote:
> I failed to explain why I tagged this as 'serious'. The reason is: it can
> lead to accidential execution of code which should not be executed.
>
I don't think you need to explain this to most programmers, the
implications were QUITE
obvious to me. Thanks much for di
I failed to explain why I tagged this as 'serious'. The reason is: it can lead
to accidential execution of code which should not be executed.
to demonstrate, try the following foo.ngc and go through the steps described.
foo.ngc:
(DEBUG, this shouldnt be executed because it's not part of a
