-'let :=' for immediate evaluation in assignment. Does this work
-for included files?
+'let :=' for immediate evaluation in assignment. Does this work for
+included files? Also ?= to only override if not already defined.
Default parameters, ie:
goal foo (name, release = true) = ...
You might only allow defaults to be added to the end, or you
might allow goals to be called with labelled parameters.
-Fix: You must use 'all ()' on the command line.
+Deleting target files if goals is interrupted, but only if the
+timestamp changes (what about non-*files?). Also: atomic code. This
+will delete the target if the code doesn't run to completion. (make
+doesn't do this, but probably it should).
-"Quiet" code. Generally {CODE} sections in user files should be
-echos, and those in stdlib should run silently (except if debugging).
-Maybe we should have a quiet keyword to indicate this?
+Conditional sections (same as "ifeq" etc in make).
+
+Let within functions and goals, eg:
+ function foo () =
+ let temp = "%bar%baz";
+ { .... }
+Unclear if this would be helpful or not.
+
+Make re-execs itself if the Makefile (or any include) changes, and
+goals should do something similar. See:
+https://www.gnu.org/software/make/manual/html_node/Remaking-Makefiles.html
+
+Code should be an expression, eg this ought to work:
+let foo = { echo "hello" }
+and/or anonymous functions:
+let foo = function (arg) { ... }
+
+Infinite loop when you have this goal:
+goal pod2man (page, section) = "docs/%page.%section" : "docs/%page.pod" { ... }
+This is caused by %section matching "pod" so the rule is called
+again, even if the local file docs/%page.pod actually exists.
+
+Implement make-like “eval” function (similar to include directive,
+but it evaluates the output of a function as Goalfile syntax).
+
+Implement make-like “origin” function. This is easy but it requires
+us to track to the origin of definitions which we do not do at
+the moment.
\ No newline at end of file
git.annexia.org / goals.git / blobdiff