To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=106591
------- Additional comments from c...@openoffice.org Tue Jun 29 14:16:06 +0000 2010 ------- Sure, I've sympathy with that position. Its definitely a bug in someone elses code, and if we didn't do anything about it at all that would be a reasonable position, but the vaguely related workaround char nCh; if ( 1 != read( SourceFileFD, &nCh, 1 ) || -1 == lseek( SourceFileFD, 0, SEEK_SET ) ) undermines that logic a little :-) --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@framework.openoffice.org For additional commands, e-mail: issues-h...@framework.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
