Changeset 97409 in vbox
- Timestamp:
- Nov 5, 2022 11:19:12 PM (2 years ago)
- svn:sync-xref-src-repo-rev:
- 154414
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/src/VBox/Main/src-client/GuestCtrlPrivate.cpp
r97399 r97409 1723 1723 */ 1724 1724 /* static */ 1725 int GuestPath::BuildDestinationPath(const Utf8Str &strSrcPath, PathStyle_T enmSrcPathStyle, Utf8Str &strDstPath, PathStyle_T enmDstPathStyle) 1726 { 1727 /** 1725 int GuestPath::BuildDestinationPath(const Utf8Str &strSrcPath, PathStyle_T enmSrcPathStyle, 1726 Utf8Str &strDstPath, PathStyle_T enmDstPathStyle) 1727 { 1728 /* 1728 1729 * Rules: 1729 1730 * … … 1735 1736 */ 1736 1737 const char *pszSrcName = RTPathFilenameEx(strSrcPath.c_str(), 1737 1738 enmSrcPathStyle == PathStyle_DOS 1738 1739 ? RTPATH_STR_F_STYLE_DOS : RTPATH_STR_F_STYLE_UNIX); 1739 1740 … … 1811 1812 * however, on DOS "\" is a path separator. 1812 1813 * 1813 * See @bugref{21095}. 1814 * See @ticketref{21095}. 1815 */ 1816 /** @todo r=bird: Seeing that callers like GuestSessionTaskCopyFrom::Run() has 1817 * passed strPath to RTPathQueryInfoEx() prior to calling this function, I don't 1818 * get the comments a bout escape sequence stuff here. 1819 * 1820 * "\" ("\\" in C/C++) is not an escape sequence on unix unless you're in a 1821 * typical unix shell like bash. It's just a filename character that doesn't 1822 * get interpreted as anything special by the kernel (unlike '/' and '\0' (C/C++ 1823 * encoding)). 1824 * 1825 * "\ " (or "\\ " in C/C++) does not mark a single space in a path component, it 1826 * signifies two characters, a backslash and a space, neither with any special 1827 * meaning to a UNIX host. 1814 1828 */ 1815 1829 else if (psz[off] == '\\')
Note:
See TracChangeset
for help on using the changeset viewer.