procedure variables...

BackupUser · Post by **BackupUser** » Fri Apr 11, 2003 1:00 pm

Restored from previous forum. Originally posted by Skipsy.

Hi folks,

Is there any tip to see variable declared on procedures ???

Damn !! I must use global when I want to trace var values...

Thks a lot.

"If you want to touch the sky,
f**k a duck and try to fly"

BackupUser · Post by **BackupUser** » Fri Apr 11, 2003 2:17 pm

Restored from previous forum. Originally posted by GPI.

Try debug:

Code: Select all

  procedure test(a,b,c)
    debug "test:"+str(a)+" "+str(b)+" "+str(c)
    ...code...
  endprocedure

  for i=0 to 100
   test (i,i*20,i+100-43)
  next
[code]

PII 333, 256MB, Asus TNT2Ultra 32MB, AWE Gold 64 4MB

BackupUser · Post by **BackupUser** » Sat Apr 12, 2003 8:17 am

Restored from previous forum. Originally posted by Skipsy.

Works fine, thnks.

I am just wondering why PB developpers choose to do not give access
to procedures variables via the "variables" window.

Enjoy.

"If you want to touch the sky,
f**k a duck and try to fly"

BackupUser · Post by **BackupUser** » Sat Apr 12, 2003 10:10 am

Restored from previous forum. Originally posted by GPI.

I think the debug command is usefuller.

With debug you can get a history of the variables and you can combine with if, etc.

PII 333, 256MB, Asus TNT2Ultra 32MB, AWE Gold 64 4MB

BackupUser · Post by **BackupUser** » Sat Apr 12, 2003 11:06 am

Restored from previous forum. Originally posted by tinman.

Originally posted by Skipsy

I am just wondering why PB developpers choose to do not give access to procedures variables via the "variables" window.

Because the debugger isn't very good now. However, Fred knows this and hopefully it will improve someday.

--
I used to be a nihilist but I don't believe in that any more.
(Win98first ed. + all updates, PB3.51, external editor)

BackupUser · Post by **BackupUser** » Sat Apr 12, 2003 3:00 pm

Restored from previous forum. Originally posted by Skipsy.

Yes, in some situations it could be userfuller. The negative point is
that we have to think what we'll need to display before running the
app. We can't access to the data "on the fly".

You know, I am not criticizing PB. I have really GOOD TIME with it.
Of course everything can be improved... as long as it is not
against the quality of the generated code.

Just a very personal suggestion : with all previous languages I used
to try (C, ASM, JAVA) it is very powerfull to add/remove breakpoint
when debugging. With PB, as breakpoints seem to be part of the code
(set when compiling) I understand it is not possible.

ww

"If you want to touch the sky,
f**k a duck and try to fly"

BackupUser · Post by **BackupUser** » Sat Apr 12, 2003 4:27 pm

Restored from previous forum. Originally posted by GPI.

try "calldebugger"

PII 333, 256MB, Asus TNT2Ultra 32MB, AWE Gold 64 4MB

BackupUser · Post by **BackupUser** » Sat Apr 12, 2003 5:41 pm

Restored from previous forum. Originally posted by tinman.

Originally posted by GPI

try "calldebugger"

But you cannot do that "on-the-fly" while you are already debugging (which was Skipsy's point). It must be possible though since you can press the "Stop" button in the debugger to stop your code.

--
I used to be a nihilist but I don't believe in that any more.
(Win98first ed. + all updates, PB3.51, external editor)