00:00:00 --- log: started forth/03.01.03 00:57:33 --- quit: Klaw` (Read error: 104 (Connection reset by peer)) 02:24:18 --- nick: Speuler -> RoadScare 03:04:49 --- join: kryptide (~smoker@12-215-177-179.client.mchsi.com) joined #forth 03:05:01 --- part: kryptide left #forth 03:22:28 --- quit: RoadScare (Remote closed the connection) 03:23:02 --- join: RoadScare (~Speuler@mnch-d9ba4af5.pool.mediaWays.net) joined #forth 04:23:06 --- join: RoadScare_ (~Speuler@mnch-d9ba4fa4.pool.mediaWays.net) joined #forth 04:31:37 --- quit: RoadScare (Read error: 60 (Operation timed out)) 06:55:17 If I write a 16-bit forthish VM for a microcontroller, how should I deal with 32-bit numbers? 07:24:20 What do you mean by "16-bit forthish VM"? 07:24:41 Robert: as doubles 07:25:38 TreyB: For a microcontroller, stack based VM, with Forth primitives as instructions. 07:25:45 --- join: tathi (~josh@wsip68-15-54-54.ri.ri.cox.net) joined #forth 07:26:19 onetom: Hmm... should I use 2swap, 2dup instructions to deal with those? 07:27:12 Hmm. I really meant "how many bits do you want/need for the CELLL-size"? 07:27:45 Robert: sure. how else? 07:29:11 On an 8-bit microcontroller, I think using 32 bits for everything would be a waste of memory and CPU power... but sometimes I might need 32-bit numbers. 07:30:44 of course. i use 8bit cell size on pic-s coz its much more efficient than a general 16bit implementation 07:32:56 Yes... I did the same, but how should I deal with 32-bit numbers? On the ordinary data stack? 07:33:02 Or should I have a 32-bit stack? 07:35:38 just try it out what is more efficient 07:35:56 just try it out which solution is more efficient 07:36:26 Okay :) 08:05:21 --- join: lament (~lament@h24-78-145-92.vc.shawcable.net) joined #forth 08:14:00 --- quit: lament ("PROSECUTORS WILL BE TRANSGRESSICUTED.") 08:49:24 --- join: lament (~lament@h24-78-145-92.vc.shawcable.net) joined #forth 09:46:26 --- join: crypton (trilluser@1Cust218.tnt4.vancouver.bc.da.uu.net) joined #forth 09:48:09 --- part: crypton left #forth 11:08:41 anyone use screen split terminals? 11:54:14 eh? 12:14:40 iangreen: i used them some times but splitvt is better 12:14:58 u can split 1 window of a screen session w it 12:15:11 this behaviour is more useful 12:25:02 --- quit: lament ("PROSECUTORS WILL BE TRANSGRESSICUTED.") 13:09:45 --- join: rodapop (~askme@24.114.111.156) joined #forth 13:11:07 --- part: rodapop left #forth 13:59:09 --- quit: tathi ("leaving") 15:17:38 --- join: wossname (wossname@HSE-QuebecCity-ppp82155.qc.sympatico.ca) joined #forth 15:20:32 --- join: lament (~lament@h24-78-145-92.vc.shawcable.net) joined #forth 16:48:03 --- quit: lament ("PROSECUTORS WILL BE TRANSGRESSICUTED.") 17:53:45 --- join: lament (~lament@h24-78-145-92.vc.shawcable.net) joined #forth 18:28:15 --- join: jax (~jax@slip-12-65-102-68.mis.prserv.net) joined #forth 18:31:23 --- quit: wossname ("good evening all") 18:57:25 --- quit: jax ("Client Exiting") 21:28:50 --- quit: skylan (Read error: 110 (Connection timed out)) 21:29:19 --- join: skylan (sjh@207.164.213.108) joined #forth 21:37:26 --- quit: skylan ("Reconnecting") 21:37:30 --- join: skylan (sjh@207.164.213.51) joined #forth 21:48:01 --- quit: skylan ("O_O") 21:59:26 --- quit: lament ("PROSECUTORS WILL BE TRANSGRESSICUTED.") 22:21:20 --- join: skylan (sjh@207.164.213.72) joined #forth 23:59:59 --- log: ended forth/03.01.03