00:00:00 --- log: started forth/03.11.26 00:13:29 --- join: Serg_Penguin (~z@212.34.52.140) joined #forth 00:16:52 --- quit: Serg_Penguin (Client Quit) 00:23:40 --- join: ree (~jwm@ns.fasthost.net) joined #forth 02:44:49 --- quit: warp0x00 (Excess Flood) 02:45:43 --- join: warp0x00 (~warpzero@dsl.142.mt.onewest.net) joined #forth 04:47:26 --- join: haroldo (~haroldo@r200-40-217-251.adsl.anteldata.net.uy) joined #forth 04:51:44 --- quit: haroldo__ (Read error: 60 (Operation timed out)) 06:26:23 --- join: madgarden (~bughead@216.94.153.178) joined #forth 07:33:41 --- join: schihei (~schihei@pD9E5CD81.dip.t-dialin.net) joined #forth 09:08:23 --- quit: warp0x00 ("#") 10:12:27 --- join: warp0x00 (~warpzero@dsl.142.mt.onewest.net) joined #forth 10:55:29 --- quit: madgarden (Read error: 54 (Connection reset by peer)) 11:00:26 --- join: Sonarman (~matt@adsl-64-160-164-153.dsl.snfc21.pacbell.net) joined #forth 13:01:14 --- join: madgarden (~bughead@216.94.153.178) joined #forth 13:16:57 --- quit: schihei (Client Quit) 13:33:10 --- part: madgarden left #forth 14:50:29 --- join: jamc (dne@as3-6-8.asp.s.bonet.se) joined #forth 14:51:02 --- join: Robert__ (~snofs@c-7f5a71d5.17-1-64736c10.cust.bredbandsbolaget.se) joined #forth 14:51:51 --- quit: Robert (Read error: 104 (Connection reset by peer)) 14:52:37 --- nick: Robert__ -> Robert 15:53:25 --- quit: jamc ("WHO sees a BEACH BUNNY sobbing on a SHAG RUG?!") 16:49:22 --- join: haroldo_ (~haroldo@r200-40-167-88.adsl.anteldata.net.uy) joined #forth 16:52:55 --- quit: haroldo (Read error: 60 (Operation timed out)) 17:17:48 --- join: slava (~slava@CPE0080ad77a020-CM.cpe.net.cable.rogers.com) joined #forth 17:18:00 are there any good guides out there for factoring, and choosing good names for words? 17:20:25 I would *assume* you'd want words that concisely explained what they were doing, and adhered to whatever rules there are for words (i.e., no illegal characters or whatever) ... however, I barely know any Forth, so I may be wrong :) 17:20:32 as for factoring ... I still have a long way to go 17:49:16 --- quit: Zoopee (Read error: 60 (Operation timed out)) 18:14:34 --- join: madgarden (~madgarden@Kitchener-HSE-ppp3576567.sympatico.ca) joined #forth 18:44:53 --- join: melinda (name@melinda.usercloak.freenode) joined #forth 18:47:12 Yay. I'm officially unemployed. "Organizational Restructuring". I've been factored out, heh! 18:48:49 :-( 18:49:32 It's all good. Didn't like that stinkin' job anyway. :D 18:52:13 I was just on the verge of convincing the head of verification that they needed to use Forth scripting to automate all their testing. :) 18:52:31 aww :/ 18:55:35 how does the forth community feel about joy? 18:56:30 it seems like a modernized forth 18:56:46 Or a lispized one. 18:57:25 heh 18:57:59 Anything RPN is good I say. 18:58:13 personalle i think code quotations for control structures are better than forth's immediate words 18:58:21 rpn is nice yes 18:58:36 i'm writing my own interpreter 19:23:49 --- join: onetom_ (~tom@cab.bio.u-szeged.hu) joined #forth 19:23:50 --- quit: onetom (Read error: 54 (Connection reset by peer)) 19:41:14 --- quit: slava (zelazny.freenode.net irc.freenode.net) 19:42:04 --- join: slava (~slava@CPE0080ad77a020-CM.cpe.net.cable.rogers.com) joined #forth 20:02:24 --- quit: slava (zelazny.freenode.net irc.freenode.net) 20:03:16 --- join: slava (~slava@CPE0080ad77a020-CM.cpe.net.cable.rogers.com) joined #forth 20:30:18 How are quotations nicer? 20:49:41 --- quit: Sonarman (Read error: 110 (Connection timed out)) 20:50:56 --- quit: melinda (Read error: 60 (Operation timed out)) 21:06:34 --- part: madgarden left #forth 22:18:04 --- join: _gps_ (~gps@166.70.196.201) joined #forth 22:18:20 hey gps 22:20:43 <_gps_> hi ree 22:26:12 <_gps_> In my Forth-like language written in C I realized that after compilation doing so many case comparisons within a switch must be inefficient, so I started searching and I found a gcc feature for jump tables. 22:26:51 <_gps_> Have any of you implemented a Forth using the gcc extension to goto (Labels as Values in gcc.info)? 22:27:22 is that really a gcc extension or just an included C function 22:27:35 <_gps_> It says it's a gcc extension. 22:27:38 goto addr; goto *addr; 22:27:58 <_gps_> void *ptr; ptr = &&foo; goto *ptr; 22:28:04 not to call it a function, that was a misnomer 22:28:12 I believe that gforth uses this feature. 22:28:20 yeah, that would be more efficient 22:28:28 harder to debug though 22:28:52 <_gps_> yah it may be. 22:28:58 <_gps_> I haven't ever used gforth. 22:29:24 <_gps_> I've been looking at how pforth and ficl are implemented, and they don't use this feature. 22:30:05 <_gps_> Is gforth faster than ficl and pforth usually? 22:30:29 They strive for portability over performance. gforth has the luxury of requiring gcc (GNU-forth). 22:30:58 <_gps_> ok. Thanks TreyB and ree for the help. 22:31:00 (They == pforth/ficl) 22:31:22 G'night, all. 22:31:34 <_gps_> g'night 22:31:56 <_gps_> Forth and Moore have expanded my mind. 22:32:16 <_gps_> I keep looking at my old code and realizing that if I factored from the start I wouldn't have dealt with so many bugs. 22:33:11 <_gps_> I keep asking myself "What does this code do?" and then I make a function for it, and I don't need a comment because it's clear. 22:35:30 --- join: Serg_Penguin (~z@212.34.52.140) joined #forth 22:36:41 yeah, I appreciate the moore way of factoring code 22:37:29 though I think there is more to efficiency when it comes to programming than just code size 23:27:30 --- nick: onetom_ -> onetom 23:29:53 --- quit: warp0x00 (Read error: 110 (Connection timed out)) 23:35:20 --- quit: Serg_Penguin () 23:59:59 --- log: ended forth/03.11.26