Writing Debuggable Code
Description
For those of you who take on massive coding tasks such as creating an entire site from scratch, you'll notice that it tends to become tedious to debug your code unless you've taken a few precautionary measures. This tutorial will start you off in the right direction. It won't make your code debuggable for you, but you'll have an idea on how to do it. Most code can be modified to fit the schema suited for debugging fairly easily, but this guide is written with a clean slate in mind; it will describe the process of preparing your code to be easily debuggable from scratch.
Visits : 246
Google Page Rank : ![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
![]()
Requirements
| Date Included | 2006-03-21 15:15:58 |
| Date Modified | 2006-03-21 15:15:58 |
| URL | http://forums.dreamincode.net/showtopic9942.htm |
| Download URL | http://forums.dreamincode.net/showtopic9942.htm |
| Version | n/a |
| Platform | n/a |
| Filesize | KB |
| Price | |
| Author | fury |
If you have used Writing Debuggable Code or tried the demos, you can go ahead and rate it.
Comments for Writing Debuggable Code
Previous visitors and users reviewed Writing Debuggable Code and their observations and experience has been written below by them.
Commenting and Review Guidelines
Member Reviews are intended to provide valuable information regarding a listing to other people considering using the resource. As such, the following guidelines have been established and are utilized when validating reviews.
No review shall be validated if:
the contents are more than 600 characters;
any field contains any profane or obscene language.
it suggests or contains information about an alternate script (no suggestions are allowed);
it contains advertising of an alternate program or website;
it contains HTML or other programming language code in it;
it is vague or generic in nature (i.e. "This script is awesome!" does not contain valuable information regarding the program and thus will not be validated);
it contains a URL to any website;
is written in any language except for English;
it appears the user has been forced to write a review (i.e. requiring a review to demo a program);
it is written by the author or an employee of the company who submitted the link to websiteingredients.com; or
it appears to be asking for technical support.
It is websiteingredients.com's policy not to intervene in a dispute between a reviewer and a link owner. Once a review is validated, it will not be removed unless it is later determined that it violates any of these Review Guidelines.
As Member Reviews are an important tool for WebsiteIngredients.com visitors and in order to provide Link Owners the ability to respond to criticism, WebsiteIngredients.com allows Link Owners to respond to reviews submitted on their listing. This tool is provided so that WebsiteIngredients.com Link Owners may provide their side to a negative review, without the need for WebsiteIngredients.com to intervene. As with any review, all responses by Link Owners must be validated by WebsiteIngredients.com, and the Review Guidelines apply to these responses as well.
Report Writing Debuggable Code
