dockimbel on money
FIX: truncates integral part of… (compare)
dockimbel on money
FIX: "+$.1" literal causes runt… (compare)
x: 10 | append series x....
|basically means noop
series <- append 10might be even more clearly understandable, though more difficult to read
ixcor <- copy/part 1 <- enbase 2
myword//contextword? Then, if the element is a function you could write
myword//contextword mywordto execute a "method" of the word in that context on the word value or just get a value of another word in that context. I have called it "reverse object" where you retain
set-word/get-wordnotation but you also have object functionality.
.<-|pipe/thread/forward model...a dialected func is the way to experiment IMO. They aren't a "win", just different. We should encourage writing readable code, and terse ops and dialects may be more readable in some cases. Just keep in mind that Redbol langs are very much word oriented by design. In some domains, those words may be short symbols.
method(object)). I'd still just write a Forth dialect, but I have to conclude that's just because I'm weird.
Forth is a bit more than tacit programming and stack shuffling though. I would be extremely interested to see how concatenative and homoiconic properties can be aligned (see e.g. Om language) and what the Joy (pun intended) of concatenative combinators can bring to the HOF table (@giesse you're not the only weirdo here).
Thinking aloud, one can define an operator that accepts a data stack (
block!) and a program (also a
block!) which then can be combined together; that would be weaving (two threads), and
.-style would be threading (evaluator's IP needle thru the eyelet of
.example which I had submitted (which I think it seems this discussion is still going on!) was my attempt to replicate a similar behavior. When working withthose anguages I found it very readable since it allowed me to express a sequence of steps or transformations from left to right, or top down. As an alternative to the
->was also nice.
source modreturns the same incorrect implementation. Is there a branch where it isn't busted?
a [number! char! pair! tuple! vector! time!]is a lie