Hiding Code? Is it possible?

Hello, I want to implement my own type of debug option where a window opens and will just spit out variouse things that the program is doing as it does them. But the things i want to record are all over the place and I don't really want to have random debug lines all throughout my code. Does eclipse have a way to assign code to a group and then hide that group, or maybe assign certain code to be a seperate color? Anything to distinguish from my real code and just random stuff I rather not have visible.

Thank you

Eclipse doesn't have anything like that to my knowledge but there are a couple of things you could try:

Wrap debug code with if(debug) { ... }, with debug being taken from the command line parameters.

Use java.util.logging to set up multiple levels of debug verbosity.

Use the Debug view in eclipse to inspect runtime variables, etc, while the program is running.

Search on the forum as well. I'm not remember the exact title, but there is a thread discussion about debugging and I guess it's helpful to you.

Here is the link.

http://www.java-forums.org/new-java/...a-program.html

I have an idea, it's not automatic though.

Use the same coding style through out your source. find and replace with // at the beginning. e.g.

find: System.out.println("debug:
replace with: //System.out.println("debug

to undo:
find: //System.out.println("debug:
replace with: System.out.println("debug

Intresting Idea, but then the code is still there, plus I have I think about 20 classes. Heh I suppose if I really wanted to I could write somthing up that would find and remove the lines from my code and then insert them whenever, still impractical though. Would be a nice feature in eclipse, for me at least :P
Hey I'm not very experienced yet, especially with plugins, but is this somthing you could write a plugin to do? If so, I'd probly spent some spare time researching that.

I wouldn't bother. It's good practice not to change any code in order to debug, but to change parameters or use a proper debugger.

Quote:

---

Originally Posted by OrangeDog

I wouldn't bother. It's good practice not to change any code in order to debug, but to change parameters or use a proper debugger.

---

I agreed with you OD, changing code time to time can cause lots of issues. Best things for me is use of a better debugger. Those we have lots of advance debugging tools. So why don't we use of them have a better solution in quick time.