Re: encapsulating directory operations

On Tue, 20 May 2025 19:33:18 +1000, Paul Edwards wrote:

"Lawrence D'Oliveiro" <ldo@nz.invalid> wrote in message
news:100hase$24odp$1@dont-email.me...

>
On Tue, 20 May 2025 16:06:19 +1000, Paul Edwards wrote:
>

And in essence, when you read from a directory, the only thing you
get is the filename.

>
You want at least the type of entry as well, surely.
>
<https://manpages.debian.org/readdir(3)>

 
No - I'm not attempting to support such sophistication.

It’s not about sophistication, it’s about efficiency in real-world
operation. Without that, you will need to do a second lookup in nearly
every common directory-traversal case.

If it is actually a subdirectory, then that is indicated with a "/"
at the end of the filename.

>
What if it's a symlink to a directory?

 
I guess that can be left as "implementation-defined". I would treat it
the same as a hardlink, ie a directory.

The key point about symlinks is they are not the same as hardlinks.

As far as I am aware, IBM mainframes are the most important systems on
the planet. The only professional ones too. Everything else is a clown
show.

You are aware wrong.