00:00:00 --- log: started forth/17.10.04 00:47:57 --- quit: smokeink (Ping timeout: 240 seconds) 00:54:30 --- quit: dys (Ping timeout: 248 seconds) 01:00:52 --- join: smokeink (~smoke@221.7.252.113) joined #forth 01:11:41 --- join: dys (~dys@2003:5b:203b:100:6af7:28ff:fe06:801) joined #forth 02:27:30 --- quit: smokeink (Ping timeout: 246 seconds) 02:33:15 --- quit: mnemnion (Remote host closed the connection) 02:43:31 --- quit: proteusguy (Remote host closed the connection) 02:47:03 --- join: ZombieChicken (~weechat@gateway/tor-sasl/forgottenwizard) joined #forth 03:42:52 --- join: proteusguy (~proteus-g@180.183.48.154) joined #forth 03:42:52 --- mode: ChanServ set +v proteusguy 03:50:26 --- join: mnemnion (~mnemnion@2601:643:8102:7c95:8513:248d:51ef:59f7) joined #forth 03:54:34 --- quit: mnemnion (Ping timeout: 246 seconds) 03:54:38 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 03:59:43 --- quit: proteusguy (Remote host closed the connection) 04:13:03 --- quit: wa5qjh (Remote host closed the connection) 04:15:13 What if the terminal input buffer was just large enough for a token, not an entire line? 04:16:10 So REFILL wouldn't have to read text until a line break, just to the next whitespace. 04:17:21 I'm thinking microcontrollers here, maybe less than 256 byte RAM. 04:18:42 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 04:19:05 Hmm, might not work very well with some parsing words. 04:48:36 --- quit: wa5qjh (Remote host closed the connection) 04:48:39 if you have a separate token buffer, you should be able to get away with an input buffer of any size 04:49:46 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 04:50:16 it's more a question of your software keeping up with the rate of input 04:55:32 --- join: smokeink (~smoke@221.7.252.119) joined #forth 05:23:02 --- quit: wa5qjh (Read error: Connection reset by peer) 05:23:32 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 05:34:00 --- join: nighty-- (~nighty@s229123.ppp.asahi-net.or.jp) joined #forth 05:37:39 --- join: proteusguy (~proteus-g@184.22.240.66) joined #forth 05:37:39 --- mode: ChanServ set +v proteusguy 06:24:57 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 06:26:59 --- quit: wa5qjh (Ping timeout: 255 seconds) 06:27:00 --- nick: wa5qjh_ -> wa5qjh 07:25:20 --- quit: ZombieChicken (Remote host closed the connection) 07:25:43 --- join: ZombieChicken (~weechat@gateway/tor-sasl/forgottenwizard) joined #forth 08:22:34 --- quit: smokeink (Ping timeout: 260 seconds) 09:12:48 --- quit: dys (Ping timeout: 246 seconds) 09:17:39 --- join: muzgo (~abc@mail.oitobits.net) joined #forth 09:47:08 --- join: mnemnion (~mnemnion@2601:643:8102:7c95:8513:248d:51ef:59f7) joined #forth 10:36:05 --- quit: ZombieChicken (Remote host closed the connection) 10:37:01 --- join: ZombieChicken (~weechat@gateway/tor-sasl/forgottenwizard) joined #forth 11:07:56 --- quit: mnemnion (Remote host closed the connection) 11:11:02 --- join: mnemnion (~mnemnion@2601:643:8102:7c95:8513:248d:51ef:59f7) joined #forth 11:11:39 --- quit: mnemnion (Remote host closed the connection) 11:12:36 --- quit: dzho (Quit: leaving) 11:25:32 --- join: dzho (~dzho@unaffiliated/dzho) joined #forth 11:38:35 crc: I actually found a better way 11:38:37 I defined this: 11:38:45 : LOAD-F PAD DUP F! @ ; 11:39:05 for debug purposes, I defined : 64BITS 63 1 SWAP DO DUP 2 I EXPO AND I RSHIFT 48 + EMIT -1 +LOOP 1 AND 48 + EMIT ; (print 1s place due to expo bug) 11:39:15 so now I can do this: 11:39:18 -1.5e LOAD-F 64BITS 1011111111111000000000000000000000000000000000000000000000000000 ok 11:39:24 and it shows me the bits :D 11:39:43 it seemed evil to use a variable 11:39:47 so I just used the PAD 11:41:02 :) 11:54:32 --- quit: muzgo (Remote host closed the connection) 12:06:57 --- join: dys (~dys@tmo-106-163.customers.d1-online.com) joined #forth 15:41:47 --- join: leaverite (~quassel@freebsd/user/wa5qjh) joined #forth 15:56:09 I must be doing something wrong, I'm getting odd results 15:56:18 so if I do the following to see the bits.. 15:56:21 10.5e LOAD-F 64BITS 0100000000100101000000000000000000000000000000000000000000000000 ok 15:56:37 it prints out 10.5e in the 64 bit double precision form (it looks) 15:57:06 now I tried to grasp the exponent part which is, besides the last sign bit, the highest most 8 bits, so I did the following: 15:57:21 255 55 LSHIFT AND 55 RSHIFT 15:57:26 and when I look at the stack, I have 128 15:57:28 not 130? 15:57:40 I should have 130 unless I'm doing something terribly wrong 16:01:24 --- quit: nighty-- (Quit: Disappears in a puff of smoke) 16:07:46 --- quit: karswell (Read error: Connection reset by peer) 16:13:14 FatalNIX: assuming you are using ieee-754, the exponent is 11 bits and mantissa is 52 16:13:56 well I'm looking right at the bits there and it corresponds with my other spec I see, I'm just curious as to why my bitmasks aren't working right.. 16:14:09 which is kinda unrelated to whatever format its in since I can see the bits right there 16:14:21 yeah it's definatelyt 754 16:14:42 but the spec I look at 754 is 8 bit expo 16:15:06 are you looking at single precision 16:15:16 and looking at this output it's definately 8 bit too.. 16:15:57 oh you know 16:16:01 maybe it is 11 for double precision 16:16:08 shit 16:20:09 you make a very good point koisoke_ 16:20:12 DUP 2047 52 LSHIFT AND 52 RSHIFT 1023 - . 3 ok 16:20:31 so I get 3 when I do that- I'm assuming for double precision I subtract 1023 instead from the exponent here 16:20:41 which will give me the actual expone nt 16:22:24 it works! 16:22:28 688128.0e LOAD-F EXPO-F . 19 ok 16:22:34 2 ^ 19 16:26:11 yay 16:29:48 so now I just need a mantissa thingy 16:55:02 --- quit: dys (Ping timeout: 248 seconds) 17:04:55 WHY OH WHY 17:05:06 why can't they just keep floating point numbers on the main stack 17:05:12 it makes way more sense to me 17:05:39 I am not sure a floating point stack should exist 17:05:47 a number is a number 17:06:34 you can't add an integer and a float though 17:07:22 all numbers are numbers but some numbers are more numbers than others 17:07:26 animal farm style 17:07:39 well, I COULD add them.. 17:08:04 I mean 17:08:21 historical reasons. a float was typically be >1 cell, and e.g. x87 implements its own stack anyway 17:08:23 for all you know my number could represent leds on a decoder 17:08:34 true 17:17:53 --- nick: Zarutian_PI2 -> Zarutian_PI 17:50:55 1.0e 2.0e f* 10 f/ :30: Floating-point stack underflow 17:50:56 wat 17:51:23 OH 17:51:25 forgot 10e 18:11:26 https://www.irccloud.com/pastebin/3C9wcCGE/ 18:11:31 Looks like I can get this to work! 18:46:57 10e 308e f** flog f. 308. ok 18:46:57 10e 309e f** flog f. inf ok 18:47:53 It looks like the max exponent is 308. 18:52:57 Note: I am using gforth. 18:53:45 --- join: mnemnion (~mnemnion@c-73-34-61-146.hsd1.co.comcast.net) joined #forth 19:28:00 --- quit: mnemnion (Remote host closed the connection) 19:36:52 --- join: Chef_Gromboli (~Chef_Grom@static-72-88-80-103.bflony.fios.verizon.net) joined #forth 19:48:48 --- join: smokeink (~smoke@221.7.252.119) joined #forth 20:58:17 --- join: mnemnion (~mnemnion@c-73-34-61-146.hsd1.co.comcast.net) joined #forth 21:01:27 --- quit: wa5qjh (Ping timeout: 248 seconds) 21:02:44 --- quit: leaverite (Read error: Connection reset by peer) 21:05:03 10e -311e f** flog f. -311. ok 21:05:03 10e -312e f** flog f. -312.000000000001 ok 21:05:04 10e -323e f** flog f. -323.005185347452 ok 21:05:04 10e -324e f** flog f. -in ok 21:05:50 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 21:12:46 --- quit: Chef_Gromboli (Quit: Leaving) 21:35:40 --- quit: wa5qjh (Remote host closed the connection) 21:38:04 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 21:44:43 --- join: leaverite (~quassel@175.158.225.197) joined #forth 21:44:46 --- quit: leaverite (Changing host) 21:44:46 --- join: leaverite (~quassel@freebsd/user/wa5qjh) joined #forth 22:13:32 --- quit: roundsf (Read error: Connection reset by peer) 22:13:38 --- quit: smokeink (Ping timeout: 258 seconds) 22:14:13 --- join: roundsf (~user@2a00:2381:1a72:10:f5b0:ed90:1e60:9d72) joined #forth 22:28:03 --- quit: proteusguy (Remote host closed the connection) 22:50:45 --- join: proteusguy (~proteus-g@180.183.121.36) joined #forth 22:50:45 --- mode: ChanServ set +v proteusguy 23:17:41 --- join: smokeink (~smoke@221.7.252.112) joined #forth 23:32:27 --- join: dys (~dys@tmo-109-27.customers.d1-online.com) joined #forth 23:38:02 --- quit: roundsf (Read error: Connection reset by peer) 23:39:14 --- join: roundsf (~user@2a00:2381:1a72:10:f5b0:ed90:1e60:9d72) joined #forth 23:43:31 --- quit: roundsf (Read error: Connection reset by peer) 23:43:58 --- join: roundsf (~user@2a00:2381:1a72:10:f5b0:ed90:1e60:9d72) joined #forth 23:59:59 --- log: ended forth/17.10.04