00:00:00 --- log: started forth/20.11.30 00:35:12 --- join: xek joined #forth 00:38:31 lispmacs: I think usually they have their own dictionaries too 00:38:47 There is a system dictionary and user dictionaries, or something like that 00:39:07 Download PolyForth, read manual 01:15:53 --- quit: gravicappa (Ping timeout: 256 seconds) 01:20:27 --- join: gravicappa joined #forth 02:01:51 --- join: dave0 joined #forth 02:17:58 --- quit: dave0 (Read error: Connection reset by peer) 02:23:12 --- join: dave0 joined #forth 02:43:18 --- join: Vedran joined #forth 04:26:15 --- join: Gromboli joined #forth 04:37:20 --- quit: hosewiejacke (Ping timeout: 265 seconds) 05:04:52 --- join: hosewiejacke joined #forth 06:02:12 --- quit: dave0 (Quit: dave's not here) 08:53:49 --- quit: gravicappa (Ping timeout: 256 seconds) 09:14:23 --- quit: hosewiejacke (Ping timeout: 264 seconds) 09:21:22 --- join: hosewiejacke joined #forth 09:24:39 --- join: Zarutian_HTC joined #forth 09:30:43 --- quit: hosewiejacke (Ping timeout: 265 seconds) 10:02:11 --- join: gravicappa joined #forth 10:08:18 --- quit: Zarutian_HTC (Ping timeout: 240 seconds) 10:24:00 --- join: Zarutian_HTC joined #forth 11:00:01 --- quit: Zarutian_HTC (Remote host closed the connection) 11:14:04 --- join: hosewiejacke joined #forth 11:20:38 --- quit: gravicappa (Ping timeout: 260 seconds) 11:32:22 --- quit: hosewiejacke (Ping timeout: 272 seconds) 11:48:13 --- join: openbsd535 joined #forth 12:08:46 --- quit: openbsd535 (Quit: http://www.kiwiirc.com/ - A hand crafted IRC client) 12:09:51 --- join: openbsd535 joined #forth 12:10:30 --- quit: openbsd535 (Client Quit) 13:55:50 --- join: Zarutian_HTC joined #forth 14:23:51 --- join: dave0 joined #forth 14:26:22 --- quit: xek (Ping timeout: 256 seconds) 14:50:09 * neuro_sys is reading POL (Problem Oriented Language), and enjoying it. 15:07:16 --- quit: Gromboli (Read error: Connection reset by peer) 15:07:16 --- quit: dave0 (Read error: Connection reset by peer) 15:07:17 --- join: Gromboli joined #forth 15:10:14 --- join: dave0 joined #forth 15:10:16 Chuck Moore is probably right about comments 15:10:55 Good code does speak for itself 15:14:08 Yeah, more so in high level languages. But when writing assembly code, I comment out groups of instructions that mean something distinct (which can be routines or macros). 15:15:20 Although if they're repeated often and are idiomatic, then I don't. Like in Z80: ld a, (hl) / inc hl / ld h, (hl) / ld l, a 15:16:59 Sparse comments are helpful in assembly, heavy comments are hard to maintain and not useful documentation in assembly or anywhere 15:38:54 depends on what the comments are used for 15:39:13 if they document the why the sure 15:39:48 but if they just restate the same as the code they are worse than useless 15:44:58 Then they're no more than tautology 15:45:13 "Where Forth programmers come from is as mysterious and as much a subject for debate as was in the previous century the source of Nile." 15:49:19 but usually I use comments to stick in url links to reference material for the particular problem the code is written to solve 15:58:25 --- join: jedb_ joined #forth 16:00:28 --- quit: dave0 (Quit: dave's not here) 16:01:06 --- quit: jedb (Ping timeout: 260 seconds) 16:08:31 "Rather than link each entry to its physical predecessor, link it to a predecessor in one of a number of chains. Scramble the word to determine which chain it belongs in, both when you enter it and when you search for it" 16:08:42 Does Chuck Moore talk about using a hash table here? 16:09:49 --- join: jedb__ joined #forth 16:10:20 assume nothing. How Chuck describes stuff might not have exact translation in usual comp sci terms 16:12:56 --- quit: jedb_ (Ping timeout: 272 seconds) 16:15:34 many people are too prone to do what I call noospheric snap-to 16:15:53 --- nick: jedb__ -> jedb 16:18:55 that is, they see a description of a concept and they think it is symonymus with a closely related but distinct concept they already know 16:19:04 I see what you mean 16:21:00 what Chuck is describing might be something new or at least something that overlapps something well known 16:21:06 "noospheric snap-to" is a nice way to put it 16:22:44 but looking at what he describes can be a source of inspiration of a diffrent view on these things 16:38:30 "It is a futile exercise to attempt to establish a universal set of nouns. Compiler languages have repeatedly stumbled by not providing enough, and no matter how many they provide, someone will want one more." 16:38:45 It makes me think of the latest C++ features and proposals. 17:44:25 --- quit: jimt[m] (Ping timeout: 246 seconds) 17:50:49 --- join: jimt[m] joined #forth 17:55:40 --- quit: Zarutian_HTC (Remote host closed the connection) 18:19:15 --- join: boru` joined #forth 18:19:17 --- quit: boru (Disconnected by services) 18:19:20 --- nick: boru` -> boru 18:38:40 --- quit: Gromboli (Read error: Connection reset by peer) 20:36:12 --- join: gravicappa joined #forth 20:50:51 --- quit: sts-q (Ping timeout: 272 seconds) 21:03:24 --- join: sts-q joined #forth 21:17:43 --- join: hosewiejacke joined #forth 23:59:59 --- log: ended forth/20.11.30