- Joined
- Aug 14, 2005
- Messages
- 49
Hi everyone
I was wondering: How can I effectively debug Wurst code? Obviously, it's always possible to use print(...) statements to put some variable values on the screen, and even though it works, it's cumbersome and inefficient. Moreover, there are some bugs which I can't fix like this.
Right now, I am fighting with trying to make a closure work (with a functional interface, see this last post of minehttps://www.hiveworkshop.com/threads/how-can-i-accomplish-hashmap-item-function.305409/ )
But, unfortunately, I am getting a NULL pointer exception and even after staring at the code and tinkering around for an hour, I don't know what I'm doing wrong.
At the same time, I don't want to annoy the maintainers of Wurst or the members of this forum every time I run into a small problem. Hence my desire to debug this myself. I've searched Google, the forums and the manual, but I can't find any mention on how I could attack a problem like this. (Full disclaimer: I'm not a VSCode guru, so if there already is an option there that I overlooked in my search, I apologize).
I was wondering: How can I effectively debug Wurst code? Obviously, it's always possible to use print(...) statements to put some variable values on the screen, and even though it works, it's cumbersome and inefficient. Moreover, there are some bugs which I can't fix like this.
Right now, I am fighting with trying to make a closure work (with a functional interface, see this last post of minehttps://www.hiveworkshop.com/threads/how-can-i-accomplish-hashmap-item-function.305409/ )
But, unfortunately, I am getting a NULL pointer exception and even after staring at the code and tinkering around for an hour, I don't know what I'm doing wrong.
At the same time, I don't want to annoy the maintainers of Wurst or the members of this forum every time I run into a small problem. Hence my desire to debug this myself. I've searched Google, the forums and the manual, but I can't find any mention on how I could attack a problem like this. (Full disclaimer: I'm not a VSCode guru, so if there already is an option there that I overlooked in my search, I apologize).