From: Gregg T. <gm...@cs...> - 2014-03-17 23:53:01
|
On Mar 14, 2014, at 2:17 PM, Steve Wampler <swa...@no...> wrote: > > As implemented in numbers.icn, gcd(i,j) throws a runtime error if > either i or j is negative, or either either i or j = 0. However, > gcd is computable for all cases except where both i and j = 0…. That's a useful change, and it seems to be consistent with most definitions of GCD (that is, with anyone who even thinks to discuss the possibility of negative numbers). I've put it on the list for the next version. On Mar 14, 2014, at 2:24 PM, Cheyenne Wills <che...@gm...> wrote: > > Maybe one suggestion, have a global variable that if set will either have gcd behave the old or new way. That way the behavior can be controlled. Hidden state in the library is generally dangerous, not to mention the added complication, so I'm not going to do this. Gregg Townsend Icon Project University of Arizona |