File: TODO

package info (click to toggle)
yorick 1.5.08-1
  • links: PTS
  • area: main
  • in suites: woody
  • size: 7,508 kB
  • ctags: 7,937
  • sloc: ansic: 75,604; cpp: 1,282; lisp: 1,217; sh: 1,026; makefile: 616; fortran: 19
file content (43 lines) | stat: -rw-r--r-- 1,716 bytes parent folder | download | duplicates (2)
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
Most of these will probably be postponed until yorick-2.0.

(1) Fix the x(1)=y bug by adding a virtual instruction for assignment.

(2) Dictionary object could allow interpreted access to hashing,
    replace clumsy list object, and provide OO features.

(3) Add a syntax for trace operations; actually it would be better
    to go for an indexing syntax that allows you to specify that one
    index equals another.  The following would even allow more than
    two indices to be set equal:

        x(=,i,=,j,...)

    This even works with the =:start:stop:step syntax, which is very
    nice, and it should work on assignment as well, since all you are
    doing is adding the strides of the participating dimensions.

    Three minor problems:
    (a) Where does the new index go in the index list?
        Suggestion: at the position of the first marked index
    (b) What happens if only one index is marked?
        Suggestion: noop
    (c) Must the index lengths agree?

(4) L'Ecuyer random numbers, compiled Bessel, gamma, and elliptic funcs

(5) Investigate sort algorithm -- can performance for big numerical
    sorts be improved by actually moving the data during the sort?

(6) Work on new binary file model.
    (a) Directories?  (dictionaries?)
    (b) Interpreted close hooks?  Other hooks?
        -- should there be a destroy hook for any interpreted variable?
    (c) Support for opening family as array of filenames.
    (d) Attributes?  With dictionaries, maybe these can be interpreted.
    (e) Better low level support for interpreted open routines.

(7) Make yorick return non-0 exit status codes.

(8) Allow raw p_win interface with interpreted callbacks.  Also alarms.

(9) DLL interface.