My guess would be that it's because the loop was very tight. I've seen lots of
instances where tight loops couldn't be interrupted at all. Maybe in this case
it wasn't in basic code when it interrupted, and couldn't find any basic code
within a few steps, so didn't offer D.
On Oct 2, 2013, at
Sounds reasonable.
George
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Ed Clark
Sent: Thursday, October 03, 2013 8:32 AM
To: U2 Users List
Subject: Re: [U2] Interesting
My guess would be that it's because
I don't think this is it.
Perhaps George you could post the full code that is the actual issue, not just
an example.
We could then test it, to see if your symptom can be replicated.
However I still don't like Break=Null, that seems wrong to me.
It should say Break=Intr
-Original
I'm fairly confident that the Break= is not applicable to my connection
Since it's not a serial connection where a break signal could be sent.
The portion that would be applicable is INTR= ^C - which did work,
When I hit control C, it interrupted the program. So the interrupt portion
Isn't
The portion you posted works perfectly fine on my system.
It's quite likely that another portion you didn't post is the problem.
The 'D' option can be turned off in a variety of ways.
Without having more details its not very easy to find the cause.
-Original Message-
From: George
If it worked fine for you, then what's the problem?
-Original Message-
From: George Gallen ggal...@wyanokegroup.com
To: U2 Users List u2-users@listserver.u2ug.org
Sent: Thu, Oct 3, 2013 10:27 am
Subject: Re: [U2] Interesting
Yes, it worked fine for me as well - which is what
Good question...
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Wjhonson
Sent: Thursday, October 03, 2013 1:29 PM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] Interesting
If it worked fine for you, then
It's impossible to debug your situation, without more details.
The code you posted is NOT the problem.
It's elsewhere. To determine where we need to know more details.
Sorry, there's just too many ways to turn off the debugger.
-Original Message-
From: George Gallen
I can't really provide any more details.
What would be the most common ways to turn off the debugger? By not actually
trying...
George
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Wjhonson
Sent: Thursday,
The command that makes the BASIC program *run* supports an option to turn it
off.
That's one way out of dozens
I'm not going to go through them all here :)
-Original Message-
From: George Gallen ggal...@wyanokegroup.com
To: U2 Users List u2-users@listserver.u2ug.org
Sent: Thu,
From this page
http://www.rocketsoftware.com/brand/rocket-u2/technical-documentation/UniVerse-v11.1.11
Select this
UniVerse Transaction Logging and Recovery
and you will get the error
Unable to retrieve document
By the way it says to contact the webmaster and yet there does not appear to
be
oops the compiler... not the run engine
-Original Message-
From: Wjhonson wjhon...@aol.com
To: u2-users u2-users@listserver.u2ug.org
Sent: Thu, Oct 3, 2013 10:54 am
Subject: Re: [U2] Interesting
The command that makes the BASIC program *run* supports an option to turn it
Well that one is an obvious no - since the debugger works at the input
statement in that program,
But wasn't working when it was stuck in the loop.
That is what I meant by by not actually trying - if it's a method that is
intentional to turn
Off the debugger, then that is not the cause -
The only way to help you debug this, is with the full scope of the Area of
code
What is was, what it is.
If you're not willing to show that, there is no way to help you :)
-Original Message-
From: George Gallen ggal...@wyanokegroup.com
To: U2 Users List
14 matches
Mail list logo
