82 |
- Investigate performance drop from Dec. 8, 2002 to Dec. 12, 2000. |
- Investigate performance drop from Dec. 8, 2002 to Dec. 12, 2000. |
83 |
|
|
84 |
- Eventually |
- Eventually |
85 |
|
- ice-9/ftw.scm should use closedir explicitly, to conserve file |
86 |
|
descriptors. |
87 |
|
|
88 |
|
- hashx-remove!, corresponding to other hash*-remove! functions. |
89 |
|
|
90 |
|
scm_hashx_remove_x exists, but has never been documented, and |
91 |
|
might be non-functional (looks like it's missing "&closure" in the |
92 |
|
scm_hash_fn_remove_x call). |
93 |
|
|
94 |
|
Might want to think about the procedures taken. Separate assoc |
95 |
|
and delete! suit existing such functions, but it's wasteful to |
96 |
|
traverse a bucket list once to see if an element exists, then |
97 |
|
again to delete it. Think about maybe a function returning both a |
98 |
|
modified list and a flag indicating whether a delete was done. Or |
99 |
|
maybe just returning the list tail of the target element. |
100 |
|
|
101 |
|
- mapping.scm hash-table-mapping-hooks uses hashx-create-handle, |
102 |
|
which doesn't exist. Probably a typo for hashx-create-handle!, |
103 |
|
just wants to get a little test program to exercise it. |
104 |
|
- mapping.scm hash-table-mapping-hooks uses hashx-get-handle in its |
105 |
|
constructed delete-proc, which is probably meant to be |
106 |
|
hashx-remove!, if/when such a function exists. |
107 |
|
|
108 |
- in6addr_loopback made available as some sort of constant, like |
- in6addr_loopback made available as some sort of constant, like |
109 |
INADDR_LOOPBACK for ipv4. |
INADDR_LOOPBACK for ipv4. |
110 |
- in6addr_any made available as some sort of constant, like |
- in6addr_any made available as some sort of constant, like |
111 |
INADDR_ANY for ipv4. Describe this under "bind" in the manual. |
INADDR_ANY for ipv4. Describe this under "bind" in the manual. |
112 |
|
|
113 |
- document the operation of the garbage collector (what's scanned, etc.) |
- document the operation of the garbage collector (what's scanned, etc.) |
114 |
- add support for srfi-25 (multi-dimensional arrays). |
- add support for srfi-25 (multi-dimensional arrays). |
115 |
- How do we handle guile's existing support? srfi module overrides? |
- How do we handle guile's existing support? srfi module overrides? |