Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | XSimpleFileAccess::openFileWrite() not truncating | ||
---|---|---|---|
Product: | ucb | Reporter: | em2 <em-ooo> |
Component: | code | Assignee: | AOO issues mailing list <issues> |
Status: | ACCEPTED --- | QA Contact: | |
Severity: | Trivial | ||
Priority: | P3 | CC: | issues |
Version: | OOo 1.1 | ||
Target Milestone: | AOO PleaseHelp | ||
Hardware: | PC | ||
OS: | Linux, all | ||
Issue Type: | DEFECT | Latest Confirmation in: | --- |
Developer Difficulty: | --- |
Description
em2
2003-11-22 22:28:24 UTC
Yes, I agree that this is at least a documentation issue (if not even a request for an improved implementation). Hi Andreas, can you please have a look into this (and at least improve the documentation, if not the implementation)? Thanks, Matthias AB: Accepted as documentation issue. I think the implementation must not be changed, because code may already rely on the current behaviour. Besides, the statement "There's no API which atomically opens truncates a file" is not true. Everyone is free to use UCB API directly. The SimpleFileAccess service is - as its name says - only a simple wrapper for convenience. So, everyone who wants to create/truncate a file has to reinvent the wheel? If that's the policy, why have XSimpleFileAccess in the first place? Using the UCB for such a simple operation as creating/truncating a file is overkill -- it's much simpler to wrap a C FILE in an XOutputStream. Why not add createTruncateFile() to, say, XSimpleFileAccess4? According to the roadmap of OpenOffice.org 2.0 (http://tools.openoffice.org/releases/q-concept.html) this issue has been scheduled for 3.0. s. above cp: retargeted to Office-Later due to limited ressources Reset assigne to the default "issues@openoffice.apache.org". |