00:00:00 --- log: started forth/08.02.19 00:00:34 --- quit: JasonWoof ("Leaving.") 00:08:25 --- quit: maht (Read error: 104 (Connection reset by peer)) 00:21:26 --- quit: nighty^ ("Disappears in a puff of smoke") 01:09:00 --- join: crest_ (n=crest@p5B1074F9.dip.t-dialin.net) joined #forth 02:27:18 --- join: Al2O3_ (n=Al2O3@c-76-120-54-133.hsd1.co.comcast.net) joined #forth 02:34:07 --- quit: Al2O3 (Read error: 110 (Connection timed out)) 04:05:15 --- join: Quartus__ (n=Quartus_@209.167.5.1) joined #forth 04:07:08 --- join: tathi (n=josh@pdpc/supporter/bronze/tathi) joined #forth 04:07:08 --- mode: ChanServ set +o tathi 04:28:08 --- quit: Quartus__ (Read error: 104 (Connection reset by peer)) 04:55:30 --- quit: rAyS ("Should have paid the bill.") 04:56:57 --- quit: tathi ("leaving") 05:05:17 --- join: nighty^ (n=nighty@p3047-adsau16honb13-acca.tokyo.ocn.ne.jp) joined #forth 06:01:45 --- join: madwork (n=foo@204.138.110.15) joined #forth 07:27:16 --- join: edrx (i=edrx@189.25.96.238) joined #forth 07:28:18 --- join: maht (n=maht@85.189.31.174.proweb.managedbroadband.co.uk) joined #forth 08:07:38 --- quit: nighty^ ("Disappears in a puff of smoke") 08:08:07 --- part: edrx left #forth 08:11:47 --- quit: madwork ("?OUT OF DATA ERROR") 08:12:38 --- join: madwork (n=foo@204.138.110.15) joined #forth 08:26:55 --- quit: Al2O3_ (Remote closed the connection) 08:27:25 --- join: Al2O3 (n=Al2O3@c-76-120-54-133.hsd1.co.comcast.net) joined #forth 08:58:14 --- join: Quartus__ (n=Quartus_@209.167.5.2) joined #forth 09:24:52 --- quit: madwork (Read error: 110 (Connection timed out)) 09:58:51 --- join: madwork (n=foo@204.138.110.15) joined #forth 10:40:10 --- join: forther (n=forther@c-67-180-150-67.hsd1.ca.comcast.net) joined #forth 10:50:25 --- join: ygrek (i=user@gateway/tor/x-aec27613cd2bd932) joined #forth 11:03:27 --- quit: ramkrsna ("Leaving") 11:21:09 --- quit: sauvin (Remote closed the connection) 11:49:07 --- join: ramkrsna (n=ramkrsna@unaffiliated/ramkrsna) joined #forth 12:36:35 --- join: snoopy_1711 (i=snoopy_1@dslb-088-068-210-053.pools.arcor-ip.net) joined #forth 12:44:47 --- quit: Snoopy42 (Read error: 145 (Connection timed out)) 12:44:56 --- nick: snoopy_1711 -> Snoopy42 13:02:40 --- join: arke (n=arke@p57A75FF3.dip.t-dialin.net) joined #forth 13:02:40 --- mode: ChanServ set +o arke 13:03:27 --- quit: timlarson (Read error: 110 (Connection timed out)) 14:05:36 --- quit: ramkrsna (Remote closed the connection) 14:27:45 --- quit: ygrek (Remote closed the connection) 14:46:28 --- join: timlarson (n=timlarso@user-12l37rb.cable.mindspring.com) joined #forth 14:51:38 --- join: tathi (n=josh@pdpc/supporter/bronze/tathi) joined #forth 14:51:38 --- mode: ChanServ set +o tathi 15:00:52 --- join: crest__ (n=crest@p5B107D4D.dip.t-dialin.net) joined #forth 15:07:37 --- quit: forther ("Leaving") 15:16:59 --- quit: crest_ (Read error: 110 (Connection timed out)) 16:06:29 --- join: nighty^ (n=nighty@210.188.173.246) joined #forth 16:37:49 --- quit: lucca (Remote closed the connection) 16:39:50 --- join: lucca (n=lucca@kuu.accela.net) joined #forth 16:50:00 --- quit: proteusguy (Read error: 110 (Connection timed out)) 16:51:03 --- join: proteusguy (n=proteusg@ppp-124-120-223-250.revip2.asianet.co.th) joined #forth 16:56:12 --- quit: cr1 (Remote closed the connection) 16:58:42 --- join: crc (n=crc@pool-72-81-42-24.phlapa.east.verizon.net) joined #forth 16:58:51 --- mode: ChanServ set +o crc 17:41:03 --- quit: tathi ("leaving") 17:48:50 --- join: JasonWoof (n=JasonWoo@unaffiliated/herkamire) joined #forth 17:48:50 --- mode: ChanServ set +o JasonWoof 18:06:34 --- join: arke_ (n=arke@p57A75FF3.dip.t-dialin.net) joined #forth 18:23:15 --- quit: arke (Connection timed out) 18:33:56 --- quit: Quartus__ (Read error: 104 (Connection reset by peer)) 22:15:28 --- join: ramkrsna (n=ramkrsna@unaffiliated/ramkrsna) joined #forth 22:28:12 Hey Kids - read an interesting article from Reddit: http://www.pipeline.com/~hbaker1/ForthStack.html from 1994 evidently. Scroll down to where it talks about Stack Machine Implementation. 22:28:56 Instead of return addresses on the return stack it talks about pushing the entire subrouting's code instructions onto it and executing from there. Is anyone actually doing that in a forth implementation here? Sounds interesting... 22:58:03 --- join: sauvin (n=sauvin@74-136-191-181.dhcp.insightbb.com) joined #forth 23:00:36 sounds crazy to me 23:43:36 --- quit: arke_ (Read error: 110 (Connection timed out)) 23:50:47 --- join: ygrek (i=user@gateway/tor/x-990b50cdcd787efb) joined #forth 23:59:59 --- log: ended forth/08.02.19