public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Bogdan <bogdandr@op.pl>
Cc: xfs@oss.sgi.com
Subject: Re: About errors in XFS header  files and xfsprogs
Date: Thu, 30 Aug 2007 17:55:56 +0100	[thread overview]
Message-ID: <20070830165556.GA13308@infradead.org> (raw)
In-Reply-To: <46D6F066.5000009@op.pl>

On Thu, Aug 30, 2007 at 06:29:26PM +0200, Bogdan wrote:
>                                The header files should not only be
> ISO-C-compatible, but even ANSI-C-compatible. This will allow anyone
> to use them.

Sais who?  The GNU C extensions are very useful for programming, and
there is no reason to move to an inferior dialect.

>  Please, make useful public functions available in header files.
> Especially platform_check_ismounted() and platform_check_iswritable()
> and other "platform" functions.
> 
>  Also, anything that is a part of the public interface, should be in
> the "xfs namespace", i.e. start with "xfs_". At least one issue of
> this type is known: the list_head structure, declared in other files
> from other libraries. Things like these are very important to fix,
> because they are making other header files useless.

There is no such thing as a public inteface.  There's a good reason
libxfs is not a shared libary - it's really nothing more but a collection
of useful routines for the xfs utilities.

If you think a proper shared library with a defined interface is a good
thing you're probably right, and people would welcome you to work on one.

  reply	other threads:[~2007-08-30 16:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-30 16:29 About errors in XFS header files and xfsprogs Bogdan
2007-08-30 16:55 ` Christoph Hellwig [this message]
2007-08-30 22:39   ` Martin Schröder
2007-08-30 23:12     ` Nathan Scott
2007-09-01 10:55   ` [PATCH] " Bogdan
2007-08-31  1:17 ` Barry Naujok

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=20070830165556.GA13308@infradead.org \
    --to=hch@infradead.org \
    --cc=bogdandr@op.pl \
    --cc=xfs@oss.sgi.com \
    /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