From eff5c9c919779d262940dd7a8ec03a392da45113 Mon Sep 17 00:00:00 2001 From: Emil Williams Date: Sat, 2 Mar 2024 07:48:50 +0000 Subject: [PATCH] TODO! Moreso notes than actual future plans --- TODO | 31 +++++++++++++++++++++++++++++++ 1 file changed, 31 insertions(+) create mode 100644 TODO diff --git a/TODO b/TODO new file mode 100644 index 0000000..03adc34 --- /dev/null +++ b/TODO @@ -0,0 +1,31 @@ +Select among the @BAKEs in a file? +This could be user-useful but would require an overhaul of the options. + +Specify the shell environment somehow? +Could be nice, could be easy to implement with some different starter +command, such as @BAKE_ENV /bin/sh [command ...], but the power of +regular old /bin/sh alone should be enough for everything. Calling +a script is perfectly practical considering the rooting facilities. +Use Make or a script, this is nearing overkill. + +Enviromental variables? +No idea how the support is currently, should be fine. Anything more is +overkill, use Make if you need ?= and $(XXX). + +Longer @EMBEDDED_BAKE handle? +Possibly a good idea for large binary files, but I would rather just +write the "Select among @BAKEs" feature than cheap out with an additional +handle. Besides, this is only useful for a gimick autonomous compile +feature. If I decided to write the @BAKE_ENV feature, I'd probably need +to also include a @EMBEDDED_BAKE_ENV which is a little ridiculous. +This will at best make me consider writing/using hashmaps, which would +be a techinical improvement, but definitely is overkill. + +More Macros? +Luckily, with the rewrite to expand, this would be very easy to add. +But I don't know of any that wouldn't be overkill. If I ever think of +any that would be substantially useful, I might add them. + +Kill globals. +I'd need to first isolate them into bake_expand, which is a bit of a +pain but a thing I'll definitely do.