The Artima Developer Community
Sponsored Link

Agile Buzz Forum
The Best Error Checking is Usage

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
James Robertson

Posts: 29924
Nickname: jarober61
Registered: Jun, 2003

David Buck, Smalltalker at large
The Best Error Checking is Usage Posted: Apr 10, 2007 9:12 AM
Reply to this message Reply

This post originated from an RSS feed registered with Agile Buzz by James Robertson.
Original Post: The Best Error Checking is Usage
Feed Title: Cincom Smalltalk Blog - Smalltalk with Rants
Feed URL: http://www.cincomsmalltalk.com/rssBlog/rssBlogView.xml
Feed Description: James Robertson comments on Cincom Smalltalk, the Smalltalk development community, and IT trends and issues in general.
Latest Agile Buzz Posts
Latest Agile Buzz Posts by James Robertson
Latest Posts From Cincom Smalltalk Blog - Smalltalk with Rants

Advertisement

Actual usage of software is the best way to find bugs - especially ones you hadn't thought to look for. BottomFeeder has a syndication library that it uses for creating feed and item objects, and that library is now being used by Smalltalk-Central. Recently, I extended the way feed filters work - they had been used solely to filter items out (i.e., a match against a filter kicked the item). Mark Roberts wanted a positive filter, so I extended the library a bit while I was in Cincinnati.

However, the filtering had a flaw - the filters run sequentially, and while filter1 might keep an item, filter2 might knock it out. That's not really the behavior Mark was looking for, and since he was the person requesting the feature, it really should have worked the way he wanted it to. So this morning, while he explained the problem on the IRC channel, I fixed the code - it was a simple matter of having items remember whether they had been positively filtered during the filter loop. That's all done, Mark's happy with the code, and it's published.

Turns out that talking to the customer for a feature is usually the best way to understand the request.

Technorati Tags:

Read: The Best Error Checking is Usage

Topic: Marketing can't be left to Legal Previous Topic   Next Topic Topic: Where's Spring?

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use