00:00:00 --- log: started forth/07.05.18 02:14:51 --- join: segher__ (n=segher@dslb-084-056-160-001.pools.arcor-ip.net) joined #forth 02:14:54 --- quit: segher_ (Read error: 104 (Connection reset by peer)) 02:36:06 --- join: crest_ (n=crest@p5489E5A8.dip.t-dialin.net) joined #forth 02:39:35 --- join: crest__ (n=crest@p5489dd95.dip.t-dialin.net) joined #forth 02:44:03 --- join: Crest____ (n=crest@p5489CDB0.dip.t-dialin.net) joined #forth 02:44:23 --- quit: Crest (Nick collision from services.) 02:44:29 --- nick: Crest____ -> Crest 02:56:03 --- quit: crest_ (Read error: 110 (Connection timed out)) 02:59:58 --- quit: crest__ (Read error: 110 (Connection timed out)) 03:12:11 --- join: ayrnieu (n=julian@pdpc/supporter/sustaining/ayrnieu) joined #forth 03:53:50 --- join: crest_ (n=crest@p5489DB72.dip.t-dialin.net) joined #forth 04:10:02 --- quit: Crest (Read error: 110 (Connection timed out)) 05:40:24 --- join: timlarson_ (n=timlarso@65.116.199.19) joined #forth 05:42:25 --- quit: timlarson_ (Client Quit) 05:48:05 --- join: timlarson_ (n=timlarso@65.116.199.19) joined #forth 06:11:08 --- join: ygrek (i=user@gateway/tor/x-d74f592b69a6a4c5) joined #forth 07:58:25 --- quit: Quartus__ (Read error: 60 (Operation timed out)) 08:06:23 --- quit: ygrek (Remote closed the connection) 08:07:21 --- join: ygrek (i=user@gateway/tor/x-15a7d1f7d56c5d99) joined #forth 08:24:03 --- join: Baughn_ (n=svein@195134062103.customer.alfanett.no) joined #forth 08:24:23 --- quit: Baughn (Read error: 104 (Connection reset by peer)) 08:28:50 --- quit: madwork (Read error: 104 (Connection reset by peer)) 08:34:38 --- join: madwork (n=foo@204.138.110.15) joined #forth 08:46:08 --- quit: Baughn_ ("Reconnecting") 08:46:19 --- join: Baughn (n=svein@195134062103.customer.alfanett.no) joined #forth 08:54:56 --- join: yumehito (n=yumehito@b-internet.87.103.254.70.snt.ru) joined #forth 08:58:12 --- quit: yumehito_ (Read error: 60 (Operation timed out)) 08:59:50 --- quit: timlarson_ (Read error: 104 (Connection reset by peer)) 09:00:14 --- join: timlarson_ (n=timlarso@65.116.199.19) joined #forth 09:16:17 --- join: timlarson__ (n=timlarso@65.116.199.19) joined #forth 09:33:20 --- quit: timlarson_ (Read error: 110 (Connection timed out)) 09:39:09 --- join: yumehito_ (n=yumehito@b-internet.87.103.254.70.snt.ru) joined #forth 09:51:30 --- join: ASau (n=user@217.118.66.55) joined #forth 09:51:31 --- quit: yumehito (Read error: 110 (Connection timed out)) 09:58:59 --- join: yumehito (n=yumehito@b-internet.87.103.254.70.snt.ru) joined #forth 10:01:10 --- quit: yumehito (Client Quit) 10:11:46 --- quit: yumehito_ (Read error: 110 (Connection timed out)) 11:05:55 --- join: ASau` (n=user@217.118.66.59) joined #forth 11:18:27 --- quit: ASau (Read error: 110 (Connection timed out)) 11:18:38 --- nick: ASau` -> ASau 12:41:24 --- join: ASau` (n=user@217.118.66.55) joined #forth 12:46:04 --- quit: ASau (Read error: 104 (Connection reset by peer)) 12:51:30 --- join: yumehito (n=yumehito@b-internet.87.103.254.70.snt.ru) joined #forth 13:10:26 --- join: Quartus__ (n=Quartus_@209.167.5.1) joined #forth 13:16:59 --- quit: ygrek (Remote closed the connection) 13:27:29 --- quit: Quartus__ (Read error: 104 (Connection reset by peer)) 13:28:38 --- quit: timlarson__ (Read error: 104 (Connection reset by peer)) 13:42:16 hey 13:43:19 hey 14:15:08 --- quit: yumehito ("no cat anywhere ever gave anyone a straight answer") 14:20:09 --- join: yumehito (n=yumehito@b-internet.87.103.254.70.snt.ru) joined #forth 14:41:59 --- quit: ASau` (Read error: 110 (Connection timed out)) 14:57:29 good evening 14:57:53 hey 14:58:11 what's up boys? 15:02:04 --- join: crest__ (n=crest@p5489E303.dip.t-dialin.net) joined #forth 15:05:25 howdy 15:07:57 --- join: sorear (n=stefan@ip68-6-133-142.sd.sd.cox.net) joined #forth 15:08:07 hi sorear 15:09:39 --- quit: crest_ (Read error: 60 (Operation timed out)) 15:09:48 hello slava 15:19:27 Not too much here. How about you? 15:20:35 mostly just suprised I'm so interesting :) 15:20:54 I was replying to slava. 15:21:07 OK 15:45:08 sorear: did you just recently become interesting?! 15:51:22 JasonWoof: I assume word spreads slowly. I've only said like 20 lines in the entire forth community 15:51:50 sorear: yeah, but we here you're actually writing code. 15:52:15 * slava is writing code too 15:52:30 this is, unfortunately, not as common as you might hope 15:52:48 usually it's just slava, quartus and crc that write code 15:52:53 and the rest of us just talk about it 15:58:25 --- join: tathi (n=josh@pdpc/supporter/bronze/tathi) joined #forth 15:58:25 --- mode: ChanServ set +o tathi 15:58:39 hahaha 16:01:27 i'm working on my compiler, trying to bum a few instructions here and there 16:05:51 factor-related? 16:06:09 --- join: GregCrain (n=GCrain@c-68-61-255-250.hsd1.mi.comcast.net) joined #forth 16:06:14 --- part: GregCrain left #forth 16:15:42 --- join: ForthIRC (n=mhx@g143105.upc-g.chello.nl) joined #forth 16:39:02 --- quit: ForthIRC ("a quit that really quits") 17:20:35 --- nick: segher__ -> segher 17:30:54 sorear: yes i was working on the register allocator and now i'm improving constant folding 17:31:30 Ooh. factor.org still implies it's a dumb bytecode compiler 17:31:50 where? 17:32:47 The first thing in the feature list is "has an optimizing native compiler" 17:32:49 Need to find it agian. 17:33:02 Oh ok, I'll believe that 17:33:17 the current factor implementation never had a bytecode compiler. at one point it was interpreted though 17:33:23 What do you use images for? 17:33:27 purely interpreted, that is. 17:33:35 the interpreter is still around and runs a portion of the code 17:33:48 sorear: same as squeak, sbcl, and other image-based systems 17:34:17 slava: The only image using system I've used is gforth. Is it on the list too? 17:34:25 yes 17:34:39 except factor's images are more flexible 17:34:58 you can even save a game of space invaders or tetris then resume it later 17:35:22 all objects in the data heap, and in particular all ui state is saved 17:36:01 for example, i build a factor image with httpd loaded, then upload it to factorcode.org, because i don't want to bootstrap on the server 17:55:48 --- quit: tathi ("leaving") 18:02:01 sorear: i updated my to do list for 1.0 http://www.factorcode.org/ 18:08:25 ok, i need to fix the mbr on my windows partition and the stupid recovery console wont let me because IT doesnt understand the passwords on that partition 18:08:32 after upgrading to sp2. 18:08:51 anyone know a way i can restore a windows MBR without using the xp install cd? 18:09:58 too heck with it lol ill ust reinstall over the top 18:10:26 try using fdisk ? 18:10:57 cant 18:11:03 xp doesnt HAVE fdisk 18:13:28 *gape* 18:14:24 don't suppose you have any linux install disks handy - those make decently flexible rescue disks (assuming of course you know the interface) 18:17:22 so what forths support multithreading? 19:00:36 AIUI, quite a few. 19:00:57 The standard model includes a register for thread local storage! 19:01:18 eh? 19:01:28 Quartus: UP 19:01:38 uh, LEFT 19:01:40 i'm talking about OS-native threading with solid support for mutexes, thread-safe data structures, message queues, etc 19:01:43 Quartus: User Pointer 19:01:49 'standard model'? 19:02:29 slava: Well forth is an OS, so all forth threading is OS-native :) 19:02:46 i'm explicitly asking about hosted forths 19:03:16 And I'm mostly familiar with documentation on how to write microcontroller forths. NM then. 19:35:00 --- join: snoopy_1711 (i=snoopy_1@dslb-084-058-171-216.pools.arcor-ip.net) joined #forth 19:43:09 --- quit: Snoopy42 (Read error: 145 (Connection timed out)) 19:43:30 --- nick: snoopy_1711 -> Snoopy42 20:22:13 --- quit: OrngeTide (zelazny.freenode.net irc.freenode.net) 20:22:26 --- join: OrngeTide (n=orange@orangetide.com) joined #forth 20:23:35 --- log: started forth/07.05.18 20:23:35 --- join: clog (n=nef@bespin.org) joined #forth 20:23:35 --- topic: 'Welcome to #forth. We discuss the Forth programming language and a variety of technical subjects. Introduction: http://tinyurl.com/kvawv | Starting Forth: http://tinyurl.com/rm7pq | Thinking Forth: http://tinyurl.com/nsy4j | Gforth compiler: http://tinyurl.com/s8uho | ANS/ISO Forth Standard doc: http://tinyurl.com/nx7dx | http://quartus.net/search | Paste: http://forth.pastebin.ca' 20:23:35 --- topic: set by Quartus on [Sat Nov 25 22:45:21 2006] 20:23:35 --- names: list (clog OrngeTide @JasonWoof uiuiuiu hnaz ccfg crc mrsbrisby gordonjcp cmeme warpzero nighty- madgarden I440r timlarson @Quartus Shain gnomon TreyB segher ayrnieu madwork Baughn yumehito crest__ sorear Snoopy42 @slava) 21:23:40 --- join: nighty^ (n=nighty@sushi.rural-networks.com) joined #forth 21:44:09 --- join: edrx (n=Eduardo@201.5.14.133) joined #forth 22:41:23 --- join: ygrek (i=user@gateway/tor/x-b4c341db32941e0f) joined #forth 22:41:24 --- quit: ygrek (Client Quit) 23:26:24 : tum/mod ( ut u -- u ud ) dup >r um/mod r> swap >r um/mod r> ; 23:26:43 Is that too complicated? 23:26:56 yes 23:27:01 I'm not crazy about it. OTOH, it worked the first time 23:27:14 are ut and ud single or double cell? 23:27:27 ud is double, ut is triple. 23:27:36 ok 23:28:01 this is a factor of, among other things, m*/ 23:31:19 i'm not a big fan of having tons of variations of the basic arithmetic ops 23:33:18 Neither am I. overloading is cool - too bad you need type info (static like haskell or dynamic like factor, doesn't matter) to do it 23:33:42 otoh, thinking forth tells you no overloading is a feature 23:34:27 or static like strongforth 23:50:24 --- join: ygrek (i=user@gateway/tor/x-4a84bf9ac1c97a9e) joined #forth 23:59:59 --- log: ended forth/07.05.18