Debugging Methods

THis forum deals with questions related to the use of PSPad for editing and debugging MemBrain scripts.
Posts: 55
Joined: Wed 21. Jul 2010, 17:43

Debugging Methods

Postby MrCreosote » Mon 25. Oct 2010, 17:25

When the Compiler finds an error, it states the Line # and Col # where the error occurred.

The problem is that the Line # refers to the line in some kind of compiled form - perhaps where all the #includes are replaced with the code they represent.

In general it makes it difficult to know just where the line is.

Are there any tricks to use to find the line with the error?

Is there any possibility of modifying the compiler to provide more useful information? Even including a copy of the bad line would be a big help even if its source file was not indicated.


User avatar
Site Admin
Posts: 438
Joined: Sun 16. Nov 2008, 18:21

Re: Debugging Methods

Postby Admin » Mon 25. Oct 2010, 18:29

On the MemBrain homepage download section, as part of the scripting examples there is a zip file that I've again attached to this post.
It describes how to set up the free editor 'PSPad' for editing and debugging MemBrain scripts.

With this setup you can launch script execution/compiling directly from PSPad, where you also have syntax highlighting. If a compiler error occurs your cursor will be automatically directed to the location of interest since PSPad will parse the compiler output of MemBrain.

Give it a try! If you haven't used it up to now it will massively improve your MemBrain scripting experience, I promise!

Description on how to set up PSPad for script editing/debugging.
(399.37 KiB) Downloaded 248 times
Thomas Jetter

Return to “PSPad”