| 1 | This is the Guile developer notice-board. -*- change-log -*- |
| 2 | ---------------------------------------------------------------------- |
| 3 | CONTENTS: Notes of various kinds which the Guile developers want to |
| 4 | share among eachother, e. g., a memo about something which needs |
| 5 | fixing. Describing a certain problem here means that everyone is free |
| 6 | to fix it when and as he wishes. (Of course it can sometimes be suitable |
| 7 | to discuss it first.) |
| 8 | |
| 9 | RULES: Entries should have a date and the name of the author. Entries |
| 10 | should be sufficiently detailed to enable other members of the team to |
| 11 | understand them, but they need not be comprehensible to people who |
| 12 | don't spend much time on Guile. This file should not go into |
| 13 | snapshots or distributions, but is a strictly internal document. |
| 14 | |
| 15 | CONVENTIONS: ChangeLog format. (Reverse chronological order.) |
| 16 | ---------------------------------------------------------------------- |
| 17 | |
| 18 | Sun Mar 9 15:45:14 1997 Mikael Djurfeldt <mdj@mdj.nada.kth.se> |
| 19 | |
| 20 | * We need to discuss the long-term solution to Guile configuration |
| 21 | and customization. |
| 22 | |
| 23 | * Some day when more important stuff (module system, threads, Tk |
| 24 | interface etc) has been completed, we should split up SCM's |
| 25 | ChangeLog among us, and go through all changes since the birth of |
| 26 | Guile. We might find many nice bug fixes and improvements... |
| 27 | |
| 28 | * libguile/gc.c (scm_gc_sweep): The probability of collecting a |
| 29 | free cell should be very low (only occurring when a signal has |
| 30 | interrupted allocation). Nevertheless, the GC immediately exits |
| 31 | when the free cell test is enabled in the sweeper. Where does |
| 32 | this free cell come from? |
| 33 | |
| 34 | * libguile/arbiters.c: Remove this file? When we've implemented |
| 35 | POSIX thread support, "arbiters" will be superfluous. |
| 36 | |
| 37 | Thu Mar 6 00:54:59 1997 Mikael Djurfeldt <mdj@mdj.nada.kth.se> |
| 38 | |
| 39 | * libguile/unif.c: Introduce "fancy printing" for vectors. "Fancy |
| 40 | printing" is performed by the printer when the `fancyp' flag is |
| 41 | set in the print state (see print.h). One of its effects is that |
| 42 | sequences should be printed with maximum `length' objects. (This |
| 43 | is currently only used in backtraces and error messages). |
| 44 | This works for lists, but not yet for vectors and arrays. |
| 45 | |
| 46 | Wed Mar 5 22:56:19 1997 Mikael Djurfeldt <mdj@mdj.nada.kth.se> |
| 47 | |
| 48 | * libguile/struct.c, libguile/struct.h, libguile/gc.c: Structs |
| 49 | need reimplementation. Both user interface and representation |
| 50 | need to be improved. E. g., the struct part of scm_gc_mark need |
| 51 | to be a lot more efficient. We should probably do this redesign |
| 52 | when designing(/porting) the object system. |
| 53 | |
| 54 | * libguile/symbols.c (SCM_SYMBOL_HASH): This is slot is currently |
| 55 | not used for anything (except that it is used by symbol-hash). I |
| 56 | suppose it was originally intended to avoid doing multiple hashing |
| 57 | steps when handling symbols. |
| 58 | |
| 59 | Mon Mar 3 21:36:58 1997 Mikael Djurfeldt <mdj@mdj.nada.kth.se> |
| 60 | |
| 61 | * libguile/procprop.c: The current implementation of procedure |
| 62 | properties of closures uses a special property slot |
| 63 | (SCM_PROCPROPS (closure)), but primitive procedures don't have |
| 64 | such a slot. Setting or getting source properties for primitive |
| 65 | procedures currently involves making fake closures. These are |
| 66 | stored in an alist => finding the properties of a primitive |
| 67 | procedure is O (n primitive procedures with properties) which is |
| 68 | unacceptable. |
| 69 | |
| 70 | |