DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9403>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9403 HSSFRow.cellIterator() returns row results in reverse order [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Version|1.5.1 |2.0-dev ------- Additional Comments From [EMAIL PROTECTED] 2002-12-19 16:21 ------- Sure. You can leave it open and please feel free to vote (if enough people feel that way and I think they are making an INFORMED vote I/other commiters may change my/our mind). I'm retargeting to 2.0 because there is like NO way we're backporting such changes into 1.5.1 (behavioral/feature-oriented,etc). However, the fact we're using a HashMap will change in 3.0 and instead we'll probably return them in the order you suggest just due to HOW we'll be storing it. I just don't want to guarantee order in this interface because it could change and the file format itself might effect it. Personally, I think you're suffering from file-format API versus VBA-style API confusion. The HSSF usermodel is to give you access to the file format without exposing you to certain nasty details (such as the fact that rows are completely unrelated to cells and all the little records and intricacies). VBA and Formula 1 make it look like you're using Excel (and one interfaces with Excel single-threadedly, and the other is a full implementation of Excel in Java more or less...to the tune of 10k). Its the difference between abstracting the file format to you and creating an implementation of Excel. We make this decision for performance reasons and simplicity. (Formula 1 and VBA APIs are simpler to conceieve but harder to master because there are just so freaking many of them...10 different ways to do EVERYTHING... HSSF seeks a greater conceptual simplicity. Also "convienience functions" are by [apparent] community consensus until a later release -- we're all infected with eXtremeProgramming style thought.) Besides. Just because you need the cells or rows in order, doesn't mean everyone does. Depending on what you're doing, the reactor pattern (in your own code) might help you here regardless of whether you're using the eventmodel: http://www.freeroller.net/page/acoliver/20021215#the_reactor_pattern_in_reading -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
