Getting Username (Windows And Linux)

Quote:

Original post by Unreal how i will get the username for both windows and linux?

#include <stdio.h>#include <stdlib.h>#include <unistd.h>#include <pwd.h>#include <string.h>#include <errno.h>int main() {  struct passwd *pwd;  pwd = getpwuid(getuid());  if (NULL != pwd) {	printf("Username: %s\n", pwd->pw_name);	printf("Home directory: %s\n", pwd->pw_dir);  }  else {	fprintf(stderr, "Error: %s\n", strerror(errno));	return EXIT_FAILURE;  }  return EXIT_SUCCESS;}

Quote:

Original post by Kazade I'm pretty sure that saving to: ~/my engine/ would work in linux. ~/ is a shortcut to the home directory.

Quote:

Original post by haegarr A simpe version under linux is to investigate the environment variables, as are available from the main() invocation. Herein the variable USER denotes the user's name. Even better is to use HOME that already denotes the user's home directory (and hence would be more suitable instead of assuming it being located in /home/).

$ cat foo.c#include <stdio.h>#include <stdlib.h>int main() {  char *home = getenv("HOME");  if (home) {        printf("%s\n", home);  }  return 0;}$ ./foo/home/somebody$ HOME=/root ./foo/root

Original post by let_bound

Quote:

Original post by Unreal Quote: Original post by Kazade I'm pretty sure that saving to: ~/my engine/ would work in linux. ~/ is a shortcut to the home directory. It's the shell that expands ~ into the home directory. The C library doesn't.

Oops. My mistake.

Quote:

Original post by Unreal Quote: Original post by haegarr A simpe version under linux is to investigate the environment variables, as are available from the main() invocation. Herein the variable USER denotes the user's name. Even better is to use HOME that already denotes the user's home directory (and hence would be more suitable instead of assuming it being located in /home/). That's dangerous. Consider: code removed This isn't dangerous per se (lambda users can't write to /root), but it illustrates that you can't trust environment variables to get meaningful data.

Quote:

Original post by Unreal Its true that environment variables can simply be faked, e.g. I can tell the computer to display me chinese messages by setting $LANG to the appropriate value. Well, then I have to live with the result ;) But it isn't dangerous to let the user write to any directory the user has write permissions for. Of course, it is best practise to check whether opening/writing files is possible instead of breaking the program. The only "security" issue would be that the user may overwrite the same files of another user, but that can (and should) simply be avoided by file permissions. Last but not least I second the hint of the AP above.

$ export HOME="/some/dir"(do lots of work in /some/dir and its subdirectories)$ cd           # back in /some/dir$ commit       # commit to some RCS$ run_the_game # it uses $HOME to find the home directory,                 and saves its data to /some/dir