[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Enormous sizes of Hurd *.h headers

On Wed, May 17, 2000 at 08:39:57PM +0200, Tomasz Wegrzanowski wrote:
> I did ``cpp -D_GNU_SOURCE file.h | wc'' on a few headers.
> Here are results ( format: lines words bytes )
> hurd.h :
>   23528   16126  167120
> hurd/store.h
>   13732    9483  100985
> hurd/trivfs.h
>   24875   17743  184575
> hurd/diskfs.h
>   28631   21074  216393

Why don't you look at the original files? diskfs for example is a very high
level layer, and has a rich interface, which is described in the Hurd info
manual and in the code. All of the above depend on many of the ther more low
level libraries in the hurd (ports, thread, iohelp, fshelp etc).
BTW, although this is not true for the above headers, there are also MiG
generated files, where you should read the *.defs file instead.

> Hurd headers are about 10x bigger than other C headers.
>     ( This is one of the reasons why reading headers doesn't work
>       as a way of learning programming Hurd )

You shouldn't read the headers, but the info manual, and, more important,
the source. If you want to write a translator based on trivfs or diskfs, you
really better start with an existing translator that is similar to the one
you need and modify it.

For example, for the fatfs 0.1 translator I used almost all of isofs/*
For the next version, I use much of the ext2fs code.

`Rhubarb is no Egyptian god.' Debian http://www.debian.org Check Key server 
Marcus Brinkmann              GNU    http://www.gnu.org    for public PGP Key 
Marcus.Brinkmann@ruhr-uni-bochum.de,     marcus@gnu.org    PGP Key ID 36E7CD09
http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/       brinkmd@debian.org

Reply to: