From 9947032c4c6a772df888323338df699f54087013 Mon Sep 17 00:00:00 2001 From: Stephan Bergmann Date: Thu, 19 Jun 2014 11:15:32 +0200 Subject: 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 --- udkapi/com/sun/star/io/FilePermission.idl | 69 +++++++++++++++---------------- 1 file changed, 34 insertions(+), 35 deletions(-) (limited to 'udkapi/com/sun') diff --git a/udkapi/com/sun/star/io/FilePermission.idl b/udkapi/com/sun/star/io/FilePermission.idl index d23d90a38bee..b3d19817087b 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. -

- The path of the file url that ends in "/*" indicates all the files and - directories contained in that directory. A path that ends with "/-" - indicates (recursively) all files and subdirectories contained in that - directory. A file url string consisting of the special token - "<>" matches any file. -
- Note: A file url string consisting of a single "*" indicates all the files - in the current directory, while a string consisting of a single "-" indicates - all the files in the current directory and (recursively) all files and - subdirectories contained in the current directory. -
- The actions to be granted is a list of one or more comma-separated keywords. - The possible keywords are "read", "write", - "execute", and "delete". - Their meaning is defined as follows: -


- The actions string is processed case-insensitive. -

- - @attention - Be careful when granting FilePermissions. Think about the implications of - granting read and especially write access to various files and directories. - The "<>" 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. +///

+/// The path of the file url that ends in "/*" indicates all the files and +/// directories contained in that directory. A path that ends with "/-" +/// indicates (recursively) all files and subdirectories contained in that +/// directory. A file url string consisting of the special token +/// "<>" matches any file. +///
+/// Note: A file url string consisting of a single "*" indicates all the files +/// in the current directory, while a string consisting of a single "-" indicates +/// all the files in the current directory and (recursively) all files and +/// subdirectories contained in the current directory. +///
+/// The actions to be granted is a list of one or more comma-separated keywords. +/// The possible keywords are "read", "write", +/// "execute", and "delete". +/// Their meaning is defined as follows: +///


+/// The actions string is processed case-insensitive. +///

+/// +/// @attention +/// Be careful when granting FilePermissions. Think about the implications of +/// granting read and especially write access to various files and directories. +/// The "<>" 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 -- cgit