|
From: <kin...@us...> - 2025-09-30 21:11:16
|
Revision: 7553
http://sourceforge.net/p/teem/code/7553
Author: kindlmann
Date: 2025-09-30 21:11:13 +0000 (Tue, 30 Sep 2025)
Log Message:
-----------
some long-standing hest annoyances have been addressed with the rewrite
Modified Paths:
--------------
teem/trunk/src/TODO.txt
teem/trunk/src/hest/TODO.txt
Modified: teem/trunk/src/TODO.txt
===================================================================
--- teem/trunk/src/TODO.txt 2025-09-30 20:57:42 UTC (rev 7552)
+++ teem/trunk/src/TODO.txt 2025-09-30 21:11:13 UTC (rev 7553)
@@ -1,11 +1,3 @@
-******* Figure out what is going on with parsing spaces in hest:
-this doesn't work:
- unu basinfo -i tmp.nrrd -kv space:=RGB "novalue:=0.3 0 0" -o tmp2.nrrd
-and instead it sees:
- !unu basinfo: kvpstring[0/2] = |space:=RGB|
- !unu basinfo: kvpstring[1/2] = |"novalue:=0.3|
-where the hell is the " coming from?
-
(Actually maybe ctypes is not important, now that the CFFI stuff is solid with exult.py)
revisit ctypes with new ctypeslib2:
https://github.com/trolldbois/ctypeslib
@@ -82,22 +74,6 @@
to a great many functions (or else it itself would be a global),
and then how do you know which functions should take it?
-hest:
-* consider renaming hestParmFree --> hestParmNix
-* air/hest: remove the airType* enum. The following sort of code looks
-correct but is completely wrong
- if (nrrdAlloc(nout, airTypeFloat, 3, size[0], size[1], size[2])) { ...
-because "airTypeFloat" is there instead of "nrrdTypeFloat". All
-things airType were created for the sake of hest. Instead of taking an
-airType enum value for hestOptAdd, hestOptAdd can take a string
-(e.g. "uchar", "float", "enum", "callback" for airTypeOther).
-* There's no such thing as a truly optional parameter: data is needed
-for all options, whether it comes from the default string or the
-command line, and its an error if no data is found. Not having
-optional parameters is why things like "unu make" learn centerings via
-strings: the string can be given or not, and if its given, then the
-information is used.
-
biff:
* biffMove(destKey, err, srcKey) --> biffMove(destKey, srcKey, err)
so that it matches biffMovef
Modified: teem/trunk/src/hest/TODO.txt
===================================================================
--- teem/trunk/src/hest/TODO.txt 2025-09-30 20:57:42 UTC (rev 7552)
+++ teem/trunk/src/hest/TODO.txt 2025-09-30 21:11:13 UTC (rev 7553)
@@ -5,6 +5,3 @@
currently the "input nrrd" option to unu comes last as a way of allowing
hest to do error checking on all other (more error prone) options. But
it would be nice to indicate a parsing order seperate from the option order.
-
-
-??? What is relationship between parseHest.c/whichCase() and hestOpt.alloc ???
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|