Index: ossp-pkg/rc/00TODO
RCS File: /v/ossp/cvs/ossp-pkg/rc/00TODO,v
rcsdiff -q -kk '-r1.30' '-r1.31' -u '/v/ossp/cvs/ossp-pkg/rc/00TODO,v' 2>/dev/null
--- 00TODO	2002/07/10 19:03:21	1.30
+++ 00TODO	2002/07/29 16:33:48	1.31
@@ -5,6 +5,7 @@
   Manpage reorganization lacks important option combination info.
   What when multiple command interpreters and one --print or --eval given?
   File rc.func totally undocumented, but logic should be clear.
+  Check combo options for correctness, like config contains exc, evl, prn.
   Control flow
     Explain logical ordering of multiple section spanning multiple rcfiles.
     Give example semantics of a common scenario.
@@ -37,7 +38,6 @@
   Use str_hash von ossp str or static RC_XXX_VAL array from rc_option.h.
   Restore lost multiple location merging logic.
   Use OSSP cfg library for dotconf parsing, ask Ralf to help.
-  Add config section of each rc file to start of script.
 
 Implementation
   Correct assertion, sanity check, and if () checks according to one standard.
@@ -48,6 +48,28 @@
   I think rc_anal is violating the singleton configuration.
   Totally remove warnings from the exception logic
 
+Change data type locations to private for additional abstraction
+  Index: ossp-pkg/cfg/cfg_buf.c
+  ============================================================
+  +struct cfg_buf_st {
+  +    char   *buf_ptr;
+  +    size_t  buf_size;
+  +    size_t  buf_len;
+  +};
+  +
+
+  Index: ossp-pkg/cfg/cfg_buf.h
+  ============================================================
+   struct cfg_buf_st;
+   typedef struct cfg_buf_st cfg_buf_t;
+
+  -struct cfg_buf_st {
+  -    char   *buf_ptr;
+  -    size_t  buf_size;
+  -    size_t  buf_len;
+  -};
+  -
+
 Detailed ;-) project plan
 -------------------------
 Release v0.8