|
3162
|
1 <html> |
|
|
2 <pre> |
|
2330
|
3 Octave PROJECTS -*- text -*- |
|
|
4 =============== |
|
|
5 |
|
5041
|
6 Check with maintainers@octave.org for a possibly more current copy. |
|
|
7 Also, if you start working steadily on a project, please let |
|
|
8 maintainers@octave.org know. We might have information that could |
|
|
9 help you; we'd also like to send you the GNU coding standards. |
|
2330
|
10 |
|
|
11 This list is not exclusive -- there are many other things that might |
|
|
12 be good projects, but it might instead be something we already have, |
|
5041
|
13 so check with maintainers@octave.org before you start. |
|
2330
|
14 |
|
|
15 --------- |
|
|
16 Numerical: |
|
|
17 --------- |
|
|
18 |
|
|
19 * Improve logm, and sqrtm. |
|
|
20 |
|
3713
|
21 * Improve complex mapper functions. See W. Kahan, ``Branch Cuts for |
|
|
22 Complex Elementary Functions, or Much Ado About Nothing's Sign |
|
|
23 Bit'' (in The State of the Art in Numerical Analysis, eds. Iserles |
|
|
24 and Powell, Clarendon Press, Oxford, 1987) for explicit |
|
|
25 trigonometric formulae. |
|
2330
|
26 |
|
|
27 * Make functions like gamma() return the right IEEE Inf or NaN |
|
|
28 values for extreme args or other undefined cases. |
|
|
29 |
|
|
30 * Handle complex values in fread and fwrite. |
|
|
31 |
|
|
32 * Support for lp_solve for linear programming problems. |
|
|
33 |
|
|
34 * Free QP solver. |
|
|
35 |
|
|
36 * Free NLP solver. |
|
|
37 |
|
|
38 * Fix CollocWt to handle Laguerre polynomials. Make it easy to |
|
|
39 extend it to other polynomial types. |
|
|
40 |
|
3130
|
41 * Make filter faster (perhaps by calling BLAS functions). |
|
|
42 |
|
2330
|
43 * Add optional arguments to colloc so that it's not restricted to |
|
|
44 Legendre polynomials. |
|
|
45 |
|
|
46 * Fix eig to also be able to solve the generalized eigenvalue |
|
|
47 problem, and to solve for eigenvalues and eigenvectors without |
|
|
48 performing a balancing step first. |
|
|
49 |
|
|
50 * Move rand, eye, xpow, xdiv, etc., functions to the matrix classes. |
|
|
51 |
|
2477
|
52 * Use octave_allocator for memory management in Array classes once |
|
|
53 g++ supports static member templates. |
|
|
54 |
|
2330
|
55 * Implement the following functions: |
|
|
56 -- ppval -- cross -- dot |
|
|
57 |
|
2789
|
58 * When constructing NLConst (and other) objects, make sure that |
|
|
59 there are sufficient checks to ensure that the dimensions all |
|
|
60 conform. |
|
|
61 |
|
2439
|
62 * Allow parameters to be passed through the call to fsolve() to the |
|
2777
|
63 user-supplied function for Matlab compatibility. Don't place an |
|
2439
|
64 upper limit on the number of arguments. |
|
|
65 |
|
2330
|
66 * Check matrix classes for proper handling of empty matrices. |
|
|
67 |
|
2789
|
68 * Make operations with empty matrices produce empty matrices, for |
|
|
69 compatibility with Matlab (but only if Matlab 5 still does things |
|
|
70 this way). For example: [1, 2] * [] ==> []. |
|
|
71 |
|
2330
|
72 * Improve design of ODE, DAE, classes. |
|
|
73 |
|
|
74 * Extend meaning of .* to include v .* M or M .* v (where v is a |
|
|
75 column vector with the same number of rows as M) to scale rows of |
|
|
76 M by elements of v. Similarly, if w is a row vector with as many |
|
|
77 columns as M, then either w .* M or M .* w scales the columns of |
|
|
78 M. |
|
|
79 |
|
2497
|
80 * Given two vectors x and y of length m and n, implement a function |
|
|
81 outer (x, y, f) that returns an m-by-n matrix with entries |
|
|
82 f (x(i), y(j)). If f is omitted, multiplication is the default. |
|
2506
|
83 Should probably work for any vectors, not just if x is a column |
|
|
84 vector and y is a row vector. |
|
2497
|
85 |
|
2789
|
86 * Make it possible to solve b = L \ x efficiently, either by |
|
|
87 providing an explicit function call, or by automatically |
|
|
88 determining that L is triangular. If it is done automatically, |
|
|
89 provide some means for determining whether Octave has actually |
|
|
90 detected that the matrix is triangular. |
|
|
91 |
|
2799
|
92 * The polyfit function uses the economy QR factorization, but even |
|
|
93 that can take a lot of time for large datasets. Consider an |
|
|
94 option to compute the result with inv (A' * A) * A' * y or some |
|
|
95 other faster method.d Possibly just switch to this method if the |
|
|
96 dataset is larger than some value. |
|
|
97 |
|
3141
|
98 * Make QR more memory efficient for large matrices when not all the |
|
|
99 columns of Q are required (apparently this is not handled by the |
|
|
100 lapack code yet). |
|
|
101 |
|
2799
|
102 * Consider making the behavior of the / and \ operators for |
|
3758
|
103 non-square systems compatible with Matlab. Currently, they return |
|
|
104 the minimum norm solution from DGELSS, which behaves differently. |
|
2799
|
105 |
|
5164
|
106 --------------- |
|
|
107 Sparse Matrices: |
|
|
108 --------------- |
|
|
109 |
|
|
110 * QR factorization functions, also for use in lssolve functions. Write |
|
|
111 svds function based on this. Write sprank function based on svds. |
|
|
112 |
|
5322
|
113 * Once dmperm is implemented, perhaps use the technique to detect permuted |
|
|
114 triangular matrices with permutations in both rows and cols. |
|
5164
|
115 |
|
|
116 * Implement fourth argument to the sprand and sprandn that the leading |
|
|
117 brand implements. |
|
|
118 |
|
5282
|
119 * Sparse logical indexing in idx_vector class so that something like |
|
|
120 "a=sprandn(1e6,1e6,1e-6); a(a<1) = 0" won't cause a memory overflow. |
|
5164
|
121 |
|
|
122 * Write the rest of the sparse docs |
|
|
123 |
|
|
124 * The algo in TOMS 582 is perfect for symrcm function. However, this is |
|
|
125 under the ACM license and can't be used in a GPL program. |
|
|
126 |
|
|
127 An alternative is that PETSC is GPL compatiable and has a symrcm |
|
|
128 implemented from the original SPARSPAK. Its not clear that this is |
|
|
129 legal to me as I have found no clarification of the original license |
|
|
130 of SPARSPAK. As PETSC has had this code for over 10 years without |
|
|
131 problem, we can perhaps assume that there is no issues. Maybe need |
|
|
132 to contact PETSC people or the SPARSPAK people at uni of waterloo |
|
|
133 to check issues. |
|
|
134 |
|
|
135 * Make spalloc(r,c,n) actually create an empty sparse with n non-zero |
|
|
136 elements? This allows something like |
|
|
137 |
|
|
138 sm = spalloc (r,c,n) |
|
|
139 for j=1:c |
|
|
140 for i=1:r |
|
|
141 tmp = foo (i,j); |
|
|
142 if (tmp != 0.) |
|
|
143 sm (i,j) = tmp; |
|
|
144 endif |
|
|
145 endfor |
|
|
146 endfor |
|
|
147 |
|
|
148 actually make sense. Otherwise the above will cause massive amounts |
|
|
149 of memory reallocation. |
|
|
150 |
|
|
151 The fact is that this doesn't make sense in any case as the assign |
|
|
152 function makes another copy of the sparse matrix. So although spalloc |
|
|
153 might easily be made to have the correct behaviour, the first assign |
|
|
154 will cause the matrix to be resized !!! There seems to be no simple |
|
|
155 way to treat this but a complete rewrite of the sparse assignment |
|
|
156 functions... |
|
|
157 |
|
5322
|
158 * Port the sparse testing code into the DejaGNU testing code. Add tests |
|
|
159 for spkron, matrix_type, luinc.. |
|
5164
|
160 |
|
|
161 * Other missing Functions |
|
|
162 - eigs |
|
5506
|
163 - dmperm Use Tim Davis' BTF code when available |
|
5164
|
164 - symmmd Superseded by symamd |
|
|
165 - colmmd Superseded by colamd |
|
|
166 - sprandsym |
|
|
167 - etreeplot |
|
|
168 - treeplot |
|
|
169 - gplot |
|
|
170 - treelayout |
|
|
171 - cholinc |
|
|
172 - condest |
|
|
173 - normest |
|
|
174 - bicg |
|
|
175 - bicgstab |
|
|
176 - cgs |
|
|
177 - gmres |
|
|
178 - lsqr |
|
|
179 - minres |
|
|
180 - pcg Can this be taken from o-forge? Is it compatiable |
|
|
181 - pcr Can and should this be taken from o-forge? |
|
|
182 - qmr |
|
|
183 - symmlq |
|
|
184 - spaugment |
|
|
185 |
|
2330
|
186 -------- |
|
|
187 Graphics: |
|
|
188 -------- |
|
|
189 |
|
|
190 * Make plotting with plplot work. |
|
|
191 |
|
|
192 * Fix interface with gnuplot to wait for gnuplot to output any text |
|
|
193 before octave returns a prompt. Possible by implementing two |
|
|
194 way communication between gnuplot and Octave. |
|
|
195 |
|
3136
|
196 * Handle gnuplot ranges correctly for parametric modes (accept 3 |
|
|
197 ranges for 2d plots and 5 ranges for 3d plots). |
|
|
198 |
|
2330
|
199 * Make gsave (and possibly gload) work. Implement gsave by having it |
|
|
200 also alter the plot command to not use temporary files (perhaps |
|
|
201 with some user-specified template for naming them) and then |
|
|
202 sending a `save' command to gnuplot. |
|
|
203 |
|
|
204 * It would be nice to be able to check that a plot is currently |
|
|
205 being displayed. |
|
|
206 |
|
2422
|
207 * Implement clf, gcf, get, set, orient, print, close, etc. in |
|
|
208 Matlab-compatible ways. |
|
2330
|
209 |
|
|
210 * Make it possible to check the current graphics terminal type. |
|
|
211 |
|
2560
|
212 * If possible, pass data to gnuplot without using temporary files. |
|
|
213 |
|
|
214 * If possible, pass binary data to gnuplot to speed things up. |
|
|
215 |
|
2799
|
216 * If using gnuplot, consider setting a smaller default for the |
|
|
217 `zero' value (e.g., set zero sqrt (realmin) or something). |
|
|
218 |
|
2330
|
219 ------- |
|
|
220 Strings: |
|
|
221 ------- |
|
|
222 |
|
2789
|
223 * Improve performance of string functions, particularly for |
|
|
224 searching and replacing. |
|
|
225 |
|
|
226 * Provide some regex matching functions. |
|
|
227 |
|
2330
|
228 * Convert string functions to work on string arrays. |
|
|
229 |
|
|
230 * Make find work for strings. |
|
|
231 |
|
2378
|
232 * Consider making octave_print_internal() print some sort of text |
|
|
233 representation for unprintable characters instead of sending them |
|
|
234 directly to the terminal. (But don't do this for fprintf!) |
|
|
235 |
|
|
236 * Consider changing the default value of `string_fill_char' from SPC |
|
|
237 to NUL. |
|
|
238 |
|
2560
|
239 * Consider making ["test", []] ==> "test", for compatibility with |
|
|
240 Matlab, at least when some set of preferences are set. |
|
|
241 |
|
2330
|
242 ---------------- |
|
|
243 Other Data Types: |
|
|
244 ---------------- |
|
|
245 |
|
|
246 * Template functions for mixed-type ops. |
|
|
247 |
|
|
248 ------------------------ |
|
|
249 Graphical User Interface: |
|
|
250 ------------------------ |
|
|
251 |
|
|
252 * In an X11 or other windowing environment, allow the user to pop up |
|
|
253 windows for menus and other purposes. A good place to start might |
|
|
254 be Tk, as long as Tcl is avoided. |
|
|
255 |
|
|
256 * Add a way to handle events, like alarms, mouse clicks, etc. |
|
|
257 |
|
|
258 ------------ |
|
|
259 Input/Output: |
|
|
260 ------------ |
|
|
261 |
|
|
262 * Make fread and fwrite work for complex data. Iostreams based |
|
|
263 versions of these functions would also be nice, and if you are |
|
|
264 working on them, it would be good to support other size |
|
|
265 specifications (integer*2, etc.). |
|
|
266 |
|
5008
|
267 * Make fread and fopen look in LOADPATH for files. |
|
2330
|
268 |
|
|
269 * Make load and save look for <file>.mat if only given <file>. |
|
|
270 |
|
2799
|
271 Potential sticky points: |
|
|
272 |
|
|
273 - For load, if both foo and foo.mat exist, should it prefer foo |
|
|
274 or foo.mat? Should the preference depend on the arguments to |
|
|
275 load? I think it should only prefer .mat files if the |
|
|
276 -mat-binary option is supplied, or if the file foo.mat exists |
|
|
277 but the file foo does not. |
|
|
278 |
|
|
279 - For save, should it prefer to create foo or foo.mat? Should |
|
|
280 the preference depend on the arguments to save? Should the |
|
|
281 default_save_format imply a default preference? I think it |
|
|
282 should only create .mat files if it is writing Matlab |
|
|
283 compatible files. |
|
|
284 |
|
2330
|
285 * Move some pr-output stuff to liboctave. |
|
|
286 |
|
|
287 * Make the cutoff point for changing to packed storage a |
|
|
288 user-preference variable with default value 8192. |
|
|
289 |
|
2378
|
290 * Make it possible to load other image formats (ppm, pbm, etc. would |
|
|
291 probably be best since there are already filters to convert to |
|
|
292 these formats from others.) |
|
|
293 |
|
2330
|
294 * Complain if there is not enough disk space available (I think |
|
|
295 there is simply not enough error checking in the code that handles |
|
|
296 writing data). |
|
|
297 |
|
|
298 * Make it possible to tie arbitrary input and output streams |
|
|
299 together, similar to the way iostreams can be tied together. |
|
|
300 |
|
|
301 ----------- |
|
|
302 Interpreter: |
|
|
303 ----------- |
|
|
304 |
|
3162
|
305 * Allow customization of the debug prompt. |
|
|
306 |
|
|
307 * For the keyboard function, parse return (or quit) more |
|
|
308 intelligently so that something like |
|
|
309 |
|
|
310 debug> x = 1; return |
|
|
311 |
|
|
312 will work as expected. |
|
|
313 |
|
5008
|
314 * Handle multi-line input at the keyboard/debug prompt correctly. |
|
|
315 |
|
2601
|
316 * Fix the parser so that |
|
|
317 |
|
3081
|
318 if (expr) 'this is a string' end |
|
|
319 |
|
|
320 is parsed as IF expr STRING END. |
|
|
321 |
|
2330
|
322 * Consider grouping all preference variables in a structure instead |
|
|
323 of further polluting the namespace. Maybe `Octave_options.xxx'? |
|
|
324 |
|
|
325 * Rewrite functions in input.cc to do the right thing in all cases |
|
|
326 of using readline, forced interactive behavior, echoing of input, |
|
|
327 etc. |
|
|
328 |
|
|
329 * Consider making linspace() and logspace() return the value |
|
|
330 corresponding to the first argument if the number of requested |
|
|
331 points is 1. |
|
|
332 |
|
|
333 * Consider allowing an arbitrary property list to be attached to any |
|
|
334 variable. This could be a more general way to handle the help |
|
|
335 string that can currently be added with `document'. |
|
|
336 |
|
|
337 * Allow more command line options to be accessible as built-in |
|
|
338 variables (--echo-commands, etc.). |
|
|
339 |
|
|
340 * Allow `octave -c STRING' to execute commands from STRING then |
|
|
341 exit. |
|
|
342 |
|
|
343 * Make the interpreter run faster. |
|
|
344 |
|
|
345 * Make it possible to disable or enable all warnings on an |
|
|
346 individual basis from the command line or via some built-in |
|
|
347 structure variable. |
|
|
348 |
|
2378
|
349 * Warn about complex comparisons? Could just use double_value() or |
|
|
350 matrix_value() instead of explicit conversions to real types. For |
|
|
351 this to really be useful, some additional information must be |
|
|
352 available to point to the location of the code that triggers the |
|
|
353 warning. |
|
|
354 |
|
4325
|
355 * Allow arbitrary lower bounds for array indexing. |
|
2330
|
356 |
|
4325
|
357 * Improve performance of recursive function calls. |
|
2330
|
358 |
|
|
359 * Improve the way ignore_function_time_stamp works to allow |
|
3167
|
360 selecting by individual directories or functions. |
|
2330
|
361 |
|
|
362 * Add a command-line option to tell Octave to just do syntax |
|
|
363 checking and not execute statements. |
|
|
364 |
|
|
365 * Is it necessary for do_binary_op and do_unary_op to be friends of |
|
|
366 the tree_constant class. |
|
|
367 |
|
|
368 * Clean up symtab and variable stuff. |
|
|
369 |
|
|
370 * Input stream class for parser files -- must manage buffers for |
|
|
371 flex and context for global variable settings. |
|
|
372 |
|
3162
|
373 * make parser do more semantic checking, continue after errors when |
|
|
374 compiling functions, etc. |
|
|
375 |
|
2330
|
376 * Make LEXICAL_ERROR have a value that is the error message for |
|
|
377 parse_error() to print? |
|
|
378 |
|
|
379 * Add a run-time alias mechanism that would allow things like |
|
|
380 |
|
|
381 alias fun function_with_a_very_long_name |
|
|
382 |
|
|
383 so that `function_with_a_very_long_name' could be invoked as |
|
|
384 `fun'. |
|
|
385 |
|
|
386 * What should is_global() return when called for built-in variables? |
|
|
387 |
|
|
388 * Allow local changes to variables to be written more compactly than |
|
|
389 is currently possible with unwind_protect. For example, |
|
|
390 |
|
|
391 function f () |
|
|
392 local prefer_column_vectors = something; |
|
|
393 ... |
|
|
394 endfunction |
|
|
395 |
|
|
396 would be equivalent to |
|
|
397 |
|
|
398 function f () |
|
3758
|
399 save_prefer_column_vectors = prefer_column_vectors; |
|
2330
|
400 unwind_protect |
|
|
401 prefer_column_vectors = something; |
|
|
402 ... |
|
|
403 unwind_protect_cleanup |
|
|
404 prefer_column_vectors = save_prefer_column_vectors; |
|
|
405 end_unwind_protect |
|
|
406 endfunction |
|
|
407 |
|
|
408 * Fix all function files to check for bogus inputs (wrong number or |
|
|
409 types of input arguments, wrong number of output arguments). |
|
|
410 |
|
2789
|
411 * Reduce the memory and time required to parse very large matrix |
|
|
412 lists. |
|
|
413 |
|
2330
|
414 * Handle options for built-in functions more consistently. |
|
|
415 |
|
|
416 * Too much time is spent allocating and freeing memory. What can be |
|
|
417 done to improve performance? |
|
|
418 |
|
|
419 * Error output from Fortran code is ugly. Something should be done to |
|
|
420 make it look better. |
|
|
421 |
|
|
422 * It would be nice if output from the Fortran routines could be |
|
|
423 passed through the pager. |
|
|
424 |
|
|
425 * Attempt to recognize common subexpressions in the parser. |
|
|
426 |
|
|
427 * Handle arrays with more than two dimensions. |
|
|
428 |
|
|
429 * Consider making it possible to specify an empty matrix with a |
|
|
430 syntax like [](e1, e2). Of course at least one of the expressions |
|
|
431 must be zero... |
|
|
432 |
|
|
433 * Is Matrix::fortran_vec() really necessary? |
|
2862
|
434 |
|
2330
|
435 * print_usage() should set error_state in most cases? |
|
|
436 |
|
|
437 * Add a command that works like bash's `builtin' command. |
|
|
438 |
|
3758
|
439 * Handle end-of-line comments correctly in parse trees for use with |
|
|
440 the type command. |
|
2330
|
441 |
|
|
442 * Clean up eye, eval, feval, keyboard, input, ones, zeros. |
|
|
443 |
|
|
444 * It would be nice to have an interactive debugger. |
|
|
445 |
|
2378
|
446 * Make whos report total memory used by variables (and functions?). |
|
|
447 |
|
2746
|
448 * Rewrite whos and the symbol_record_info class. Write a built-in |
|
|
449 function that gives all the basic information, then write who and |
|
|
450 whos as M-files. |
|
2439
|
451 |
|
3125
|
452 * Make whos work for structure elements: |
|
|
453 |
|
|
454 prot type rows cols name |
|
|
455 ==== ==== ==== ==== ==== |
|
4325
|
456 wd matrix m n struct.field |
|
3125
|
457 |
|
3249
|
458 * Allow who to return information as a list of strings. |
|
|
459 |
|
2799
|
460 * On systems that support matherr(), make it possible for users to |
|
|
461 enable the printing of warning messages. |
|
|
462 |
|
2862
|
463 * Make it possible to mark variables and functions as read-only. |
|
|
464 |
|
3060
|
465 * Provide a built-in function for applying a scalar function to an |
|
|
466 array. Be sure to note in the manual that this is not the |
|
|
467 preferred way to write a function that can handle vector/matrix |
|
|
468 arguments because there is a significant overhead for function |
|
|
469 calls. If you are really looking to make a function work for |
|
|
470 vector/matrix arguments and you want it to run fast, you should |
|
|
471 write it in terms of the existing vector/matrix operators as much |
|
|
472 as possible. |
|
|
473 |
|
3092
|
474 * Make it possible to write a function that gets a reference to a |
|
|
475 matrix in memory and change one or more elements without |
|
|
476 generating a second copy of the data. |
|
|
477 |
|
5228
|
478 * Use nanosleep instead of usleep if it is available? Apparently |
|
|
479 nanosleep is to be preferred over usleep on Solaris systems. |
|
|
480 |
|
2330
|
481 ------- |
|
|
482 History: |
|
|
483 ------- |
|
|
484 |
|
|
485 * Add an option to allow saving input from script files in the |
|
|
486 history list. |
|
|
487 |
|
3092
|
488 * The history command should accept two numeric arguments to |
|
|
489 indicate a range of history entries to display, save or read. |
|
|
490 |
|
2862
|
491 * Add an option to include information about the Octave session in |
|
|
492 the history list. Possibly a time/date stamp and the current |
|
|
493 Octave line number, appended as a comment (users should probably |
|
|
494 be able to control the format). |
|
|
495 |
|
5026
|
496 * Avoid writing the history file if the history list has not |
|
|
497 changed. |
|
|
498 |
|
|
499 * Avoid permission errors if the history file cannot be opened for |
|
|
500 writing. |
|
|
501 |
|
2330
|
502 * Fix history problems -- core dump if multiple processes are |
|
|
503 writing to the same history file? |
|
|
504 |
|
|
505 ------------------------------ |
|
|
506 Configuration and Installation: |
|
|
507 ------------------------------ |
|
|
508 |
|
2473
|
509 * Add an --enable-pathsearch option to configure to make it possible |
|
|
510 to configure and run without kpathsea. |
|
|
511 |
|
2330
|
512 * Makefile changes: |
|
|
513 -- eliminate for loops |
|
|
514 -- define shell commands or eliminate them |
|
|
515 -- verify distclean |
|
|
516 -- consolidate targets |
|
|
517 |
|
|
518 * Make it possible to configure so that installed binaries and |
|
|
519 shared libraries are stripped. |
|
|
520 |
|
3069
|
521 * Create a docs-only distribution? |
|
|
522 |
|
2330
|
523 ------------------------------ |
|
|
524 Documentation and On-Line Help: |
|
|
525 ------------------------------ |
|
|
526 |
|
|
527 * Document new features. |
|
|
528 -- history-search-{back,for}ward. |
|
|
529 -- Other stuff mentioned in the NEWS file. |
|
|
530 |
|
|
531 * Improve the Texinfo Documentation for the interpreter. It would |
|
|
532 be useful to have lots more examples, to not have so many forward |
|
|
533 references, and to not have very many simple lists of functions. |
|
|
534 |
|
|
535 * The docs should mention something about efficiency and that using |
|
|
536 array operations is almost always a good idea for speed. |
|
|
537 |
|
|
538 * Texinfo documentation for the C++ classes. |
|
|
539 |
|
|
540 * Support multiple info files, perhaps allowing one or more in each |
|
|
541 directory in the LOADPATH, so that local collections of M-files |
|
|
542 could be documented with Info. |
|
|
543 |
|
|
544 * Improve help messages for operators and keywords in help.cc. |
|
|
545 |
|
|
546 * Make index entries more consistent to improve behavior of `help -i'. |
|
|
547 |
|
|
548 * Make `help -i' try to find a whole word match first. |
|
|
549 |
|
|
550 * Allow help for local additions to be accessible with help -i. |
|
|
551 |
|
3130
|
552 * Clean up help stuff. |
|
|
553 |
|
2330
|
554 * Demo files. |
|
|
555 |
|
|
556 * As the number of m-files with octave grows perhaps a 'Contents.m' |
|
|
557 file for each toolbox (directory) would be appropriate so one |
|
|
558 knows exactly what functions are in a toolbox with a quick look. |
|
|
559 It would be best to generate information for each function directly |
|
|
560 from the M-files, so that the information doesn't have to be |
|
|
561 duplicated, and will remain current if the M-files change. It |
|
|
562 would also be best to do as much of this as possible in an M-file, |
|
|
563 though I wouldn't mind adding some basic support for listing the |
|
|
564 names of all the directories in the LOADPATH, and the names of all |
|
|
565 the M-files in a given directory if that is needed. |
|
|
566 |
|
2787
|
567 Also make it possible to recursively search for Contents files: |
|
|
568 |
|
|
569 help dir -- Contents from dir |
|
|
570 help dir// -- Contents from dir and all its subdirectories |
|
|
571 help dir1/dir2 -- Contents from dir2 which is under dir1 |
|
|
572 |
|
2330
|
573 * Some sort of blurb (2-3 pages) describing Octave in a reasonably |
|
|
574 coherent way, where to get it etc., perhaps formatted pretty, |
|
|
575 i.e. not just text. Maybe start with the latest Announce file. |
|
|
576 |
|
|
577 ----- |
|
|
578 Tests: |
|
|
579 ----- |
|
|
580 |
|
|
581 * Improved set of tests: |
|
|
582 |
|
|
583 -- Tests for various functions. Would be nice to have a test file |
|
|
584 corresponding to every function. |
|
|
585 |
|
|
586 -- Tests for element by element operators: |
|
|
587 + - .* ./ .\ .^ | & < <= == >= > != ! |
|
|
588 |
|
|
589 -- Tests for boolean operators: && || |
|
|
590 |
|
|
591 -- Tests for other operators: * / \ ' .' |
|
|
592 |
|
|
593 -- Tests from bug reports. |
|
|
594 |
|
|
595 -- Tests for indexed assignment. Need to consider the following: |
|
|
596 o fortran-style indexing |
|
|
597 o zero-one indexing |
|
|
598 o assignment of empty matrix as well as values |
|
|
599 o resizing |
|
|
600 |
|
|
601 * Tests for all internal functions. |
|
|
602 |
|
|
603 ----------- |
|
|
604 Programming: |
|
|
605 ----------- |
|
|
606 |
|
2475
|
607 * Better error messages for missing operators? |
|
|
608 |
|
|
609 * Eliminate duplicate enums in pt-exp.cc, pt-const.cc, and ov.cc. |
|
|
610 |
|
|
611 * Handle octave_print_internal() stuff at the liboctave level. Then |
|
|
612 the octave_value classes could just call on the print() methods |
|
|
613 for the underlying classes. |
|
|
614 |
|
|
615 * As much as possible, eliminate explicit checks for the types of |
|
|
616 octave_value objects so that user-defined types will automatically |
|
|
617 do the right thing in more cases. |
|
|
618 |
|
2330
|
619 * Only include config.h in files that actually need it, instead of |
|
|
620 including it in every .cc file. Unfortunately, this might not be |
|
|
621 so easy to figure out. |
|
|
622 |
|
|
623 * GNU coding standards: |
|
|
624 |
|
|
625 -- Add a `Makefile' target to the Makefiles. |
|
|
626 -- Comments on #else and #endif preprocessor commands. |
|
|
627 -- Change error message format to match standards everywhere. |
|
|
628 |
|
|
629 * Use STL stuff instead of libg++ lists, maps, and stacks. |
|
|
630 |
|
|
631 * Eliminate more global variables. |
|
|
632 |
|
|
633 * Move procstream to liboctave. |
|
|
634 |
|
|
635 * Use references and classes in more places. |
|
|
636 |
|
|
637 * Share more code among the various *_options functions. |
|
|
638 |
|
|
639 ------------- |
|
|
640 Miscellaneous: |
|
|
641 ------------- |
|
|
642 |
|
|
643 * Implement some functions for interprocess communication: bind, |
|
|
644 accept, connect, gethostbyname, etc. |
|
|
645 |
|
2454
|
646 * The installation process should also install octave.el. This |
|
|
647 needs to detect the appropriate Emacs binary to use to |
|
|
648 byte-compile the .el file. Following GNU Emacs philosophy, |
|
|
649 installation would be into $(prefix)/share/emacs/site-lisp by |
|
|
650 default, but it should be selectable. |
|
|
651 |
|
2330
|
652 * The ability to transparently handle very large files: |
|
|
653 |
|
|
654 Juhana K Kouhia <kouhia@nic.funet.fi> wrote: |
|
|
655 |
|
|
656 If I have a one-dimensional signal data with the size 400 |
|
|
657 Mbytes, then what are my choices to operate with it: |
|
|
658 |
|
|
659 * I have to split the data |
|
|
660 * Octave has a virtual memory on its own and I don't have to |
|
|
661 worry about the splitting. |
|
|
662 |
|
|
663 If I split the data, then my easily programmed processing |
|
|
664 programs will become hard to program. |
|
|
665 |
|
|
666 If possible, I would like to have the virtual memory system in |
|
|
667 Octave i.e. the all big files, the user see as one big array or |
|
|
668 such. There could be several user selectable models to do the |
|
|
669 virtual memory depending on what kind of data the user have (1d, |
|
|
670 2d) and in what order they are processed (stream or random |
|
|
671 access). |
|
|
672 |
|
|
673 Perhaps this can be done entirely with a library of M-files. |
|
|
674 |
|
3136
|
675 * An interface to gdb. |
|
|
676 |
|
|
677 Michael Smolsky <fnsiguc@weizmann.weizmann.ac.il> wrote: |
|
|
678 |
|
|
679 I was thinking about a tool, which could be very useful for me |
|
|
680 in my numerical simulation work. It is an interconnection |
|
|
681 between gdb and octave. We are often managing very large arrays |
|
|
682 of data in our fortran or c codes, which might be studied with |
|
|
683 the help of octave at the algorithm development stages. Assume |
|
|
684 you're coding, say, wave equation. And want to debug the |
|
|
685 code. It would be great to pick some array from the memory of |
|
|
686 the code you're develloping, fft it and see the image as a |
|
|
687 log-log plot of the spectral density. I'm facing similar |
|
|
688 problems now. To avoid high c-development cost, I develop in |
|
|
689 matlab/octave, and then rewrite into c. It might be so much |
|
|
690 easier, if I could off-load a c array right from the debugger |
|
|
691 into octave, study it, and, perhaps, change some [many] values |
|
|
692 with a convenient matlab/octave syntax, similar to |
|
|
693 a(:,50:250)=zeros(100,200), and then store it back into the |
|
|
694 memory of my c code. |
|
|
695 |
|
2789
|
696 * Add a definition to lgrind so that it supports Octave. |
|
|
697 (See http://www.tex.ac.uk/tex-archive/support/lgrind/ for more |
|
|
698 information about lgrind.) |
|
|
699 |
|
2330
|
700 ------ |
|
|
701 Always: |
|
|
702 ------ |
|
|
703 |
|
|
704 * Squash bugs. |
|
|
705 |
|
|
706 --30-- |
|
3162
|
707 </pre> |
|
|
708 </html> |
