| Details | Language | Abstract |
| BugsTrace.call |
Visual Basic
| This snippet inserts the BugsTrace.call statement. Locate it wherever you want to trace program flow or critical variable values, in place of comments. See BugsTrace.doc.snippet for instructions. |
| BugsTrace.function |
Visual Basic
| This is part of a 3 snippet set:
bugstrace.doc.snippet, bugstrace.call.snippet, and bugstrace.function.snippet |
| BugsTrace.function |
Visual Basic
| This is part of a 3 snippet set:
bugstrace.doc.snippet, bugstrace.call.snippet, and bugstrace.function.snippet |
| BugsTrace.doc |
Visual Basic
| BugsTrace provides a very lightweight, easily deployed developer message trace capability
that is not dependent on the application, language, framework, or runtime tools for use.
Instant BugsTraces can contribute greatly to rapid development, testing, and debugging.
The BugsTrace output only has trace statements and information the developer wanted to include, making it much more easily readable for rapid testing and debugging. I wrote the BASIC version in the 1980's and have reused it in many different languages and environments including VB, C, C#, PHP, Ruby and COBOL. All work the same using a simple text file as the trace toggle and trace content. System security controls read and write access. The code can be customized but that is not required. It can stay in the application throughout it's life cycle and deployment contexts with very negligible performance impact. For VB 2005, there are 3 snippet files: bugstrace.call, bugstrace.method, and bugstrace.doc. Enjoy! |