|
Check-in Number:
|
2418 | |
| Date: |
2002-Jul-29 18:33:48 (local)
2002-Jul-29 16:33:48 (UTC) |
| User: | ms |
| Branch: | |
| Comment: |
Remember data type abstraction and other important things. |
| Tickets: |
|
| Inspections: |
|
| Files: |
|
ossp-pkg/rc/00TODO 1.30 -> 1.31
--- 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
|
|
