Save Lives: Debug Code

James Z jazu at comcast.net
Fri Apr 14 09:32:36 EDT 2006


1. detailed notes on what each code segment does.

2. sample input and resulting output in the notes to verify it works.

3. a consistant coding style.


James Z.


On 4/14/06 4:46 AM, "Marielle Lange" <mlange at lexicall.org> wrote:

> On the topics of bugs, what I would like to get discussed here is
> about the strategy persons on this list have to prevent bugs getting
> into their codes in the first place and how to spot and process them
> when they did.
> 
> Sure, some books can be found for advice on this. But what are the
> things to be more specifically careful about when programming with
> runrev? Let's avoid the discussion on whether bug free shipping
> exists or not. Let's focus on a discussion on what to be careful
> about when developing with revolution and what precautions to take to
> ensure solid/reliable code.
> 
> A little grasshoper,
> Marielle
> 
> On Thu, 13 Apr 2006, Dan Shafer wrote:
>> Offered without comment as further conversation fodder for the ongoing
>> discussion about bugs and their fixing:
>> 
>> http://www.informationweek.com/blog/main/archives/2006/04/
>> save_lives_debu.html
>> 
> 
> 
> ------------------------------------------------------------------------
> --------
> Marielle Lange (PhD),  Psycholinguist
> 
> Alternative emails: mlange at blueyonder.co.uk,
> 
> Homepage         
> http://homepages.widged.com/mlange/
> Easy access to lexical databases                    http://
> lexicall.widged.com/
> Supporting Education Technologists              http://
> revolution.widged.com/wiki/
> 
> 
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution





More information about the use-livecode mailing list