[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
source tree organization (Was: Re: GRUB plans...)
From: |
Yoshinori K. Okuji |
Subject: |
source tree organization (Was: Re: GRUB plans...) |
Date: |
Wed, 24 Oct 2001 18:21:36 +0900 |
User-agent: |
Wanderlust/2.6.0 (Twist And Shout) SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (UnebigoryĆmae) APEL/10.3 Emacs/20.7 (i586-pc-linux-gnu) MULE/4.0 (HANANOEN) |
[I send this message to the list, since I'd like everyone to know what
the official maintainer thinks.]
I see Thierry's point about the organization of the source tree and
the documentation system. For now, I'm thinking these about the
organization:
* Making a small libc-like library. Currently GRUB has libc-like
functions in char_io.c and somewhere else, but this is bad, because
we need to realize if a function is necessary for Stage 1.5 (or
diskless images) manually. So it would be better to have many files,
one file for each function, create a static library of them, and
link GRUB images with the library.
* Having arch-dependent directories and a common directory. This is
not trivial, as we would want to have, for example, both common
commands and arch-dependent commands. I don't have any specific idea
about this at the moment.
As for the documentation, I don't like WEB personally. I don't like to
have a vast amount of comments. It is a Good Thing to have rich
comments, but comments must be terse. Lengthy documents are just
bothering for hackers, when they read source code. So, write good
documents, if possible. But PLEASE don't include them in source files.
Okuji
- Re: GRUB plans..., (continued)
Re: GRUB plans..., Yoshinori K. Okuji, 2001/10/24