linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ron Michael Khu <ronkhu@ntsp.nec.co.jp>
To: linux-c-programming@vger.kernel.org
Subject: Re: HOME directory
Date: Tue, 26 Apr 2005 00:46:04 +0800	[thread overview]
Message-ID: <426D1ECC.3000307@hq.ntsp.nec.co.jp> (raw)
In-Reply-To: <426D1E0B.6020307@hq.ntsp.nec.co.jp>

Ooops... inapplicable solution...
scratch it...


Ron Michael Khu wrote:

> I dont know what specific system calls are used for retreiving the 
> current user or home dir(if there are any).
> But perhaps u can make use of the getenv() function to retrieve the 
> value of $HOME and $USER
> (it may not work on some shells, though, didnt test it)
>
>
>
>
> HIToC wrote:
>
>>> Hello all!
>>>     I am writing a piece of code that makes files, open directories 
>>> in my
>>> HOME directory. All worked well until I changed the name of my HOME 
>>> dir.
>>> To make the code portable I tried with use of '~' character:
>>>
>>>     const char*    filename = "~/file.txt";
>>>     ofstream     my_file(filename, ios::out);
>>>
>>> but this solution does not work.
>>> Have you any suggestion to find the path of the current home 
>>> directory or
>>> the current user name?
>>>
>>> Thanks for any suggestion.
>>>  
>>>
>>
>>
>
>



  reply	other threads:[~2005-04-25 16:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-25 16:27 HOME directory HIToC
     [not found] ` <426D1DC8.2080900@hq.ntsp.nec.co.jp>
2005-04-25 16:42   ` Ron Michael Khu
2005-04-25 16:46     ` Ron Michael Khu [this message]
2005-04-25 16:43 ` Benjamin Machuletz
2005-04-25 16:59 ` Richard Nairn
2005-04-25 17:05 ` Steve Graegert
     [not found]   ` <426D38D3.5060901@tlen.pl>
     [not found]     ` <6a00c8d505042511529bd72c8@mail.gmail.com>
2005-04-26 11:26       ` Adam Dyga
2005-04-25 17:06 ` Glynn Clements
  -- strict thread matches above, loose matches on Subject: below --
2005-04-25 16:50 Luciano Moreira - ht
2005-04-28 12:28 HIToC

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=426D1ECC.3000307@hq.ntsp.nec.co.jp \
    --to=ronkhu@ntsp.nec.co.jp \
    --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).