1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Another debugger observation

Discussion in 'Support' started by vefatica, Sep 11, 2010.

  1. vefatica

    Joined:
    May 20, 2008
    Messages:
    8,129
    Likes Received:
    33
    I noticed that IDE's built-in TCC has _TRANSIENT == 1. I doubt it will bother me but some might be surprised by unexpected results. If it must be so for correct functioning, it should probably be documented.
     
  2. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    10,092
    Likes Received:
    85
    It always has, since the very first debugger version many years ago. As
    does any batch file that's not run directly from the TCC prompt.

    (And it's *not* a built-in TCC, as it only includes the scripting capability
    and not the command line interface.)

    Rex Conn
    JP Software
     
  3. vefatica

    Joined:
    May 20, 2008
    Messages:
    8,129
    Likes Received:
    33
    On Sat, 11 Sep 2010 18:31:26 -0400, rconn <> wrote:

    |(And it's *not* a built-in TCC, as it only includes the scripting capability
    |and not the command line interface.)

    Funny that you mentioned that. I have been meaning to suggest (for a future
    version) that it would be convenient to have a combo-box where you could enter
    commands (while not debugging) to be executed by IDE's interpreter to, for
    example, stop a running TIMER or close a file (either of which might be left by
    an aborted debug session).
     
  4. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    10,092
    Likes Received:
    85
    You already can (Alt-F11).

    Rex Conn
    JP Software
     
  5. vefatica

    Joined:
    May 20, 2008
    Messages:
    8,129
    Likes Received:
    33
    On Sat, 11 Sep 2010 21:13:24 -0400, rconn <> wrote:

    |You already can (Alt-F11).

    Could you allow commands there too?
     
  6. vefatica

    Joined:
    May 20, 2008
    Messages:
    8,129
    Likes Received:
    33
    On Sat, 11 Sep 2010 22:01:45 -0400, vefatica <> wrote:

    |On Sat, 11 Sep 2010 21:13:24 -0400, rconn <> wrote:
    |
    ||You already can (Alt-F11).
    |
    |Could you allow commands there too?

    Never mind. That's easy enough with @EXEC.

    Hmmm! I evaluated %@EXEC{timer on] and a few seconds later, %@EXEC[timer off].
    In the console I saw

    Code:
    Timer 1 on: 22:20:56
    Timer 1 off: 22:21:08  Elapsed: 0:00:00.00
    That looks fishy.

    If I keep evaluating %@EXEC[timer] over and over I see

    Code:
    Timer 1 on: 22:26:35
    Timer 1 on: 22:26:44
    Timer 1 on: 22:26:47
    Timer 1 on: 22:26:48
     
  7. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    10,092
    Likes Received:
    85
    Not possible. But you can use @EXEC.

    Rex Conn
    JP Software
     
  8. vefatica

    Joined:
    May 20, 2008
    Messages:
    8,129
    Likes Received:
    33
    Yeah, but it's not perfect (see my other post).

    I wouldn't mind that Alt-F11 thing in a combo box (with memory) on the toolbar.
     
  9. vefatica

    Joined:
    May 20, 2008
    Messages:
    8,129
    Likes Received:
    33
    Or, as a dialog, the ability to leave it open.
     
  10. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    10,092
    Likes Received:
    85
    Not possible; it'd mangle your batch file results.

    Rex Conn
    JP Software
     
  11. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    10,092
    Likes Received:
    85
    WAD. You're not running a persistent interpreter in the evaluate expression
    dialog. (Nor do I see any useful purpose in that.)

    Rex Conn
    JP Software
     
  12. vefatica

    Joined:
    May 20, 2008
    Messages:
    8,129
    Likes Received:
    33
    On Sat, 11 Sep 2010 23:22:44 -0400, rconn <> wrote:

    |---Quote---
    |> Hmmm! I evaluated %@EXEC{timer on] and a few seconds later,
    |> %@EXEC[timer off].
    |> In the console I saw
    |>
    |> Code:
    |> ---------
    |> Timer 1 on: 22:20:56
    |> Timer 1 off: 22:21:08 Elapsed: 0:00:00.00
    |> ---------
    |> That looks fishy.
    |>
    |---End Quote---
    |WAD. You're not running a persistent interpreter in the evaluate expression
    |dialog. (Nor do I see any useful purpose in that.)

    The whole idea originally came from wanting to stop a TIMER that was left
    running when I aborted a debug run (because it was still on when I started
    debugging again). Can that be done? What if I abort a debug run after
    @FILEOPEN and without @FILECLOSE? Can I use Alt-F11 to evaluate @FILECLOSE and
    close the handle? If not, is there any way to close it?
     
  13. vefatica

    Joined:
    May 20, 2008
    Messages:
    8,129
    Likes Received:
    33
    > ---Quote (Originally by vefatica)---
    > Yeah, but it's not perfect (see my other post).
    >
    > I wouldn't mind that Alt-F11 thing in a combo box (with memory) on the
    > toolbar.
    > ---End Quote---
    > Or, as a dialog, the ability to leave it open.

    > Not possible; it'd mangle your batch file results.

    It would benefit from some history recall then (ITNV of course).
     

Share This Page