00:00:00 --- log: started forth/17.10.22
01:23:02 --- quit: mtsd (Quit: Leaving)
01:41:19 --- quit: smokeink (Ping timeout: 240 seconds)
02:21:10 --- join: mnemnion (~mnemnion@cpc130658-camd16-2-0-cust176.know.cable.virginm.net) joined #forth
02:21:24 --- join: gravicappa (~gravicapp@ppp83-237-169-222.pppoe.mtu-net.ru) joined #forth
04:23:25 --- quit: mnemnion (Remote host closed the connection)
04:23:56 --- join: mnemnion (~mnemnion@cpc130658-camd16-2-0-cust176.know.cable.virginm.net) joined #forth
04:25:50 --- join: nighty-- (~nighty@s229123.ppp.asahi-net.or.jp) joined #forth
04:28:29 --- quit: mnemnion (Ping timeout: 260 seconds)
04:28:56 --- join: mnemnion (~mnemnion@host86-160-25-45.range86-160.btcentralplus.com) joined #forth
04:45:35 --- quit: mnemnion (Remote host closed the connection)
04:55:20 --- join: mnemnion (~mnemnion@host86-160-25-45.range86-160.btcentralplus.com) joined #forth
05:01:27 --- quit: gravicappa (Ping timeout: 240 seconds)
05:03:46 --- quit: mnemnion (Remote host closed the connection)
05:37:58 --- quit: nighty-- (Ping timeout: 258 seconds)
05:50:31 --- join: nighty-- (~nighty@s229123.ppp.asahi-net.or.jp) joined #forth
06:10:42 --- join: gravicappa (~gravicapp@ppp83-237-162-100.pppoe.mtu-net.ru) joined #forth
06:15:38 --- quit: Zarutian_PI (Read error: Connection reset by peer)
06:16:11 --- join: Zarutian_PI (~3.1415@173-133-17-89.fiber.hringdu.is) joined #forth
06:17:57 --- join: frunobulax (~mhx@541E3425.cm-5-7a.dynamic.ziggo.nl) joined #forth
06:21:43 <frunobulax> Knock, knock.
06:24:09 --- quit: frunobulax (Quit: a quit that really quits)
07:04:26 --- quit: proteusguy (Remote host closed the connection)
07:04:28 --- join: mnemnion (~mnemnion@host86-160-25-45.range86-160.btcentralplus.com) joined #forth
07:08:27 --- quit: mnemnion (Ping timeout: 240 seconds)
07:13:36 --- join: bedah (~bedah@2a02:810d:243f:f584:b4b5:7454:25e5:3c32) joined #forth
07:19:22 --- join: _spt_ (~Steve@unaffiliated/-spt-/x-5624824) joined #forth
07:52:10 --- quit: nighty-- (Ping timeout: 240 seconds)
08:40:40 --- quit: _spt_ (Quit: Leaving)
10:04:32 <johnmark_> frunobulax hi.
10:36:14 --- join: nighty-- (~nighty@s229123.ppp.asahi-net.or.jp) joined #forth
11:45:22 --- join: dys (~dys@tmo-122-25.customers.d1-online.com) joined #forth
11:51:10 --- quit: M-jimt (Ping timeout: 240 seconds)
11:51:10 --- quit: pointfree1 (Ping timeout: 240 seconds)
12:05:19 --- join: mnemnion (~mnemnion@host86-160-25-45.range86-160.btcentralplus.com) joined #forth
12:09:57 --- quit: mnemnion (Ping timeout: 252 seconds)
12:15:54 --- join: mnemnion (~mnemnion@host86-160-25-45.range86-160.btcentralplus.com) joined #forth
12:19:11 <FatalNIX> I'm assumin there's never reazlly a reliable way to determine the size of thepad at runtime is there
12:19:31 <FatalNIX> I wonder if I can expect it to at least be 512 bytes..
12:28:36 <johnmark_> gfoth pad-minsize . 132  ok
12:29:47 <johnmark_> gforth: pad . 140692410360720  ok
12:42:26 --- join: M-jimt (jimtmatrix@gateway/shell/matrix.org/x-dpeipdwbvxgpvrqy) joined #forth
13:15:50 --- join: pointfree1 (pointfreem@gateway/shell/matrix.org/x-hwtyfzelhzahttmt) joined #forth
13:21:36 <crc> FatalNIX: ANS section 3.3.3.6 only guarantees a min of 84 characters for PAD
13:23:34 <crc> and 3.2.6 shows an environment query of /pad to get the actual size
13:38:40 --- join: Gromboli (~Gromboli@static-72-88-80-103.bflony.fios.verizon.net) joined #forth
14:16:59 <FatalNIX> I see
14:17:23 <FatalNIX> oh man this may be harder than I thought
14:18:21 <FatalNIX> I need to accept a number with ACCEPT, and then check to see if it's a number.
14:18:30 <FatalNIX> Oh wait I have an idea, I never thought of this before..
14:18:58 <FatalNIX> Maybe I can tell if something looks like a number just by looking in the ascii table and checking to see if every digit is in the ascii range
14:19:00 <FatalNIX> of numbers
14:22:57 --- quit: gravicappa (Ping timeout: 240 seconds)
15:33:05 <FatalNIX> I must be blind..
15:33:17 <FatalNIX> https://www.irccloud.com/pastebin/EEPRgqaH/
15:33:39 <FatalNIX> when I do @,.. shouldn't I be getting the ascii code for F not 6510615555426176838 ?
15:33:40 <FatalNIX> wtf ...
15:33:48 <FatalNIX> I am very confused.
15:34:33 <FatalNIX> something wonky is going on around here..
15:35:27 --- quit: nighty-- (Ping timeout: 255 seconds)
15:35:31 <FatalNIX> https://www.irccloud.com/pastebin/iaReGBEH/
15:35:42 <FatalNIX> Looks like it works on the jsforth one..
15:35:52 <FatalNIX> I get 70 which in the top of my head I assume is F
15:36:34 <FatalNIX> OH DUH
15:36:35 <FatalNIX> I want C@
15:36:37 <FatalNIX> :D
15:38:24 <johnmark_> When inputing a number it is nice to be able to enter "2 s>f pi f*"
15:39:20 <FatalNIX> wot
15:40:09 <johnmark_> s" 2 s>f pi f* " evaluate f. 6.28318530717959  ok
15:40:50 <johnmark_> let evaluate to the conversion for you.
15:42:29 <johnmark_> I have been trying to figure out accept myself.
15:43:22 <johnmark_> Do you know how to use accept?
15:43:56 <FatalNIX> yes. you give it an address and a limit and it goes up to CR
15:44:01 <FatalNIX> or limit
15:44:07 <FatalNIX> sp I could do 
15:44:09 <FatalNIX> PAD 50 ACCEPT
15:44:21 <FatalNIX> so*
15:44:53 <FatalNIX> pforth apparently doesn't like using EXIT from a loop. wut..
15:46:46 <johnmark_> So the string goes into pad?
15:47:16 <FatalNIX> in that case yes
15:47:31 <johnmark_> how to I print or evaluate pad?
15:47:33 <FatalNIX> I'm be using the first 80 bytes of the PAD to input my boolean expression
15:47:43 <FatalNIX> so ACCEPT returns how many characters you typed
15:47:52 <johnmark_> yes
15:48:12 <FatalNIX> but it consumes the address
15:48:14 <FatalNIX> so you can do.
15:48:34 <FatalNIX> PAD DUP 80 ACCEPT TYPE TEst TEst   ok
15:48:45 <FatalNIX> or PAD 80 ACCEPT PAD TYPE
15:48:51 <FatalNIX> er
15:48:53 <FatalNIX> PAD SWAP TYPE
15:49:33 <FatalNIX> of course nothing stops you from going like
15:50:14 <FatalNIX> PAD DUP 80 ACCEPT 0 DO DUP C@ EMIT 1+ LOOP
15:50:17 <FatalNIX> or something like that
15:50:21 <FatalNIX> I'm just guessing on top of my head
15:52:31 <johnmark_> It works!!!
15:52:39 <johnmark_> Thank you!!!
15:52:46 <johnmark_> pad 50 accept pad swap evaluate f.
15:53:19 <FatalNIX> I thought you were the all known forth genius
15:53:19 <FatalNIX> :D
15:53:33 <johnmark_> No! I am a beginner...
15:53:43 <FatalNIX> I found a fun way to get floating point numbers into the data stack
15:55:29 <FatalNIX> 1.5e PAD DUP f! @ . 4609434218613702656    ok
15:55:37 <FatalNIX> so I could take it apart and see the inside of it
15:55:43 <FatalNIX> with bitwise operations
15:56:03 <FatalNIX> I literally just copy the bits to the PAD and then read it into the data stack :D
15:56:07 <FatalNIX> because f>d didn't work
15:56:48 <FatalNIX> I don't even understand f>d much
15:56:53 <FatalNIX> but d>f yes
15:56:59 <johnmark_> oh
15:58:23 <johnmark_> I have been trying to write a program where you enter the weigh of an object and the program tell you how much it will weigh on the moon.
15:58:45 <johnmark_> But I got stuck on the input weight command.
15:58:59 <FatalNIX> heh
15:59:10 <FatalNIX> I have to allow somebody to enter in a boolean algebraic expression
15:59:12 <johnmark_> The space suit add 180 pounds.
15:59:17 <FatalNIX> and I have to tokenize it and parse it
15:59:24 <FatalNIX> and see if it's valid
15:59:29 <johnmark_> ok
15:59:40 <FatalNIX> it's turning into a lot of time consuming..
15:59:57 <FatalNIX> but ideally, the parser should be fairly ok I will do shift reduce parsing
16:00:03 <FatalNIX> finding the handle may be the hard part
16:01:28 <FatalNIX> man I wish I could use exit..
16:01:41 <FatalNIX> this is much harder when I can't just exit
16:03:29 --- quit: Gromboli (Quit: Leaving)
16:15:45 <FatalNIX> O M G! I DID IT
16:15:51 * FatalNIX does the dance
16:15:55 <FatalNIX> a dance*
16:15:59 <FatalNIX>     ok
16:15:59 <FatalNIX> Stack<10> 
16:15:59 <FatalNIX> s" 12" LOOKS-LIKE-NUMBER . -1    ok
16:15:59 <FatalNIX> Stack<10> 
16:16:00 <FatalNIX> s" 1a" LOOKS-LIKE-NUMBER . 0    ok
16:16:01 <FatalNIX> Stack<10> 
16:16:12 <FatalNIX> johnmark_: Here's the code:
16:16:32 <FatalNIX> https://www.irccloud.com/pastebin/KJXh3DGn/
16:16:50 <FatalNIX> let me check it with test..
16:17:53 <FatalNIX> check it with accept I mean
16:18:47 <FatalNIX> PAD DUP 80 ACCEPT LOOKS-LIKE-NUMBER . 55 -1    ok
16:18:47 <FatalNIX> Stack<10> 
16:18:47 <FatalNIX> PAD DUP 80 ACCEPT LOOKS-LIKE-NUMBER . abcd 0    ok
16:18:47 <FatalNIX> Stack<10> 
16:18:48 <FatalNIX> YES!
16:18:54 <FatalNIX> johnmark_: Epicness ^
16:41:09 --- quit: nighty- (Quit: Disappears in a puff of smoke)
16:41:56 <johnmark_> I just got back.  My wife told me that supper is ready.  It was good.
16:45:47 <johnmark_> FatalNIX congratulations!!!
17:17:58 --- quit: mnemnion (Remote host closed the connection)
17:18:06 <johnmark_> FatalNIX whats next?
17:25:02 --- join: mnemnion (~mnemnion@cpc130658-camd16-2-0-cust176.know.cable.virginm.net) joined #forth
17:31:03 --- quit: mnemnion (Ping timeout: 240 seconds)
18:25:11 --- join: Gromboli (~Gromboli@static-72-88-80-103.bflony.fios.verizon.net) joined #forth
18:28:09 --- join: mnemnion (~mnemnion@cpc130658-camd16-2-0-cust176.know.cable.virginm.net) joined #forth
18:32:37 --- quit: mnemnion (Ping timeout: 248 seconds)
18:39:45 --- join: wa5qjh (~quassel@175.158.225.193) joined #forth
18:39:45 --- quit: wa5qjh (Changing host)
18:39:45 --- join: wa5qjh (~quassel@freebsd/user/wa5qjh) joined #forth
18:56:09 <FatalNIX> next is the tokenizer
18:56:18 <FatalNIX> I'm trying to figure out if forth has something like continue or next
18:56:25 <FatalNIX> for forcing a loop to go to the next
19:04:21 --- join: nighty- (~nighty@kyotolabs.asahinet.com) joined #forth
19:16:38 <FatalNIX> I can emulate it with BEGIN surrounding DO
19:25:16 --- quit: wa5qjh (Remote host closed the connection)
19:41:26 <FatalNIX> man this is weird
19:41:35 <FatalNIX> if only there was a continue statement XD
19:41:53 --- quit: Gromboli (Quit: Leaving)
19:45:11 <zy]x[yz> you can write one
19:45:39 <zy]x[yz> loops are such a janky thing in forth imo
19:45:53 <zy]x[yz> I really would like to come up with a better way to do them
20:16:30 --- join: mnemnion (~mnemnion@cpc130658-camd16-2-0-cust176.know.cable.virginm.net) joined #forth
20:21:06 --- quit: mnemnion (Ping timeout: 252 seconds)
20:30:13 --- join: proteusguy (~proteus-g@p2035150-ipngn200605osakachuo.osaka.ocn.ne.jp) joined #forth
20:30:13 --- mode: ChanServ set +v proteusguy
20:31:33 --- quit: proteusguy (Max SendQ exceeded)
21:01:24 <FatalNIX> I might have to take the week off from work..
21:01:28 <FatalNIX> I just have way too much shit to do
22:04:42 --- join: mnemnion (~mnemnion@cpc130658-camd16-2-0-cust176.know.cable.virginm.net) joined #forth
22:08:50 --- quit: mnemnion (Ping timeout: 240 seconds)
22:09:32 --- quit: reepca (Read error: Connection reset by peer)
22:09:58 --- join: reepca (~user@208.89.170.230) joined #forth
22:21:59 <reepca> FatalNIX: LEAVE is what you're looking for. DO loops don't work with EXIT because EXIT knows nothing about the necessary clean up. You can do UNLOOP to clean up followed by EXIT, or you can do LEAVE, which is just UNLOOP EXIT.
22:22:41 <reepca> DO usually keeps the indices on the return stack, so EXIT tries to basically jump to whatever the index is, which understandably screws stuff up.
23:41:25 --- quit: Zarutian_PI (Ping timeout: 248 seconds)
23:49:25 --- join: Zarutian_PI (~3.1415@89.17.133.173) joined #forth
23:49:57 --- quit: dys (Ping timeout: 240 seconds)
23:53:08 --- join: mnemnion (~mnemnion@cpc130658-camd16-2-0-cust176.know.cable.virginm.net) joined #forth
23:57:44 --- quit: mnemnion (Ping timeout: 255 seconds)
23:59:59 --- log: ended forth/17.10.22