« first day (824 days earlier)      last day (711 days later) » 

 
2 hours later…
3:27 AM
@ngn I think there's a small usability problem with online ngn/k interpreter. If I accidentally invoke an infinite loop, I can't recover my source code because refreshing the tab will try running the code immediately (and get unresponsive again)
(I ended up opening a clean interpreter in a separate tab and feeding the original hash into console.log(p0("hash")) so it is technically recoverable, but anyway)
 
When I download the k9 version labeled 06.05 from shakti.com and then run the resulting mi2.0 binary, it says: mi 2021.06.07 2 16 (c)shakti 2.0. Also, the 06.07 version fixes the with !5 I reported the other day.
I notified tech@shakti.com.
 
 
2 hours later…
ngn
5:52 AM
@Bubbler i would say it's a train - a sequence of nouns and verbs ending with a verb. i think dzaima wants to use that word only for j-style trains.
in pre-shakti dialects, all functions had fixed arity. for a train, the arity of the last "carriage" determines the arity of the whole train, so yes: */ # is a dyad. to make it monadic, one would have to use #: (i.e. monadic #) explicity as the last carriage
@dzaima k doesn't have schizos. / is always an adverb.
 
@ngn Thanks for clarification
 
ngn
6:27 AM
@Bubbler i changed it so urls ending with a "-" aren't run automatically. now when you press "eval" or ctrl-enter, the url is initially given a "-", and only after the program finishes it is changed to the usual auto-running url
 
Nice :)
 
 
5 hours later…
12:25 PM
@ngn I know it isn't, my confusion was about the default arity of */#
 
1:18 PM
@Bubbler playing around with it a bit, you can replace (+/'x*\:)/ with (+/x*)'/
 
 
3 hours later…
4:01 PM
in k6 */# has arity 2. you have to force the monadic case with */#:
in k9 all verbs (and also compositions) are always indifferent. the arity is fixed at call time. sth like #: as a verb does not exist in k9.
 
5:00 PM
@ktye I think the thing in question is more oK-specific, e.g. the varying behavior of these
 
 
6 hours later…
11:14 PM
@coltim Thanks! Looks like it's multiplying x on the right side instead of the left side.
 

« first day (824 days earlier)      last day (711 days later) »