Ary Manzana Wrote: > You are right. > > I see that you throw ConvException, because when some to!... fails it > throws that. But you don't catch it. So you'd get something like "Can't > convert 'hello' to an int", but you loose the information of which row > and column caused the problem. So maybe catching it and throwing a more > detailed exception...
I'll look into that. > Also, sometimes people fill out numbers with some comments, like "1 > apple", so maybe a less strict parsing for numbers might be good (as an > option). Loose rules are hard to setup to make everyone happy. I think this use case should be left to the user. I just want to get the information out quickly. Adding a row count shouldn't be too bad.
