aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorArnold D. Robbins <arnold@skeeve.com>2012-10-11 19:31:58 +0200
committerArnold D. Robbins <arnold@skeeve.com>2012-10-11 19:31:58 +0200
commit921f9dd3b97236892c632e15c1a8f35ce3e74533 (patch)
tree18b99e363e42b939fc43940458076fee45ac74d3
parent8eb78103a37e75819388c2a175caf40bf0f7b4c9 (diff)
downloadegawk-921f9dd3b97236892c632e15c1a8f35ce3e74533.tar.gz
egawk-921f9dd3b97236892c632e15c1a8f35ce3e74533.tar.bz2
egawk-921f9dd3b97236892c632e15c1a8f35ce3e74533.zip
Minor doc update in FUTURES.
-rw-r--r--FUTURES6
1 files changed, 2 insertions, 4 deletions
diff --git a/FUTURES b/FUTURES
index e42cd013..ba1f1b26 100644
--- a/FUTURES
+++ b/FUTURES
@@ -24,7 +24,8 @@ For 4.1
DONE: Redo the loadable modules interface from the awk level.
- DONE: SYMTAB functionality.
+ DONE: Consider really implementing BWK awk SYMTAB for seeing what
+ global variables are defined.
Continue code reviews / code cleanup
@@ -56,9 +57,6 @@ For 4.2
??? Gnulib
- Consider really implementing BWK awk SYMTAB for seeing what
- global variables are defined.
-
Probably never:
===============
Do an optimization pass over parse tree?