https://bz.apache.org/bugzilla/show_bug.cgi?id=60902
--- Comment #4 from Javen O'Neal <[email protected]> --- > The only reason I can think of (why the optimizer method is preferable) is > for performance. Performance is a big reason. It's always tricky as a library developer to make choices that impact our users. For example, should I be choosing whether we should cache values at the expense of memory in order to make code run faster for certain cases (and perhaps slower for others)? In general I prefer to give the choice to the user, but try to do so without presenting an overwhelming API. HSSFOptimizer is probably a O(n²) operation, which could be done at the user's convenience, rather than executing O(n) comparisons every time a style is changed. CellUtil.setCellStyleProperties attempts to find a matching style before creating a new style. Maybe you could implement something along those lines, so a user can choose to eat the cost when modifying a cell style or when saving. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
