Mercurial > hg > octave-nkf
comparison PROJECTS @ 2569:5e0c65023ba5
[project @ 1996-12-06 07:36:46 by jwe]
author | jwe |
---|---|
date | Fri, 06 Dec 1996 07:37:17 +0000 |
parents | 6fa1ac46c980 |
children | 2480ef198c46 |
comparison
equal
deleted
inserted
replaced
2568:ed6532d8bf12 | 2569:5e0c65023ba5 |
---|---|
201 together, similar to the way iostreams can be tied together. | 201 together, similar to the way iostreams can be tied together. |
202 | 202 |
203 ----------- | 203 ----------- |
204 Interpreter: | 204 Interpreter: |
205 ----------- | 205 ----------- |
206 | |
207 * If foo.oct and foo.m both exist in the LOADPATH, Octave will | |
208 always find foo.oct, even if foo.m appears earlier in the list of | |
209 directories. This should be fixed (in the kpathsearch library) to | |
210 find the first .oct or .m file in the path, and only prefer .oct | |
211 over .m if both files are in the same directory. | |
206 | 212 |
207 * Fix the grammar to allow structure references and index operations | 213 * Fix the grammar to allow structure references and index operations |
208 for for anonymous expressions. For example, it should be possible | 214 for for anonymous expressions. For example, it should be possible |
209 to write | 215 to write |
210 | 216 |