summaryrefslogtreecommitdiff
path: root/TODO
diff options
context:
space:
mode:
authorAkim Demaille <akim@epita.fr>2001-05-22 12:32:18 +0000
committerAkim Demaille <akim@epita.fr>2001-05-22 12:32:18 +0000
commit6dff6080104d2c79ed58ca8d02bfe70bcae349ee (patch)
tree5a32663ada74dc49c18a1432c5728a1f38bb3c53 /TODO
parent54a5d2d5a7a21a9c1f4379624a90af8fe174a20e (diff)
downloadautoconf-6dff6080104d2c79ed58ca8d02bfe70bcae349ee.tar.gz
* autoconf.sh, autoreconf.sh, autoheader.sh, autoscan.pl, ifnames.sh:
Rename as... * autoconf.in, autoreconf.in, autoheader.in, autoscan.in, ifnames.in: these.
Diffstat (limited to 'TODO')
-rw-r--r--TODO19
1 files changed, 10 insertions, 9 deletions
diff --git a/TODO b/TODO
index c42f730e..f2198c21 100644
--- a/TODO
+++ b/TODO
@@ -7,7 +7,7 @@ these suggestions... their presence here doesn't imply my endorsement.
------------------------------------------------------------------------------
-* Autoconf 2.50
+* Autoconf 2.51
** --target & AC_ARG_PROGRAM
Shouldn't *any* `program' be installed as `$target_alias-program' even
@@ -15,13 +15,14 @@ if AC_ARG_PROGRAM is not called? That would be much more predictable.
Ian?
** Document
-Automake, Libtool.
+Automake, Libtool, AC_ARG_VAR.
+
+** RedHat's Autoconf page
+should be removed.
** AC_CHECK_TOOL...
Write a test that checks that it honors the values set by the user.
-* Autoconf 2.51
-
** AC_CHECK_FUNCS and AC_TRY_LINK_FUNC
I have still not understood what's the difference between the two
which requires to have two different sources: AC_LANG_CALL and
@@ -118,11 +119,11 @@ technology. Should we make this a new language? AC_LANG(ISO C). It
would be great to introduce AC_LANG_COMPILER in this release too.
* autoconf.texi
-Move the specific macro documentation blocks into the source files, and use
-a doc-block extraction/merge technique to get docuemntation into texi-file.
-This should help avoid bit-rot in the doc, and make the doc easier to update
-when people add/change macros. The name "autodoc" is probably already taken
-so we probably need another one.
+Move the specific macro documentation blocks into the source files,
+and use a doc-block extraction/merge technique to get docuemntation
+into texi-file. This should help avoid bit-rot in the doc, and make
+the doc easier to update when people add/change macros. The name
+"autodoc" is probably already taken so we probably need another one.
------------------------------------------------------------------------------