I need to create, remove and check if a directory exists. It seems that theres no standard/portable way to do this? Is this correct? Are there "recommended" functions, or should I just use system()? To check if a directory exists should I just change working path and use the return value? It's for a windows console app. Thanks
> It seems that theres no standard/portable way to do this? Is this correct?
Correct - there is no standard way
Here's a recent thread which may help
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
Thanks - bizarre
how are you supposed to write portable code
guess I'll start including windows.h
is it reasonable to check if the directory exists using:
#include windows.h
if (SetCurrentDirectory("z:\mydir\") == 0)
I can't check, because I'm at work and I'm not allowed to install a compiler grrrrrrrrrrrrr....
> how are you supposed to write portable code
Read this
> if (SetCurrentDirectory("z:\mydir\") == 0)
I think this has something to do with FTP
This is from MSDN
To test for a directoryDirectory Control
These routines access, modify, and obtain information about the directory structure.
Directory-Control Routines
Routine Use
_chdir, _wchdir Change current working directory
_chdrive Change current drive
_getcwd, _wgetcwd Get current working directory for default drive
_getdcwd, _wgetdcwd Get current working directory for specified drive
_getdrive Get current (default) drive
_mkdir, _wmkdir Make new directory
_rmdir, _wrmdir Remove directory
_searchenv, _wsearchenv Search for given file on specified paths
_stat, _wstat, _stati64, _wstati64
Get status information on a file.
int _stat( const char *path, struct _stat *buffer );
.....
buffer contains a member called st_mode
Bit mask for file-mode information. The _S_IFDIR bit is set if path specifies a directory; the _S_IFREG bit is set if path specifies an ordinary file or a device. User read/write bits are set according to the file’s permission mode; user execute bits are set according to the filename extension.
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
