File: TODO

package info (click to toggle)
guile-core 1%3A1.3.4-2
  • links: PTS
  • area: main
  • in suites: potato
  • size: 5,348 kB
  • ctags: 5,474
  • sloc: ansic: 45,175; lisp: 9,030; sh: 7,720; asm: 1,580; makefile: 483; awk: 162; csh: 50
file content (54 lines) | stat: -rw-r--r-- 1,618 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
* Add facilities for debugging Scheme programs.

The low-level debugging support is done, and we are now working on the
user interface.

* Documentation.

We have a new layout for the reference manual which covers the
C/Scheme interface, as well as the scheme variants.  We also want a
more thorough tutorial manual, but we haven't sketched that out yet.


Desired later on

* Good interface to Tk

* Add a convenient facility for running a pipeline of processes
with redirections.  Gary Houston <ghouston@actrix.gen.nz>
is working on this.

* Make it possible to link Guile and TK without using libtcl.a, by
providing Guile-based replacements for the libtcl.a functions that TK
requires.

* Make ordinary lambda functions work as callbacks for Tk;
eliminate the need for tcl-lambda.

* Translators for additional languages; in particular, Perl, Python,
TCL, Emacs Lisp, and Rexx.

* A package for time conversions and formatting.

* Make GDB work with Guile

This would permit programmable debugging and a nice integrated GUI.


Low-level things

* Use the SCM trick of tagging environments with immediates (see m_letrec1)
  to convert source correctly in unmemocopy.


Optimizations

* Eliminate argument checking for closures.  One way to do it is to
  set the cdr of application forms to an immediate representing the
  arity of the call.  If the closure contains a corresponding
  immediate, these can be matched against eachother.

* Implement a thread-safe alternative to SCM's environment caches:

  Add an extra argument to SCM_CEVAL: "evaluation context".
  Evaluation contexts contain a stack of locations.