Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
An IDE anomoly detected
#4
(04-29-2024, 04:53 PM)FellippeHeitor Wrote: Sub vwatch is always there. If you have $debug, the hidden sub will contain the debug features. If not, the hidden sub will be just a stub, so you can’t have a conflicting sub vwatch of your own.
Oh sure, I understand what VWATCH is and does in relation to the IDE and debugging, I'm just wondering if that line should read:

"Caused by (or after): FOR" 

instead of

"Caused by (or after): SUB VWATCH ( )"
New to QB64pe? Visit the QB64 tutorial to get started.
QB64 Tutorial
Reply


Messages In This Thread
An IDE anomoly detected - by TerryRitchie - 04-29-2024, 01:51 PM
RE: An IDE anomoly detected - by bplus - 04-29-2024, 04:22 PM
RE: An IDE anomoly detected - by FellippeHeitor - 04-29-2024, 04:53 PM
RE: An IDE anomoly detected - by TerryRitchie - 04-29-2024, 06:21 PM
RE: An IDE anomoly detected - by SMcNeill - 04-29-2024, 06:51 PM



Users browsing this thread: 2 Guest(s)