[pylucene-dev] Bug/JCC: NumberTools.longToString

[Pete]

On Thursday November 15 2007 10:05:57 pm Andi Vajda wrote:
> Agreed. If you send me a patch to the README, I'll apply it.

Woohoo! a patch I can finally write.  Attached. ;)

> Yes, that's part of the complications. parseArgs() would have to be told
> about the existence of overloads, some of which could be inherited, of
> course...

Sounds stressful.

> > Again, I'll deal if necessary, but I suspect this going to bite others as
> > well.  Debugging would be easier if lucene.InvalidArgsError contained
> > more info about which arg was invalid...
>
> Good point, some of that information is readily available. I should forward
> it to the error.

I'm not sure what's available, but the more info the better... Something along 
the lines of "Got int expected long for arg x" would be great... I realize 
there are a lot of ways to pass invalid args and it's probably easier to 
detect the problem than write human-readable error messages (silly humans).

Thanks.

-- 
Peter Fein   ||   773-575-0694   ||   pfein at pobox.com
http://www.pobox.com/~pfein/   ||   PGP: 0xCCF6AE6B
irc: pfein at freenode.net   ||   jabber: peter.fein at gmail.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PyLucene-README-int.diff
Type: text/x-diff
Size: 763 bytes
Desc: not available
Url : http://lists.osafoundation.org/pipermail/pylucene-dev/attachments/20071116/e28edf12/PyLucene-README-int.bin