[Libreoffice-commits] core.git: udkapi/com
Stephan Bergmann
sbergman at redhat.com
Thu Jun 19 02:17:43 PDT 2014
udkapi/com/sun/star/io/FilePermission.idl | 69 ++++++++++++++----------------
1 file changed, 34 insertions(+), 35 deletions(-)
New commits:
commit 9947032c4c6a772df888323338df699f54087013
Author: Stephan Bergmann <sbergman at redhat.com>
Date: Thu Jun 19 11:15:32 2014 +0200
Work around problem with nested /* in Doxygen comment
...where Doxygen apparently deliberately tracks nested /* ... */ comments in
/** ... */ comments (even though languages like C, C++, Java don't). Thanks to
Lionel for finding it.
Change-Id: I0cfc54216df4e49c194c097e5ad3b00f5270d395
diff --git a/udkapi/com/sun/star/io/FilePermission.idl b/udkapi/com/sun/star/io/FilePermission.idl
index d23d90a..b3d1981 100644
--- a/udkapi/com/sun/star/io/FilePermission.idl
+++ b/udkapi/com/sun/star/io/FilePermission.idl
@@ -22,41 +22,40 @@
module com { module sun { module star { module io {
-/** This permission represents access to a file or directory.
- A FilePermission consists of a file url and a set of actions valid for that url.
- <p>
- The path of the file url that ends in <code>"/*"</code> indicates all the files and
- directories contained in that directory. A path that ends with <code>"/-"</code>
- indicates (recursively) all files and subdirectories contained in that
- directory. A file url string consisting of the special token
- <code>"<<ALL FILES>>"</code> matches any file.
- <br>
- Note: A file url string consisting of a single <code>"*"</code> indicates all the files
- in the current directory, while a string consisting of a single <code>"-"</code> indicates
- all the files in the current directory and (recursively) all files and
- subdirectories contained in the current directory.
- <br>
- The actions to be granted is a list of one or more comma-separated keywords.
- The possible keywords are <code>"read"</code>, <code>"write"</code>,
- <code>"execute"</code>, and <code>"delete"</code>.
- Their meaning is defined as follows:
- <ul>
- <li><code>read</code> -- read permission</li>
- <li><code>write</code> -- write permission</li>
- <li><code>execute</code> -- execute permission</li>
- <li><code>delete</code> -- delete permission</li>
- </ul><br>
- The actions string is processed case-insensitive.
- </p>
-
- @attention
- Be careful when granting FilePermissions. Think about the implications of
- granting read and especially write access to various files and directories.
- The <code>"<<ALL FILES>>"</code> permission with write action is
- especially dangerous. This grants permission to write to the entire file system.
-
- @since OOo 1.1.2
-*/
+/// This permission represents access to a file or directory.
+/// A FilePermission consists of a file url and a set of actions valid for that url.
+/// <p>
+/// The path of the file url that ends in <code>"/*"</code> indicates all the files and
+/// directories contained in that directory. A path that ends with <code>"/-"</code>
+/// indicates (recursively) all files and subdirectories contained in that
+/// directory. A file url string consisting of the special token
+/// <code>"<<ALL FILES>>"</code> matches any file.
+/// <br>
+/// Note: A file url string consisting of a single <code>"*"</code> indicates all the files
+/// in the current directory, while a string consisting of a single <code>"-"</code> indicates
+/// all the files in the current directory and (recursively) all files and
+/// subdirectories contained in the current directory.
+/// <br>
+/// The actions to be granted is a list of one or more comma-separated keywords.
+/// The possible keywords are <code>"read"</code>, <code>"write"</code>,
+/// <code>"execute"</code>, and <code>"delete"</code>.
+/// Their meaning is defined as follows:
+/// <ul>
+/// <li><code>read</code> -- read permission</li>
+/// <li><code>write</code> -- write permission</li>
+/// <li><code>execute</code> -- execute permission</li>
+/// <li><code>delete</code> -- delete permission</li>
+/// </ul><br>
+/// The actions string is processed case-insensitive.
+/// </p>
+///
+/// @attention
+/// Be careful when granting FilePermissions. Think about the implications of
+/// granting read and especially write access to various files and directories.
+/// The <code>"<<ALL FILES>>"</code> permission with write action is
+/// especially dangerous. This grants permission to write to the entire file system.
+///
+/// @since OOo 1.1.2
published struct FilePermission
{
/** target file url
More information about the Libreoffice-commits
mailing list