We've applied to an Ivy League in North America for starters. Of course, that should also mean, any interested peers in the immediate neighbourhood with similar interests, please get in touch---because u can!

In the current (1.0.3)[0] TEA language implementation [1] and design [2], interactivity wasn't yet properly implemented. In particular, only two methods of passing input into a TEA program were possible;
1. For the TTTT TEA interpreter environment [1], the user gets to specify initial input to the target TEA Program using the "-i" command line parameter at invocation time.
2. Or, within the source code of the TEA program itself, input is set (writing the AI) via the i: command for example, but never to allow such setting of the input, directly from whatever the user of the running program wants to specify or enter while the program is actively running.

This last point in the list above, is solvable readily, if we allow to alter or rather revise the TEA standard [2], by adjusting the command "i:" from being inert when invoked without parameters, to being the standard way to prompt for user input at runtime. Essentially, in the following example TEA program:

i!:B
x:
v:vD
i:
v:vN
G*:--:vD:vN

would return "BB--Velma", if the 4th instruction in that program, "i:" --- which would block processing until the user provides some input at runtime, has the value "Velma" specified by the user. Otherwise would return whatever the user provides at runtime, prefixed by the string "BB--".

## Introducing Interactivity into TEA
REFS:

0. https://github.com/mcnemesis/cli_tttt/releases/tag/tttt-1.0.3

1. https://github.com/mcnemesis/cli_tttt

2. https://www.academia.edu/122871672/TEA_TAZ_Transforming_Executable_Alphabet_A_to_Z_COMMAND_SPACE_SPECIFICATION

#tea #language #research #design #tea-applications #philosophy #plan #postdoc #bookplan #jwl #nuchwezi
#CREATED:Sept 06, 2024 09:21:25