mirror of
https://git.savannah.gnu.org/git/guile.git
synced 2025-05-20 11:40:18 +02:00
*** empty log message ***
This commit is contained in:
parent
94c0b3b855
commit
d043e0bbf9
1 changed files with 9 additions and 0 deletions
9
HACKING
9
HACKING
|
@ -64,6 +64,15 @@ The only exceptions are the warnings about variables being clobbered
|
|||
by longjmp/vfork in eval.c. (Tho' if you can figure out how to get
|
||||
rid of those, too, I'd be happy.)
|
||||
|
||||
Note that the warnings generated vary from one version of GCC to the
|
||||
next, and from one architecture to the next (apparently). To provide
|
||||
a concrete common standard, Guile should compile without warnings from
|
||||
GCC 2.7.2.3 in a Red Hat 5.0 i386 Linux machine. Furthermore, each
|
||||
developer should pursue any additional warnings noted by on their
|
||||
compiler. This means that people using more stringent compilers will
|
||||
have more work to do, and assures that everyone won't switch to the
|
||||
most lenient compiler they can find.
|
||||
|
||||
- When you make a user-visible change (i.e. one that should be
|
||||
documented, and appear in NEWS, put an asterisk in column zero of the
|
||||
start of the ChangeLog entry, like so:
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue