~{fd} is new to me. Please help me a bit...
> >>>
> >>> This isn't readlink support. It's a a smart solution to allow child
> >>> processes to access the shell's inherited file descriptors.
>
Lionel, I don't quite understand this. Can you explain a bit more?
> We already
> >>> heavily rely on this feature, both for IPC and to shorten very long
> >>> paths to speed processing up.
> >>>
> >
> > Yes, it's an ingenious solution to the problem of long paths. You pass
> > a dir fd in which acts as virtual "/" and all paths are appended to
> > it. Using /proc/.../fd instead of /megalong/path/ is MUCH faster and
> > easier.
>
Cedric, how can you get a dir fd? All I know about opening a dir is
opendir(3).
>
> Yes, we like this feature, too. At first it was a bit 'getting used
> to' but if you imagine that each fd works - as Cedric stated - a
> virtual root then script hackers will quickly understand the power of
> this feature. Suddenly you can have as many cwds as you wish and
> that's worth $$$$.
>
Irek, I don't quite understand you here either. Can't you have as many cwds
without using ~{x}?
_______________________________________________
ast-users mailing list
[email protected]
http://lists.research.att.com/mailman/listinfo/ast-users
