00:03:51
##forth
<cleobuline>
i will do RESUME WORD tu resume a thread
15:28:27
##forth
<zozo>
helo
17:46:34
##forth
<ohnoitsnoah>
hey! anyone here?
17:46:47
##forth
<thrig>
nope
17:46:53
##forth
<ohnoitsnoah>
shame
17:47:01
##forth
<thrig>
yeah I know
17:57:56
##forth
<lispmacs[work]>
I'm not here
18:51:13
##forth
<veltas>
thrig: Okay I like vim a bit less after having to check its source recently
18:51:53
##forth
<veltas>
Looking for a bug, although it wasn't the culprit
19:01:27
##forth
<xentrac>
heh
19:01:42
##forth
<xentrac>
you prefer your source code files to be shorter than printed books?
19:10:54
##forth
<thrig>
vim has more code in header files than vi does in total
19:46:51
##forth
<cleobuline>
mforth: : test DUP
19:47:00
##forth
<cleobuline>
mforth: DUP
19:47:13
##forth
<cleobuline>
mforth: * * ;
19:47:32
##forth
<cleobuline>
mforth: 3 test .
19:47:32
##forth
<mforth>
27
19:51:50
##forth
<nmz>
what's a byte?
19:52:31
##forth
<nmz>
yall deal with weird machines, I recently learned that a byte was the smallest addressable value, so, then, it changes? its not always 8
19:52:44
##forth
<xentrac>
not always addressable, no
19:53:15
##forth
<xentrac>
lots of word-oriented machines had bytes of 6-9 bits within a word
19:53:34
##forth
<nmz>
but it seems that a byte now means 8bits, not smallest addressable value, so then, what should that be called
19:53:43
##forth
<xentrac>
"octet"
19:53:48
##forth
<nmz>
I really need a dictionary because its driving me insane
19:54:16
##forth
<xentrac>
or do you mean what should the smallest addressable value be called?
19:54:24
##forth
<nmz>
I looked around, and then a "word" is 16 in x86 and nothing else, really, there is no standardization and I don't even know what anything means anymore
19:54:33
##forth
<xentrac>
historically it was "memory word"
19:54:52
##forth
* nmz is learning
19:55:32
##forth
<xentrac>
words were also 16 bits in DG NOVA, PDP-11, MSP430, TMS9900, Tandem, Xerox Alto, and I think 65816
19:56:04
##forth
<xentrac>
of those, some but not all had byte-addressable memory
19:56:21
##forth
<xentrac>
Stretch and B5000 had bit-addressable memory IIRC
19:57:04
##forth
<xentrac>
you could go with "address unit" if you want to avoid "word", as you probably should
19:58:57
##forth
<xentrac>
normally a "word" is the size of an arithmetic operand, but old decimal computers (for business accounting) often had arbitrary-precision arithmetic and digit-addressable memory
20:37:47
##forth
<MrMobius>
you can just call them bytes. no one in actual practice would say byte and mean anything other than 8 bits without clarifying
20:38:18
##forth
<MrMobius>
even if C doesn't always mean 8 bits in the documentation
21:06:16
##forth
<nmz>
MrMobius: but that's my dislike
21:28:51
##forth
<xentrac>
nmz: you could make up a word
21:32:42
##forth
<xentrac>
$ ~/dev3/vecmarkov.py < ~/netbook-misc-devel/bible-pg10.txt | tr -cs A-Za-z '\n'| fgrep -vxf /usr/share/dict/words
21:34:05
##forth
<xentrac>
offers suggestions such as "ilt", "cousit", "warikin", "thad", "paupe", "wid", "tus", and "tond"
21:35:56
##forth
<xentrac>
I'd forgotten about the -x (--line-regexp) option
22:29:20
##forth
<nmz>
got it, bitsy
23:18:51
##forth
<veltas>
Interestingly I think it's unlawful for me to view that bible
23:20:44
##forth
<veltas>
In the UK it is protected by a perpetual royal prerogative, but in the rest of the world it's public domain
23:28:09
##forth
<veltas>
I've got a lawful copy though, of course