00:00:00 --- log: started forth/07.08.18 00:42:26 --- join: ygrek (i=user@gateway/tor/x-b692915059a7f60b) joined #forth 02:03:52 --- quit: ygrek ("Leaving") 02:09:23 --- join: ygrek (i=user@gateway/tor/x-bdd2c81f245d8aa1) joined #forth 02:52:05 --- join: ecraven (i=nex@eutyche.swe.uni-linz.ac.at) joined #forth 03:30:39 --- quit: ecraven ("bbl") 04:57:59 --- join: H4n1 (n=Hans@p57A0F2FA.dip.t-dialin.net) joined #forth 05:02:53 --- quit: bojangles (Remote closed the connection) 05:03:25 --- join: bojangles (n=duncan@ip68-226-187-82.lf.br.cox.net) joined #forth 05:16:04 --- quit: H4ns (Read error: 110 (Connection timed out)) 05:22:13 --- join: ecraven (i=nex@eutyche.swe.uni-linz.ac.at) joined #forth 08:46:36 --- quit: arcus ("Ex-Chat") 09:34:11 --- join: saon (n=saon@unaffiliated/saon) joined #forth 09:55:55 --- join: jns_ (n=jens@p57B07308.dip.t-dialin.net) joined #forth 10:02:56 --- quit: jns (Read error: 113 (No route to host)) 10:08:21 --- join: tetonca (n=chris@66.155.140.223) joined #forth 10:25:40 --- join: snoopy_1711 (i=snoopy_1@dslb-084-058-179-058.pools.arcor-ip.net) joined #forth 10:29:12 --- quit: jns_ (Read error: 113 (No route to host)) 10:33:52 --- quit: Snoopy42 (Read error: 145 (Connection timed out)) 10:33:59 --- nick: snoopy_1711 -> Snoopy42 10:40:54 hi. 10:41:07 hi 10:41:44 what's new? 10:42:21 not much, i haven't wandered into here in a matter of months i suppose 10:42:37 not that i did much more than idle even then 10:42:38 =p 10:42:44 nobody to blame but yourself :) 10:43:23 i've found myself in orlando at college majoring in computer engineering 10:43:44 fun? 10:44:05 classes haven't started yet, but i imagine it will be, yes 10:44:19 good deal 10:44:51 mostly i changed from computer science to computer engineering because i'd get access to labs and resources that'd be otherwise hard to obtain, whereas computer science materials are fairly easy to obtain these days 10:45:45 Considerable overlap at any rate. 10:46:21 pretty much yeah 10:49:19 forthing, any? 10:49:42 i haven't actually written any forth code in a while 10:50:00 i love the idea of it, and i really like pure forth, but i'm honestly a pretty terrible forth programmer 10:50:17 practice. 10:50:55 indeed indeed 10:51:11 i really want to write my own forth for practice and to do some experimenting with other ideas 10:51:31 I hold that improving your Forth improves your programming skills across the board. 11:00:35 hmm i agree with that 11:02:24 also that writing a Forth does not help improve your Forth skills 11:02:37 hmm really? 11:03:25 my most difficult problem was really understanding exactly how create, does>, and , worked 11:05:49 i figured studying a bit and implementing them would help 11:14:04 --- quit: ygrek (Remote closed the connection) 11:19:23 --- quit: Quartus__ ("used jmIrc") 11:19:36 --- join: Quartus__ (n=Quartus_@205.205.50.1) joined #forth 11:19:37 --- join: jns_ (n=jens@p57B07308.dip.t-dialin.net) joined #forth 11:19:51 hi, sorry -- did I miss anything? 11:21:13 indeed, I think writing a Forth before you become proficient at writing in Forth can be harmful 11:28:08 okay 11:38:13 hi hats. 11:38:17 oops. wrong c. 11:47:27 high hats 12:28:13 --- part: Joely left #forth 12:39:48 --- quit: tetonca ("User disconnected") 12:50:14 --- join: jns__ (n=jens@p57B07308.dip.t-dialin.net) joined #forth 12:53:36 saon create and , are easy but does> is a little harder 12:53:54 i understood how to USE does> for years before i understood how it worked lol 12:54:32 But you are a key example of my point: having built a specific implementation of DOES>, you are insistent that there is only one way to do it, and you depend on the specific implementatino. 12:54:35 its a little obfuscated but once u get ur head arround it its not that difficult 12:54:41 no 12:54:52 i didnt design my implementation of it 12:54:59 I didn't say you did. 12:55:25 ive seen other ways of doing it but i think the way i have it implemented is as good as any 12:55:36 show me a better way to do it and ill throw out my code 12:56:10 It isn't about relative merit, but you must admit you are highly resistant to the idea that other ways may be even equally valid, or perhaps more so, depending on the nature of the Forth itself 13:01:19 not all other cases but yes i resist SOME things 13:01:33 --- join: Quartus___ (n=neal@CPE0001023f6e4f-CM001947482b20.cpe.net.cable.rogers.com) joined #forth 13:01:45 my resistance for instance to a native optimizing compiler are only for ISFORTH. my arm compiler is going to be just that 13:02:10 i wanted isforth to be direct threaded and NON optimizing because the prime directive for isforth is for it to be easy to understand. 13:02:25 Well, I think back to a discussion of POSTPONE, in which you expressed amazement that some Forths may, necessarily, implement some words as IMMEDIATE that your own Forth implementation does not 13:02:29 i believe ive met that goal because ive heared many noobs in here tell me they understand it 13:02:39 i hate that word i even hate its name 13:02:48 i will never like it 13:03:10 My point does not relate to that word, nor its name 13:03:13 i may implement some as immediate that they dont too 13:03:46 theres nothing wrong with compile or [compile] and postpone is horrible methinks 13:03:58 My point has nothing to do with any of those three words. 13:04:22 then why did you bring them up 13:04:26 --- quit: jns_ (Read error: 113 (No route to host)) 13:06:02 you brought up two of them; I brought up POSTPONE as simple context to the discussion I was referencing. 13:18:26 --- quit: Quartus (Connection timed out) 13:39:24 --- join: jns_ (n=jens@p57B07308.dip.t-dialin.net) joined #forth 13:41:21 --- quit: jns__ (Read error: 113 (No route to host)) 14:53:16 --- nick: ecraven -> ecraven_ 14:53:19 --- nick: ecraven_ -> ecraven 15:01:34 --- quit: ecraven ("bbl") 15:01:41 --- join: crest_ (n=crest@p5489F2AE.dip.t-dialin.net) joined #forth 15:16:52 --- quit: crest__ (Read error: 110 (Connection timed out)) 15:25:40 --- join: Al2O3 (n=Al2O3@adsl-75-20-233-74.dsl.rcsntx.sbcglobal.net) joined #forth 15:26:09 --- quit: Quartus___ () 15:26:25 --- join: Quartus (n=neal@CPE0001023f6e4f-CM001947482b20.cpe.net.cable.rogers.com) joined #forth 15:26:25 --- mode: ChanServ set +o Quartus 15:40:48 --- join: tathi (n=josh@pdpc/supporter/bronze/tathi) joined #forth 15:40:56 --- mode: ChanServ set +o tathi 15:42:24 --- join: crest__ (n=crest@p5489CA07.dip.t-dialin.net) joined #forth 15:49:20 hey tathi 15:52:09 --- join: Crest (n=crest@p5489F01E.dip.t-dialin.net) joined #forth 15:55:04 --- quit: Al2O3 ("Eggplant & SenseTalk: Driving Success Through Automation") 15:55:23 --- quit: crest_ (Read error: 110 (Connection timed out)) 15:59:53 --- quit: crest__ (Success) 16:02:11 --- join: crest_ (n=crest@p5489C6BC.dip.t-dialin.net) joined #forth 16:05:28 Hi Quartus 16:10:19 --- quit: Crest (Connection timed out) 16:11:57 --- quit: Quartus__ (Read error: 104 (Connection reset by peer)) 16:47:35 how are things? 16:48:15 Things are OK 16:48:19 good :) 16:48:26 I took almost a whole day off yesterday :) 16:48:31 hey, good deal. 16:48:44 How's by you? 16:49:01 Could be worse. 17:13:23 --- quit: jns_ (Read error: 113 (No route to host)) 17:14:34 --- quit: nighty^ ("Disappears in a puff of smoke") 18:18:51 --- quit: Quartus (Read error: 110 (Connection timed out)) 18:21:01 --- join: arcus (n=ajt@121-73-23-172.cable.telstraclear.net) joined #forth 18:40:27 --- quit: tathi ("leaving") 19:09:16 --- join: mark4 (n=mark4__@ip70-190-68-238.ph.ph.cox.net) joined #forth 19:16:55 --- join: Quartus (n=neal@CPE0001023f6e4f-CM001947482b20.cpe.net.cable.rogers.com) joined #forth 19:16:55 --- mode: ChanServ set +o Quartus 19:26:39 --- quit: I440r_ (Read error: 110 (Connection timed out)) 20:13:45 --- quit: Baughn ("Aagh!") 20:14:03 --- join: Baughn (n=svein@2002:54ca:2640:0:0:0:0:1) joined #forth 20:57:49 --- quit: bojangles ("WeeChat 0.2.4") 23:05:03 --- quit: arcus ("Ex-Chat") 23:14:52 --- join: ygrek (i=user@gateway/tor/x-b41684a193f51fff) joined #forth 23:19:37 --- quit: Quartus (Read error: 110 (Connection timed out)) 23:40:54 --- join: jns_ (n=jens@p57B0541E.dip.t-dialin.net) joined #forth 23:59:59 --- log: ended forth/07.08.18