00:00:00 --- log: started forth/21.01.17 00:03:45 --- quit: gravicappa (Ping timeout: 256 seconds) 00:04:25 --- join: gravicappa joined #forth 00:04:26 --- quit: dave0 (Ping timeout: 256 seconds) 00:27:25 --- quit: _whitelogger (Remote host closed the connection) 00:30:21 --- join: _whitelogger joined #forth 00:46:00 --- quit: proteus-guy (Ping timeout: 264 seconds) 02:29:24 --- quit: pointfree (Quit: Connection closed for inactivity) 06:00:26 --- join: hosewiejacke joined #forth 06:12:18 Does anyone here have experience with 4 byte name fields, i.e. only 3 characters and length are stored, and how much of a pain is it? 06:14:09 To do the same thing would it be totally mad to store a 32-bit hash instead? 06:19:34 --- quit: hosewiejacke (Ping timeout: 256 seconds) 06:20:51 it has the advantage of using more bits of these 4 bytes. 3 characters means that ~6 bits go unused (and the length byte is also very unevenly distributed), a problem you likely wouldn't have with a hash function. 07:40:07 seems like it would be harder for the user though if two completely different words coincidently got the same hash and it inserted the wrong one 08:19:55 MrMobius: I think you need to have a redefinition warning, and try and figure it out based on SEE 08:20:26 But the chances of a collision are e.g. extremely low with a decent 31-bit hash and less than 10000 definitions 08:21:09 In the choice between the 1-byte length + 3-byte prefix encoding and hash encoding, you're wayyyy less likely to get collisions with the hash 08:26:23 veltas, so if you tried to make a new word that conflicted with an existing hash, it would tell you to use a different name for the new word? 08:27:12 I think for an interactive forth it would give a warning, like just print " is a redefinition" or something 08:27:15 i guess you couldnt tell the difference between redefinitions and different words with the same hash 08:27:31 Nope 08:27:50 you must be running on an ultra tiny system :) 08:27:55 If you have the source handy and use SEE on the word you were trying to define, you could figure it out 08:28:25 hmm, if you had defined the word earlier the same day 08:29:02 not if you hadnt defined it or its built in or its been a year since you looked at it 08:29:04 Well the current system I'm working on has 48KB for code+data 08:29:59 If you did "SEE " and saw ": DROP ;" or something you'd be a bit out of luck lol 08:30:06 Well you could figure it out with FIND 08:30:24 It's a constraint but you'd be extremely unlucky to get a collision 09:31:01 --- quit: gravicappa (Ping timeout: 246 seconds) 09:32:07 --- join: gravicappa joined #forth 12:29:59 --- quit: gravicappa (Ping timeout: 264 seconds) 13:34:32 --- join: hosewiejacke joined #forth 13:38:44 --- quit: hosewiejacke (Ping timeout: 256 seconds) 14:16:53 --- quit: cantstanya (*.net *.split) 14:30:03 --- join: cantstanya joined #forth 15:34:47 --- quit: lispmacs[work] (Ping timeout: 240 seconds) 18:17:23 --- join: boru` joined #forth 18:17:26 --- quit: boru (Disconnected by services) 18:17:28 --- nick: boru` -> boru 18:19:36 --- quit: irsol (Ping timeout: 246 seconds) 18:19:47 --- quit: actuallybatman (Ping timeout: 264 seconds) 18:20:05 --- join: actuallybatman joined #forth 18:23:59 --- quit: spoofer (Ping timeout: 264 seconds) 18:26:18 --- join: spoofer joined #forth 18:28:32 --- join: irsol joined #forth 18:31:11 --- quit: spoofer (Ping timeout: 264 seconds) 18:31:21 --- join: spoofer joined #forth 18:40:38 --- join: boru` joined #forth 18:40:41 --- quit: boru (Disconnected by services) 18:40:43 --- nick: boru` -> boru 19:22:42 --- quit: irsol (Ping timeout: 256 seconds) 19:23:40 --- join: jedb_ joined #forth 19:23:50 --- quit: jedb (Ping timeout: 260 seconds) 19:23:56 --- nick: jedb_ -> jedb 19:24:14 --- join: irsol joined #forth 19:54:31 --- join: charlie joined #forth 19:54:50 --- quit: the_cuckoo (Ping timeout: 256 seconds) 19:54:54 --- nick: charlie -> Guest68228 20:30:03 --- quit: Guest68228 (Ping timeout: 272 seconds) 20:31:43 --- join: proteus-guy joined #forth 20:42:18 --- join: hosewiejacke joined #forth 20:42:51 --- quit: hosewiejacke (Remote host closed the connection) 20:43:05 --- join: Guest68228 joined #forth 20:43:06 --- join: hosewiejacke joined #forth 20:59:07 --- quit: sts-q (Ping timeout: 246 seconds) 21:13:25 --- join: sts-q joined #forth 21:54:48 --- join: gravicappa joined #forth 22:17:29 --- quit: rixard_ (Read error: Connection reset by peer) 22:18:18 --- join: rixard joined #forth 23:41:51 --- quit: lispmacs (Remote host closed the connection) 23:45:31 --- join: jedb_ joined #forth 23:45:50 --- quit: jedb (Read error: Connection reset by peer) 23:50:09 --- nick: jedb_ -> jedb 23:59:59 --- log: ended forth/21.01.17