00:00:00 --- log: started forth/17.11.16 01:26:33 --- quit: malyn (Ping timeout: 240 seconds) 01:31:09 --- join: malyn (~malyn@unaffiliated/malyn) joined #forth 01:39:52 --- join: mtsd (~mtsd@194.218.150.197) joined #forth 01:51:47 --- join: karswell_ (~user@189.60.199.146.dyn.plus.net) joined #forth 01:52:54 --- quit: karswell (Ping timeout: 248 seconds) 02:12:45 --- join: dys (~dys@2003:5b:203b:100:6af7:28ff:fe06:801) joined #forth 02:46:27 --- quit: mtsd (Ping timeout: 240 seconds) 02:47:55 --- join: mtsd (~mtsd@194.218.150.197) joined #forth 02:52:53 --- quit: mnemnion (Remote host closed the connection) 02:54:27 --- join: mnemnion (~mnemnion@2601:643:8102:7c95:449d:a88a:eb0e:3ee5) joined #forth 02:58:51 --- quit: mnemnion (Ping timeout: 255 seconds) 03:15:51 --- quit: nighty- (Quit: Disappears in a puff of smoke) 03:55:50 --- join: mnemnion (~mnemnion@2601:643:8102:7c95:449d:a88a:eb0e:3ee5) joined #forth 04:00:31 --- quit: mnemnion (Ping timeout: 255 seconds) 04:27:33 --- quit: mtsd (Remote host closed the connection) 04:53:38 --- join: nighty- (~nighty@s229123.ppp.asahi-net.or.jp) joined #forth 05:26:15 --- join: mnemnion (~mnemnion@2601:643:8102:7c95:449d:a88a:eb0e:3ee5) joined #forth 05:30:57 --- quit: mnemnion (Ping timeout: 255 seconds) 05:58:36 johnmark_: I'm not going to be surprised, if gforth isn't smart enough not to convert everything to 64-bit IEEE FPNs intermediately. 06:01:14 I think we need arbitrary precision forth somehow. 06:02:23 I guess you would need a stack of 64 bit pointers that point to arbitrary precision values. 06:07:26 And you need garbage collector for that. 06:08:04 And you need references instead of plain adresses for that. 06:08:09 And you need types for that. 06:09:27 How is it going to differ from weird KM then? Except being implemented in the most unsystematic way possible, since Forth lovers avoid learning math? 06:18:31 You make a good point. 06:19:13 I understand what you are saying about garbage collection. 06:23:45 Each time the size in bytes of the arbitrary precision values changes the computer would have to relocate it in memory. 06:27:15 I wonder if you could use a (RAM drive) file allocation table approach to help manage the memory. 06:35:17 As the size increases beyond the sector size you just use up another sector. Now there is no need to move all the memory around. 06:45:20 --- join: ncv (~neceve@2a02:c7d:c5c9:a900:c792:a3e8:397d:b37) joined #forth 06:45:20 --- quit: ncv (Changing host) 06:45:20 --- join: ncv (~neceve@unaffiliated/neceve) joined #forth 06:45:20 How does it let you avoid GC? 07:03:43 --- join: proteus-guy (~proteus-g@2405:9800:bc10:1ca:edf7:8dc4:959a:cfd) joined #forth 07:42:56 --- join: josh5tone (~jstone@99-51-169-74.lightspeed.nworla.sbcglobal.net) joined #forth 08:19:31 --- quit: ZombieChicken (Remote host closed the connection) 08:21:19 --- join: ZombieChicken (~weechat@gateway/tor-sasl/forgottenwizard) joined #forth 08:26:59 --- join: mnemnion (~mnemnion@2601:643:8102:7c95:449d:a88a:eb0e:3ee5) joined #forth 08:31:24 --- quit: mnemnion (Ping timeout: 258 seconds) 08:40:47 --- quit: MrMobius (Ping timeout: 260 seconds) 09:04:56 --- quit: ncv (Ping timeout: 264 seconds) 09:17:43 --- quit: nighty- (Ping timeout: 248 seconds) 09:47:10 --- join: gravicappa (~gravicapp@ppp83-237-160-129.pppoe.mtu-net.ru) joined #forth 09:57:51 --- join: mnemnion (~mnemnion@2601:643:8102:7c95:449d:a88a:eb0e:3ee5) joined #forth 10:02:13 --- quit: mnemnion (Ping timeout: 240 seconds) 10:04:19 --- quit: gravicappa (Ping timeout: 240 seconds) 10:20:02 --- join: mnemnion (~mnemnion@2601:643:8102:7c95:449d:a88a:eb0e:3ee5) joined #forth 10:30:26 --- quit: ZombieChicken (Ping timeout: 248 seconds) 10:31:21 --- join: ZombieChicken (~weechat@gateway/tor-sasl/forgottenwizard) joined #forth 10:32:09 --- quit: dys (Ping timeout: 258 seconds) 11:01:21 --- join: dys (~dys@tmo-103-7.customers.d1-online.com) joined #forth 11:09:09 --- quit: Zarutian_PI (Ping timeout: 260 seconds) 11:44:47 --- join: alexshendi (~yaaic@ip4d15fdf7.dynamic.kabel-deutschland.de) joined #forth 12:03:40 --- join: gravicappa (~gravicapp@ppp83-237-160-129.pppoe.mtu-net.ru) joined #forth 12:17:59 --- join: Zarutian_PI (~3.1415@173-133-17-89.fiber.hringdu.is) joined #forth 12:39:50 --- quit: gravicappa (Ping timeout: 248 seconds) 15:11:49 --- quit: karswell_ (Read error: Connection reset by peer) 15:18:20 --- quit: dys (Ping timeout: 268 seconds) 18:02:07 --- join: nighty- (~nighty@kyotolabs.asahinet.com) joined #forth 18:50:46 --- join: Gromboli (~Gromboli@static-72-88-80-103.bflony.fios.verizon.net) joined #forth 18:51:42 DGASAU if you design the whole system to use sector based memory allocation then you can release the memory back to the system. The memory is fragmented but seek time is not a problem with RAM. The code to read the sectors is a little more complicated than reading with a simple index of a memory pointer, but very doable. 18:53:53 Perhaps in my retirement I can make an arbitrary precision forth. 18:55:33 The sectors would mean that there is no need to move 1000 bytes over one byte so you can add one more byte to a string. 18:56:41 pretty sure that's just a larger-atomic-size link list. I don't know much about the way arbitrary-precision algorithms work, but I expect that would only work well if none of them require random access. 18:56:51 s/link/linked 20:02:55 --- join: MrMobius2 (9c3891b4@gateway/web/freenode/ip.156.56.145.180) joined #forth 20:21:20 --- quit: Gromboli (Quit: Leaving) 20:56:11 --- join: MrBusiness (~ArcMrBism@2602:306:8325:a300:a:d288:b2ca:3c7f) joined #forth 22:29:50 --- quit: MrMobius2 (Quit: Page closed) 23:59:59 --- log: ended forth/17.11.16