2022-10-12 11:19:20 <KipIngram   > 2/ should be much faster, because it almost certainly just does a right bit shift.
2022-10-12 11:20:14 <KipIngram   > / is slower even than * on most systems, by quite a margin.  There's a bit of slick trickery in Hacker's Delight about using magic number tricks to "divide by multiplying."
2022-10-12 11:20:36 <KipIngram   > So if you happen to be dividing by a fixed known number, you can pull that out of your sleeve and buy some speed.
2022-10-12 11:21:01 <Friithian   > I had half a mind to do 2/ 2/ instead of 4 / and it was still much faster lol
2022-10-12 11:21:05 <Friithian   > but then that is harder to read
2022-10-12 11:21:25 <KipIngram   > You could do 2 >>
2022-10-12 11:21:53 <Friithian   > oh I did not know that was a thing
2022-10-12 11:21:56 <KipIngram   > Actually, though 2/ 2/ might be faster.
2022-10-12 11:22:11 <KipIngram   > Well, check  your system, but << and >> are usually shift operators.
2022-10-12 11:22:17 <thrig       > smart compilers can probably do a lot of that work for you, or anyways create hard to debug problems
2022-10-12 11:22:41 <KipIngram   > The industry depends on hard to debug problems.
2022-10-12 11:22:45 <Friithian   > gforth doesn't seem to have it, heck
2022-10-12 11:22:57 <KipIngram   > Am I totally misremembering?
2022-10-12 11:23:30 <KipIngram   > Maybe I've just added it to mine for so long that I forgot it wasn't standard.
2022-10-12 11:24:11 <KipIngram   > Surely the standard offers shift words.
2022-10-12 11:24:21 <KipIngram   > But yeah - it's not in gforth.  :-(
2022-10-12 11:24:35 <KipIngram   > I defer to those more familiar with "community products" than I am.
2022-10-12 11:24:37 <thrig       > 6.1.2162 RSHIFT
2022-10-12 11:24:51 <Friithian   > rshift
2022-10-12 11:25:36 <KipIngram   > Yeah, rshift and lshift.
2022-10-12 11:25:39 <thrig       > luckily I have a tool to grep the ANS spec with
2022-10-12 11:25:47 <KipIngram   > Ok.  I do kind of have a fetish for "terse symbology."
2022-10-12 11:26:21 <KipIngram   > In C it's << and >>
2022-10-12 11:26:41 <KipIngram   > So I felt perfectly comfortable choosing those names in my Forth.
2022-10-12 11:26:46 <thrig       > if you don't mind being asked what U+{DRUNK DRAGON WITH DOWNWARDS WIGGLY LINE} means in your code
2022-10-12 11:27:15 <KipIngram   > :-)
2022-10-12 11:27:30 <KipIngram   > Well, in my eyes << and >> are clearly superior, but I guess it's a matter of taste.
2022-10-12 11:28:44 <KipIngram   > I got on a multi-week long APL kick seven or eight months ago, and had quite a bit of debate with a friend I chat with on Discord about "terse" vs. "wordy."  He had a strong preference for seeing a lot of words that he could interpret as, well... WORDS.
2022-10-12 11:28:58 <KipIngram   > APL was definitely not to his taste, but I was rather enamored by it.
2022-10-12 11:30:08 <thrig       > WE COMEFROM COBOL LEADER TAKE TO US
2022-10-12 12:29:45 <Friithian   > I like << and >> much better, but I also like c++ so *shrug*
2022-10-12 12:47:47 <crcx        > I use shift-left and shift-right
2022-10-12 12:50:07 <Friithian   > shr
2022-10-12 12:57:37 <crcx        > I'm not bothered by long names :)
2022-10-12 12:59:31 <thrig       > least-negative-normalized-double-float
2022-10-12 12:59:49 <Friithian   > shr is the x68 ASM instruction, I think
2022-10-12 13:00:18 <thrig       > meanwhile the longest thing from ANS is environment?<b>environment-query</b> which looks like a parsing problem
2022-10-12 13:07:53 <thrig       > ... or a typo in dpansf.htm, which means the longest word is reposition-file, so FORTH ain't got nothing on Common LISP for long words
2022-10-12 13:20:05 <crcx        > least-negative-normalized-double-float is longer than I'd like. My longest word in my small system is under 15 characters, and in my larger system is 24 characters. I average 8 characters per name.
2022-10-12 13:21:50 <thrig       > presumably the lispers use emacs which presumably could complete long functions for you?
2022-10-12 13:27:00 <crcx        > maybe; I've not looked at emacs in many years
2022-10-12 13:59:37 <thrig       > Common LISP words be consistently longer! https://thrig.me/tmp/word-lengths.txt
2022-10-12 19:30:24 <KipIngram   > crcx: Long names do bother me, and I confess it's a somewhat irrational thing.  I mean, I have reasons, but there's more to it than just that.
2022-10-12 19:31:00 <KipIngram   > I try to write one line definitions, and the line length that started to set off alarm bells just kept getting shorter over the years.
2022-10-12 19:31:13 <KipIngram   > I don't like for my lines to get longer than 45-50 characters.
2022-10-12 19:31:40 <KipIngram   > I attempt to justify it by the idea that a short definition is easier to hold in my short term memory.
2022-10-12 19:32:38 <KipIngram   > For my numeric conversion word I wound up with about 25 or so 40-50 char definitions, all of the except one done with my little "temporary definition" widget.