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