[haiku-development] Re: Filesystem API documentation
- From: "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Mon, 16 Jul 2007 15:12:36 +0200 CEST
Ingo Weinhold <bonefish@xxxxxxxxxxxxxxx> wrote:
> On 2007-07-15 at 13:05:36 [+0200], Niels Reedijk <
> niels.reedijk@xxxxxxxxx>
> wrote:
> > Is there any reason not to
> > remove notify_listener() right now? (perhaps a good small task for
> > a
> > willing new young developer?)
> The only reason is, that there are file systems still using it. It
> shouldn't
> be that much of a problem to change that, though. Some of our new
> notify_*()
> functions require a bit more info, but that should usally be
> available
> anyway.
So in other words, the young and willing developer is definitely
welcome :-)
[...]
> > I see what you mean, but I think that it's good and consistent to
> > use
> > B_NOT_ALLOWED when the user does not have the proper permissions to
> > do
> > things, is a good convention. In other words, is there a list of
> > commonly used error codes when it comes to dealing with
> > filesystems?
> There's no list, but there're rules dictated by the POSIX standard. A
> good
> deal of FS hooks directly correspond to POSIX functions. The VFS
> passes the
> error codes returned by the hooks directly back to the userland.
> Therefore
> the hook should behave in way that complies with the POSIX function
> semantics, including error codes.
Exactly. A very good source of information for POSIX related things is:
http://www.opengroup.org/onlinepubs/009695399/toc.htm
Bye,
Axel.
- References:
- [haiku-development] Re: Filesystem API documentation
- From: Ingo Weinhold
Other related posts:
- » [haiku-development] Filesystem API documentation
- » [haiku-development] Re: Filesystem API documentation
- » [haiku-development] Re: Filesystem API documentation
- » [haiku-development] Re: Filesystem API documentation
- » [haiku-development] Re: Filesystem API documentation
- [haiku-development] Re: Filesystem API documentation
- From: Ingo Weinhold