search for: aa365247

...?prn?, ?aux?, ?clock$?, ?nul?, ?com1? to ?com9?, and > ?lpt1? to ?lpt9' (possibly followed by extensions) are also bad. You can > Google "PRN filename in Windows" to find lots of people confused by this. > One page I get is > > https://msdn.microsoft.com/en-us/library/aa365247(VS.85).aspx > > but there's no guarantee that will work five minutes from now. > > Duncan Murdoch > > > >> In a fresh R session 3.4.4 installed on Windows 10: >> >> grep("prn.us.txt", dir(recursive = TRUE)) >>> >> integer(0) >&g...

Dear all, while preparing some exercises I came across some highly surprising behaviour of file.exists(). The specific value "prn.us.txt" always returns TRUE, even though that file is nowhere to be found on my system. In a fresh R session 3.4.4 installed on Windows 10: > grep("prn.us.txt", dir(recursive = TRUE)) integer(0) > file.exists("prn.us.txt") [1] TRUE

...tempt to create the directory (unless it is of the form x: - i.e. a drive name) = Ignore any ?already exists? errors, otherwise throw an error This logic appears flawed in that it skips \\share which isn?t a valid path format (according to https://msdn.microsoft.com/en-us/library/windows/desktop/aa365247(v=vs.85).aspx ). Dredging my memory, it?s possible that \\share was a supported format in very old versions of Windows, but it?s been a long time since the UNC format came in. It?s also possible that \\share is a valid format in some odd environments, but the UNC format is far more widely used. Th...

...m x: - i.e. a >> drive name) >> = Ignore any ?already exists? errors, otherwise throw an error >> >> This logic appears flawed in that it skips \\share which isn?t a valid >> path format (according to https://msdn.microsoft.com/en- >> us/library/windows/desktop/aa365247(v=vs.85).aspx ). Dredging my memory, >> it?s possible that \\share was a supported format in very old versions of >> Windows, but it?s been a long time since the UNC format came in. It?s also >> possible that \\share is a valid format in some odd environments, but the >> UNC...

...ng with "?con?, ?prn?, ?aux?, ?clock$?, ?nul?, ?com1? to ?com9?, and ?lpt1? to ?lpt9' (possibly followed by extensions) are also bad. You can Google "PRN filename in Windows" to find lots of people confused by this. One page I get is https://msdn.microsoft.com/en-us/library/aa365247(VS.85).aspx but there's no guarantee that will work five minutes from now. Duncan Murdoch > > In a fresh R session 3.4.4 installed on Windows 10: > >> grep("prn.us.txt", dir(recursive = TRUE)) > integer(0) >> file.exists("prn.us.txt") > [1] TR...

...gt; drive name) >>> = Ignore any ?already exists? errors, otherwise throw an error >>> >>> This logic appears flawed in that it skips \\share which isn?t a valid >>> path format (according to https://msdn.microsoft.com/en- >>> us/library/windows/desktop/aa365247(v=vs.85).aspx ). Dredging my memory, >>> it?s possible that \\share was a supported format in very old versions of >>> Windows, but it?s been a long time since the UNC format came in. It?s also >>> possible that \\share is a valid format in some odd environments, but the...

...(unless it is of the form x: - i.e. a > drive name) > = Ignore any ?already exists? errors, otherwise throw an error > > This logic appears flawed in that it skips \\share which isn?t a valid > path format (according to https://msdn.microsoft.com/en- > us/library/windows/desktop/aa365247(v=vs.85).aspx ). Dredging my memory, > it?s possible that \\share was a supported format in very old versions of > Windows, but it?s been a long time since the UNC format came in. It?s also > possible that \\share is a valid format in some odd environments, but the > UNC format is far m...

...Ignore any ?already exists? errors, otherwise throw an error >>>>> >>>>> This logic appears flawed in that it skips \\share which isn?t a valid >>>>> path format (according to https://msdn.microsoft.com/en- >>>>> us/library/windows/desktop/aa365247(v=vs.85).aspx ). Dredging my >> memory, >>>>> it?s possible that \\share was a supported format in very old versions >> of >>>>> Windows, but it?s been a long time since the UNC format came in. It?s >> also >>>>> possible that \\share i...

lvqcl wrote: > Oops. It seems that vsnprintf_s isn't always available on MinGW platform: > MinGW declares this function only if MINGW_HAS_SECURE_API macro is defined. > That's because WinXP version of msvcrt.dll doesn't contain secure functions > like vsnprintf_s. > > Maybe it's better to revert vsnprintf_s to vsprintf or to use vnsprintf? Ok, we need to drop

...gt; drive name) >> = Ignore any ?already exists? errors, otherwise throw an error >> >> This logic appears flawed in that it skips \\share which isn?t a valid >> path format (according to https://msdn.microsoft.com/en- >> us/library/windows/desktop/aa365247(v=vs.85).aspx ). Dredging my memory, >> it?s possible that \\share was a supported format in very old versions of >> Windows, but it?s been a long time since the UNC format came in. It?s also >> possible that \\share is a valid format in some odd environments, but the...

...;>> = Ignore any ?already exists? errors, otherwise throw an error > >>> > >>> This logic appears flawed in that it skips \\share which isn?t a valid > >>> path format (according to https://msdn.microsoft.com/en- > >>> us/library/windows/desktop/aa365247(v=vs.85).aspx ). Dredging my > memory, > >>> it?s possible that \\share was a supported format in very old versions > of > >>> Windows, but it?s been a long time since the UNC format came in. It?s > also > >>> possible that \\share is a valid format in s...