>>9
can you tersely define for a standard how this third generic gets optimized at a lower and more abstract level where having vectors and improper lists defined is moot
otherwise it doesnt belong in the standard and its something you can already do with scheme
i agree the standard has too many vector bits scheme isnt a shining example of terseness but it departs greatly from the common lipth goop slide into a sink
im waiting for another apl programmer to make an argument but since you understand proper etiquette here
scheme allows some or all if you wish imo macros just fit the case forms of apls shortening while most lipth implementations omit even supporting λ by default
sure you can argue about unicode but some modern apl doesnt
and i will say both of these arent real arguments you can even use a emacs mode for translating long goop into terse symbols locally
Terseness is only good up to the point where it remains obvious what something is
isnt the extreme what cniles broken vocabulary believes terseness is
incomphrenciable goop isnt terseness the word implies theres still a concisely defined subject
Of speech or style: brief, concise, to the point.
Synonyms: concise, succinct
even better it comes from a latin word tersus
clean, neat, rubbed or wiped (off), cleansed, having been cleansed
pure, correct, nice, terse, spruce, neat
is errccwrkprtpwo() any of those you already know the answer
now i will say r7rs-tiny has-a-few-goop-procedures but some of them are justified
call/cc this is cnile i need to know cc means current continuation and / with by looking at it first glance not because i have background information from studying call/cc
instead the emacs mode is justified here as the local programmer i know what symbols i consider equivalent to call-with-current-continuation
sure another solution is a proper (help) but this is something that should already be there especially for standard procedures and now when someone else goes to read it they have to manually look up call/cc
it can be acceptable when the concept needs paragraphs to describe to someone with baseline knowledge in that case call/cc should scream / is with and cc is current continuation but there is no consistent nomenclature where / acts as a combination in r7rs-tiny unlike -> which is even strictly defined to return another type of object
the nice thing about apl is once you understand the graphemes enough and the bases they form things like quadwords its universality accepted how those symbols get used so you arent writing split-at-obtuse-point-five because there is no need and it removes the broken need for verbosity in procedure names
i recommend a glossary using logical graphemes that works with proper lisp environments over split-at-vector-point-five that way someone reading can just hover or something else configured and see the verbose procedure name until they inherit the personal nomenclature the author has for symbols