| delorie.com/archives/browse.cgi | search |
| Message-ID: | <39A53B77.BD031AE0@softhome.net> |
| Date: | Thu, 24 Aug 2000 17:12:55 +0200 |
| From: | Laurynas Biveinis <lauras AT softhome DOT net> |
| X-Mailer: | Mozilla 4.74 [en] (Win98; U) |
| X-Accept-Language: | lt,en |
| MIME-Version: | 1.0 |
| To: | Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> |
| CC: | djgpp-workers AT delorie DOT com |
| Subject: | Re: Symlink resolving rewrite |
| References: | <39A5266F DOT 2C931D88 AT softhome DOT net> <3028-Thu24Aug2000174804+0300-eliz AT is DOT elta DOT co DOT il> |
| Reply-To: | djgpp-workers AT delorie DOT com |
Eli Zaretskii wrote:
> What does readlink do on Unix?
I've tried:
$ mkdir testdir
$ ln -s testdir link1
$ cd testdir
$ touch file
$ ln -s file link2
$ cd ..
Then tiny program which calls readlink("link1/link2") returns
'file'. As expected. But in order to get this result, readlink()
had to resolve 'link1' part in passed arg, somehow. My current
implementation doesn't.
Laurynas
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |