Update NEWS and TODO

This commit is contained in:
Akim Demaille 2000-05-12 07:38:52 +00:00
parent 269df76643
commit 83d910e14e
2 changed files with 16 additions and 71 deletions

32
NEWS
View File

@ -20,6 +20,22 @@ autoupdate is now much more powerful, and is able to provide the glue
code which might be needed to move from an old macro to its newer
equivalent.
** autoheader
The internal machinery of autoheader has completely changed. As a
result, using an `acconfig.h' should be considered as obsoleted, and
you are encouraged to get rid of it using the AH macros.
** Fortran 77 compilers
Support for automatically determining a Fortran 77 compilers
name-mangling scheme. New CPP macros F77_FUNC and F77_FUNC_ are
provided to wrap C/C++ identifiers, thus making it easier and more
transparent for C/C++ to call Fortran 77 routines, and Fortran 77 to
call C/C++ routines. See the Texinfo documentation for details.
** Test suite
The testsuite no longer uses DejaGNU. It should be easy to submit
test cases in this new frame work.
** configure
- --help, --help=long, -hl
no longer dumps useless items.
@ -140,22 +156,6 @@ equivalent.
- C++ compatibility
Almost every single macros has been revisited in order to support at
best CC=c++.
** Test suite
The testsuite no longer uses DejaGNU. It should be easy to submit
test cases in this new frame work.
** Autoheader
The internal machinery of Autoheader has completely changed. As a
result, using an `acconfig.h' should be considered as obsoleted, and
you are encouraged to get rid of it using the AH macros.
** Fortran 77 compilers
Support for automatically determining a Fortran 77 compilers
name-mangling scheme. New CPP macros F77_FUNC and F77_FUNC_ are
provided to wrap C/C++ identifiers, thus making it easier and more
transparent for C/C++ to call Fortran 77 routines, and Fortran 77 to
call C/C++ routines. See the Texinfo documentation for details.
Major changes in Autoconf 2.14:
There was no release of GNU Autoconf 2.14.

55
TODO
View File

@ -13,20 +13,10 @@ These are things mandatory to fulfill before releasing 2.15. There
are also suggestions we should either satisfy right now (they're
easy), or remove (obsoleted since then).
** AU_, AH_
Document.
** AC_COPYRIGHT
Document.
** m4
The error messages for indir and dumpdef are uselessly different. Fix
this for translators.
** AC_LANG
I don't understand why we have this weird system of AC_SAVE and
RESTORE, why not push/pop etc?
** AC_PROVIDE
I think it is the epilogue that should provide, not the prologue. Not
clear: there are risks of circular dependencies :(. In fact the
@ -46,12 +36,6 @@ instance, there is still AM_PROG_LIBTOOL. Anyawy, since autoupdate
takes care of them, it is no longer the role of Automake to handle
this. Most should be removed.
** AC_INCLUDE
m4_include_unique should probably check only for the base name, to
warn includes of foo/bar.m4 and baz/bar.m4. AC_INCLUDES could admit
$2 to specify the directory? Or do we want another macro to define the
m4/ dir, a la AC_CONFIG_AUXDIR.
** Doc: autoconf
Document --install. Should --install `fix' configure.in for the user?
@ -92,13 +76,6 @@ From: Roland McGrath <roland@gnu.ai.mit.edu>
* Autoconf 3
** Find a solution for LIBOBJS
Currently Automake has no clean way to get the list of files that are
required for the distribution. One aspect of this is LIBOBJS. But we
can imagine going further and provide a mean for macro authors to
specify various files they need to distribute (headers, files to
compile and others).
** Split all those &#@! files.
acgeneral and acspecific is a bad design. The split should be done
according to the families. For instance AC_CHECK_FUNCS,
@ -158,10 +135,6 @@ macros for the listed functions.
This requires to obsolete the feature `break' in ACTION-IF, since all
the loops are to be handled by m4, not sh.
** Merge the two lex macros, AC_PROG_LEX and AC_DECL_YYTEXT?
Add give a mean to *require* Flex instead of Lex. Or at least explain
how to do that.
** Faces of a test
Each macro can potentially come with several faces: of course the
configure snippet (AC_foo), a config.h snippet (AH_foo), a system.h
@ -181,13 +154,6 @@ require a specific AC_ tests, but a specialized AS_ macro.
------------------------------------------------------------------------------
* Matthew D. Langston's suggestions:
** Change all of Autoconf's macros that print a help string via
"configure --help" to use new AC_HELP_STRING macro.
------------------------------------------------------------------------------
* Make AC_CHECK_LIB check whether the function is already available
before checking for the library. This might involve adding another
kind of cache variable to indicate whether a given function needs a
@ -220,10 +186,6 @@ require a specific AC_ tests, but a specialized AS_ macro.
------------------------------------------------------------------------------
* Allow [ and ] in AC_DEFINE args.
------------------------------------------------------------------------------
* Mike Haertel's suggestions:
** Provide header files containing decls for alloca, strings, etc.
@ -262,23 +224,6 @@ In config.status comment, put the host/target/build types, if used.
------------------------------------------------------------------------------
The default of unlimited permission is fine, but there should be some easy
way for configure to have copyright terms passed through from configure.in.
Maybe AC_LICENSE([...]).
From: roland@gnu.ai.mit.edu (Roland McGrath)
------------------------------------------------------------------------------
AC_MSG_CHECKING([checking for ANSI #stringize])
AC_REVISION([ #(@) revision 2.1 ])
causes bogus code to be generated for whatever immediately follows. The
problem goes away if the '#' is removed. Probably the macros are not
disabling the m4 "comment" feature when processing user-supplied strings.
-Jim Avera jima@netcom.com
------------------------------------------------------------------------------
on hal.gnu.ai.mit.edu, configure is getting the wrong answer for
AC_CHECK_FUNCS(select).