linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steve Graegert <graegerts@gmail.com>
To: linux-c-programming@vger.kernel.org
Subject: Re: should I use, getcwd() or *environ ?
Date: Sat, 5 Mar 2005 12:12:51 +0100	[thread overview]
Message-ID: <6a00c8d505030503121038ff83@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0503042218420.2519-100000@hestia>

On Fri, 4 Mar 2005 22:23:17 +0100 (CET), J. <mailing-lists@xs4all.nl> wrote:
> Friday, March 04 22:18:42
> 
> Hello,
> 
> I have to remember the working directory and save it in my program so that
> I can return to it later..
> 
> Which one is better/safer and why ? The environment var's or the
> getcwd() function fam... ?
> 

I usually take the following approach:

	int  fd_dir;
	char buf[PATH_MAX];
	
	if (getcwd(buf, sizeof(buf)) == NULL) {
		/* error handling */
	}
	
	/* open a directory for reading */
	if ((fd = open(buf, O_RDONLY)) < 0) {
		/* error handling*/
	}
	
	/* do all your work here and return to old dir */
	
	if (fchdir(fd_dir) < 0) {
		/* error handling */
	}

This makes sure, that you can process directories as you will and
return to the one you started by simply calling fchdir(). You see,
getcwd() is usefull and so is fchdir(). It's an easy and reliable way
to bookmark a direcory. Nevertheless, you will need a fallback if the
directory you bookmarked is changed meanwhile by another process. I
would not rely on environment variables, since this approach is
elegant while portable.

Hope this helps.


> --
> http://www.rdrs.net/
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


-- 
Kind Regards

    \Steve

  parent reply	other threads:[~2005-03-05 11:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-04 21:23 should I use, getcwd() or *environ ? J.
2005-03-05 10:48 ` Rechberger Markus
2005-03-05 11:12 ` Steve Graegert [this message]
2005-03-05 12:55   ` J.
2005-03-06 10:19   ` Glynn Clements

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6a00c8d505030503121038ff83@mail.gmail.com \
    --to=graegerts@gmail.com \
    --cc=linux-c-programming@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).