Andy, > if you "Have time" to fix bugs in the divergent > LittleEndian than you have time to combine the > functionality into the org.apache.poi.util package\
In all fairness, my patch on hpsf.littleendian.DWord.java are doc patches. If you don't want to deprecate the class and it does not behave correctly, I think the *least* we could do is put a Javadoc comment in to let the developer know a DWord is a 32 bit unsigned even though it returns a 32 bit signed int. My priority is to round out HPSF in terms of functionality before I get rid of references to /hpsf/littleendian/. The end user won't know if SummaryInformation.java calls DWord from /hpsf or /poifs. If you're not going to deprecate it, then there is not an issue, right? I am not adding functionality to DWord, only calling it. I'll work on referencing the poifs little endian stuff after I complete HPSF's functionality. Those are just my priorities of work. Also, these bugs are not present in /poifs/util/LittleEndian.java. LittleEndian makes no claim to represent a DWord. Therefore, the user does not expect DWord behavior. I don't understand what you want here. - Drew Quoting "Andrew C. Oliver" <[EMAIL PROTECTED]>: > Okay dudes, I'm going to start being a real pain and -1ing commits if > you "Have time" to fix bugs in the divergent LittleEndian than you have > time to combine the functionality into the org.apache.poi.util package > instead of causing a "lets everyone build their own little endian util > classes" in POI. I don't want to see POI turn into a microcosim of the > Apache whole where everyone builds their own conneciton pool or > whatever. > > -Andy ___________________ Drew Varner [EMAIL PROTECTED]
