00:00:00 --- log: started forth/07.11.23 00:01:27 --- join: ecraven (i=nex@eutyche.swe.uni-linz.ac.at) joined #forth 00:53:55 --- join: LOOP-HOG (n=jasondam@c-76-105-172-75.hsd1.or.comcast.net) joined #forth 01:04:56 --- quit: LOOP-HOG () 01:08:40 --- join: forther (n=forther@c-67-180-150-67.hsd1.ca.comcast.net) joined #forth 01:17:32 --- quit: forther ("Leaving") 01:57:41 --- quit: Crest (Read error: 110 (Connection timed out)) 02:30:58 --- quit: Al2O3 ("Eggplant & SenseTalk: Driving Success Through Automation") 02:38:37 --- join: Crest (n=crest@p5B106723.dip.t-dialin.net) joined #forth 02:41:50 --- join: Al2O3 (n=Al2O3@c-75-70-5-69.hsd1.co.comcast.net) joined #forth 02:57:22 --- join: doublec (n=doublec@203-97-173-6.cable.telstraclear.net) joined #forth 03:03:46 --- join: Al2O3_ (n=Al2O3@68.sub-70-215-63.myvzw.com) joined #forth 03:17:47 --- quit: Al2O3 (Read error: 110 (Connection timed out)) 03:50:27 --- quit: Off_Namuh (Remote closed the connection) 03:50:58 --- quit: doublec () 05:04:11 --- quit: ecraven ("bbl") 05:42:58 --- join: edrx (i=edrx@189.25.10.204) joined #forth 05:43:58 --- part: edrx left #forth 06:06:34 --- quit: timlarson (Read error: 110 (Connection timed out)) 06:16:29 --- join: forther (n=forther@c-67-180-150-67.hsd1.ca.comcast.net) joined #forth 06:28:35 --- join: timlarson (n=timlarso@user-12l37rb.cable.mindspring.com) joined #forth 06:52:24 --- join: KipIngram (n=KipIngra@c-98-196-82-10.hsd1.tx.comcast.net) joined #forth 06:54:03 --- part: KipIngram left #forth 07:02:41 --- quit: forther (Read error: 110 (Connection timed out)) 07:03:18 --- join: forther (n=forther@c-67-180-150-67.hsd1.ca.comcast.net) joined #forth 07:30:11 --- quit: forther (Read error: 110 (Connection timed out)) 07:41:32 --- join: manic12_ (n=manic12_@71.194.18.28) joined #forth 07:42:15 --- join: manic12__ (n=manic12_@c-71-194-18-28.hsd1.il.comcast.net) joined #forth 07:42:31 since I am feeling uninspired to code any lisp today, I would like to learn something about FORTH 07:43:13 right now I am trying to find a FORTH setup for x86_64 07:43:18 any suggestions? 07:59:22 --- quit: manic12_ (Read error: 110 (Connection timed out)) 08:00:29 --- join: manic12_ (n=manic12_@c-71-194-18-28.hsd1.il.comcast.net) joined #forth 08:17:09 --- quit: manic12__ (Read error: 110 (Connection timed out)) 08:17:40 check if gforth has an x86_64 build 08:30:07 --- join: gnomon (n=gnomon@CPE0050eb372bdb-CM000f9f776f96.cpe.net.cable.rogers.com) joined #forth 08:31:20 yeah it does, for linux, I'm trying that one, thx 08:31:39 maybe for windoze too, i haven't checked yet 08:32:43 this is like one of those HP calculators (was it HP?) 08:35:13 Both are RPN. 08:38:12 I was at my old job and they handed me some code from the early 90s for running a machine (a mechanical machine) and it was FORTH 08:39:54 I think that it is cool that FORTH has been used in manufacturing & CAM, because then supervisors can't say that it wouldn't work 08:40:50 it's too bad that the structured text programs from programmable logic controls are not forth 08:45:23 are nip and tuck standard? 08:53:09 yes. 08:53:53 forth must be where they got the name for the tv show 09:29:11 --- quit: Quartus__ (Read error: 104 (Connection reset by peer)) 09:52:42 --- join: Off_Namuh (i=GPS@gateway/tor/x-1dade1beddf3d8eb) joined #forth 09:57:13 if you have 1 2 3 4 on the stack, is it possible to manipulate the 1 with only drop, dup, over, swap and rot? I'm not seeing it if it is possible. 09:57:42 somebody make me say, oh duh! 10:00:13 --- join: Al2O3 (n=Al2O3@c-75-70-5-69.hsd1.co.comcast.net) joined #forth 10:05:00 --- quit: Al2O3_ (Read error: 110 (Connection timed out)) 10:23:19 --- join: Al2O3_ (n=Al2O3@180.sub-70-215-129.myvzw.com) joined #forth 10:36:10 --- quit: Al2O3 (Read error: 110 (Connection timed out)) 10:39:49 --- quit: Quartus (Read error: 110 (Connection timed out)) 10:39:52 --- join: Quartus (n=neal@CPE0001023f6e4f-CM001947482b20.cpe.net.cable.rogers.com) joined #forth 10:39:52 --- mode: ChanServ set +o Quartus 11:01:57 --- join: forther (n=forther@c-67-180-150-67.hsd1.ca.comcast.net) joined #forth 11:14:14 --- join: ygrek (i=user@gateway/tor/x-dbed256632af2508) joined #forth 11:18:03 --- quit: forther ("Leaving") 11:32:33 --- join: magnus_ (n=magnus@pool-71-175-153-27.phlapa.east.verizon.net) joined #forth 12:26:39 --- join: Quartus__ (n=Quartus_@209.167.5.1) joined #forth 12:38:28 --- quit: Off_Namuh (Read error: 104 (Connection reset by peer)) 12:42:14 manic, it's not; nor should you need to. 12:47:14 ok 12:54:13 --- join: Raystm2 (n=Ray@unaffiliated/raystm2) joined #forth 12:56:40 --- quit: Quartus__ ("used jmIrc") 12:56:55 --- join: Quartus__ (n=Quartus_@209.167.5.1) joined #forth 12:58:10 Ideally, items on the stack should be in the order in which they'll be consumed. 13:00:11 --- join: Al2O3 (n=Al2O3@97.sub-70-215-54.myvzw.com) joined #forth 13:12:41 * Raystm2 is thinking that should be a/the Forth Commandment. 13:14:43 --- quit: Al2O3 ("Eggplant & SenseTalk: Driving Success Through Automation") 13:20:50 --- quit: Al2O3_ (Read error: 110 (Connection timed out)) 13:22:08 --- join: Al2O3 (n=Al2O3@116.sub-70-219-207.myvzw.com) joined #forth 13:35:28 --- quit: ygrek (Remote closed the connection) 13:40:14 --- join: doublec (n=doublec@203-97-173-6.cable.telstraclear.net) joined #forth 13:46:34 --- join: charles54 (n=charles@CPE-61-9-139-165.static.vic.bigpond.net.au) joined #forth 13:50:29 --- quit: doublec () 14:03:55 --- join: doublec (n=doublec@203-97-173-6.cable.telstraclear.net) joined #forth 14:10:12 --- quit: doublec () 14:10:15 --- join: Off_Namuh (i=GPS@gateway/tor/x-0622fda5552da804) joined #forth 15:00:50 --- join: crest_ (n=crest@p5B1060B5.dip.t-dialin.net) joined #forth 15:17:41 --- quit: Crest (Read error: 110 (Connection timed out)) 15:32:55 i'm finding tons of tutorials and implementations of forth, but I haven't found too many applications I can analyze 15:35:01 is there a pseudo-standard oop system for forth? (gforth) i.e. like CLOS or something? 15:47:40 --- quit: Al2O3 (Read error: 110 (Connection timed out)) 15:48:31 there is almost too much stuff on the web 15:48:38 (about forth) 16:21:30 --- quit: Deformative (Remote closed the connection) 16:26:47 --- join: Deformative (n=joe@c-68-61-240-49.hsd1.mi.comcast.net) joined #forth 16:59:31 anybody here? 17:00:43 * crc is lurking in the background 17:01:54 i'm a complete newbie to forth, and i can't figure out why i can't get objects to work 17:10:04 something started working all of a sudden 17:20:19 --- join: Al2O3 (n=Al2O3@224.sub-70-215-23.myvzw.com) joined #forth 18:24:08 In the typical Forth style, several OOP packages exist. Each does just enough to get what the author needs out of the paradigm for a particular use, and very little more. 18:24:34 ok 18:24:42 i'm trying oof right now 18:26:26 i really think I'm getting ahead of myself though 18:27:30 there doesn't happen to be a book like "Forth for Lisp Programmers" ? 18:36:52 Not that I know of. 18:39:31 this isn't like anything I've done before, even Lisp, except for the fact that it uses a neutral/user defined syntax 18:42:31 I've looked back through the channel history, but I don't understand what you want to do. 18:43:42 --- quit: Quartus__ (Read error: 104 (Connection reset by peer)) 18:44:24 I've just been surfing for forth stuff and reading the gforth manual and "thinking forth" and I am just conversing (to myself apparently) how I can sink my teeth into this subject 18:48:11 You might try Starting Forth, updated for ANS: http://home.iae.nl/users/mhx/sf.html 18:48:23 ok, thx 18:48:47 Alternatively, you could set yourself a simple programming task and work through it in Forth. 18:49:05 Some aspects of Forth, like many things, you'll learn better by doing. 18:50:49 it took me ten years to get to what I consider an "intermediate" knowledge of Lisp, so I believe you 18:57:20 --- quit: Quartus (Read error: 110 (Connection timed out)) 18:57:30 --- join: Quartus (n=neal@CPE0001023f6e4f-CM001947482b20.cpe.net.cable.rogers.com) joined #forth 18:57:30 --- mode: ChanServ set +o Quartus 19:26:18 manic12_: there's a forth version of part of sicp in the ctm wiki 19:34:25 manic12_: about 1 2 3 4 --- it's quite easy to get at the 1: drop drop swap 19:34:35 Isn't most of it not even in forth? 19:34:49 most of the forth version of sicp? 19:34:53 Yes. 19:35:20 i haven't read through it all, but it looked like the parts that were not in english were mostly in forth. 19:35:36 What about the lambda parts? 19:36:03 anonymous functions? i didn't look hard enough to see how those were handled 19:36:22 [edit] 19:36:22 // 1.3.2 Formulating Abstractions with Higher-Order Procedures - Constructing Procedures Using Lambda 19:36:22 function pi_sum_2(a, b) { 19:36:22 return sum( 19:36:36 Starts going into javascript. 19:36:37 heh, that's part that hasn't been translated from js yet 19:36:48 how do you get the 3 4 back 19:36:49 --- quit: Raystm2 ("Should have paid the bill.") 19:37:03 that only works if you don't need them any more :) 19:37:04 manic12_: there's also the return stack, but I don't feel like I know Forth well enough to give advice on when it's a good idea to use it 19:37:09 Forth cannot do lambdas, can it? 19:37:37 Deformative: well, there's :noname, and you can always do lambda-lifting, and create...does> is a lot like closures 19:37:51 but none of them are exactly the same thing as having scheme-style lambdas in your language 19:38:06 Eh. 19:39:11 create...does> is probably the most similar in spirit 19:40:24 PostScript and Factor have lexical closures I think 19:41:00 Piff. 19:42:23 manic12_: so you can do >r >r swap, but the other answer is usually beter 19:42:24 better 19:43:41 * Deformative holds a grudge against factor because I thought I had new ideas about my language design, then I found out factor already implemented most of them. 19:43:54 haha 19:44:14 I still like my spec better though, so I am making my language anyways. 20:44:32 --- quit: Deformative (Remote closed the connection) 20:45:22 --- join: Deformative (n=joe@c-68-61-240-49.hsd1.mi.comcast.net) joined #forth 21:04:09 --- quit: Deformative (Remote closed the connection) 21:04:56 --- join: Deformative (n=joe@c-68-61-240-49.hsd1.mi.comcast.net) joined #forth 21:06:01 --- join: LOOP-HOG (n=jasondam@c-76-105-172-75.hsd1.or.comcast.net) joined #forth 21:33:12 --- join: Al2O3_ (n=Al2O3@4.sub-70-215-239.myvzw.com) joined #forth 21:42:55 --- quit: LOOP-HOG () 21:46:27 --- quit: Al2O3 (Read error: 110 (Connection timed out)) 21:51:09 --- join: ass_lover (n=blimy@cpe-76-167-152-135.socal.res.rr.com) joined #forth 21:51:26 how does one learn forth and then learn colorforth? 21:51:36 ansi seems to be far from colorforth 21:58:38 no one alive tonight eh 21:58:39 :) 22:03:47 --- nick: ass_lover -> math_lover 22:31:52 --- join: tits_loover (n=blimy@cpe-76-167-152-135.socal.res.rr.com) joined #forth 22:33:00 --- nick: tits_loover -> math_guy88 22:49:59 --- quit: math_lover (Read error: 110 (Connection timed out)) 22:52:55 --- join: math_lover (n=blimy@cpe-76-167-152-135.socal.res.rr.com) joined #forth 23:01:20 --- quit: math_guy88 (Read error: 110 (Connection timed out)) 23:10:22 --- join: math_guy88 (n=blimy@cpe-76-167-152-135.socal.res.rr.com) joined #forth 23:17:24 --- quit: Al2O3_ (Remote closed the connection) 23:18:07 --- quit: math_lover (Read error: 110 (Connection timed out)) 23:18:14 --- join: Al2O3 (n=Al2O3@4.sub-70-215-239.myvzw.com) joined #forth 23:18:15 --- quit: Al2O3 (Remote closed the connection) 23:24:08 --- join: math_lover (n=blimy@cpe-76-167-152-135.socal.res.rr.com) joined #forth 23:31:51 --- quit: math_guy88 (Read error: 110 (Connection timed out)) 23:38:27 --- join: forther (n=forther@c-67-180-150-67.hsd1.ca.comcast.net) joined #forth 23:38:49 --- join: Al2O3 (n=Al2O3@109.sub-70-215-166.myvzw.com) joined #forth 23:53:34 --- join: math_guy88 (n=blimy@cpe-76-167-152-135.socal.res.rr.com) joined #forth 23:59:59 --- log: ended forth/07.11.23