Debug vs MessageRequester

Just starting out? Need help? Post your questions and find answers here.
AussiePup
User
User
Posts: 19
Joined: Fri Jun 20, 2003 4:47 pm
Location: Chapel Hill, NC

Debug vs MessageRequester

Post by AussiePup »

I'm just now getting serious about learning my PureBasic that I purchased awhile back. I notice in so much of the example code and other code snippets, that debug seems to be the message printer of choice. Why is this? There has to be a reason other than typing a shorter name, but it is escaping me.

Thanks,

AussiePup
Regards,

Martin
Shannara
Addict
Addict
Posts: 1808
Joined: Thu Oct 30, 2003 11:19 pm
Location: Emerald Cove, Unformed

Post by Shannara »

Message requester will hault the program until you press ok. If you want to keep track on how a variable is incrementing during the run of an application, you can use the debugger to print out the values without halting the application.

that's only one application :)
Phoenix
Enthusiast
Enthusiast
Posts: 141
Joined: Sun Sep 04, 2005 2:25 am

Re: Debug vs MessageRequester

Post by Phoenix »

Debug is like Debug.Print in Visual Basic.... it lets you print things during runtime without your program stopping or opening a console.... also any Debug commands are not included in your executable when compiled but a MessageRequester is.
thefool
Always Here
Always Here
Posts: 5875
Joined: Sat Aug 30, 2003 5:58 pm
Location: Denmark

Post by thefool »

And debug commands are much easier to use.
Because you can use whatever type of variable without having to do str(), strq() and so on. And you don't need to specify a title and so on.

For speed measurements you will have to turn debugger off, and then you can't use the debug command.
AussiePup
User
User
Posts: 19
Joined: Fri Jun 20, 2003 4:47 pm
Location: Chapel Hill, NC

Post by AussiePup »

Thanks all,

It's starting to sink in!

AussiePup
Post Reply