00:00:00 --- log: started forth/01.05.15 00:06:58 * aaronl is away: out to lunch 00:07:32 * aaronl is back (gone 04:51:20) 00:42:17 --- quit: colorg (Ping timeout for colorg[humbubba.smart.net]) 00:49:50 --- quit: lar1 (varley.openprojects.net zelazny.openprojects.net) 00:49:50 --- quit: TreySleeping (varley.openprojects.net zelazny.openprojects.net) 00:49:50 --- quit: nate37 (varley.openprojects.net zelazny.openprojects.net) 00:49:51 --- quit: aaronl (varley.openprojects.net zelazny.openprojects.net) 00:50:10 --- join: TreySleeping (Baxter@ns.TreySoft.com) joined #forth 00:50:10 --- join: lar1 (lar1@adsl-63-204-134-234.dsl.snfc21.pacbell.net) joined #forth 00:50:10 --- join: aaronl (aaronl@vitelus.com) joined #forth 00:50:10 --- join: nate37 (nate@cx83983-d.irvn1.occa.home.com) joined #forth 01:12:36 * aaronl is away: sleep/school 01:47:08 --- quit: nate37 (goodnight) 03:04:32 --- quit: lar1 (zelazny.openprojects.net tolkien.openprojects.net) 03:04:52 --- join: lar1 (lar1@adsl-63-204-134-234.dsl.snfc21.pacbell.net) joined #forth 03:41:19 --- quit: lar1 (varley.openprojects.net farmer.openprojects.net) 03:41:20 --- quit: TreySleeping (varley.openprojects.net farmer.openprojects.net) 03:41:20 --- quit: aaronl (varley.openprojects.net farmer.openprojects.net) 03:41:35 --- join: TreySleeping (Baxter@ns.TreySoft.com) joined #forth 03:41:35 --- join: aaronl (aaronl@vitelus.com) joined #forth 03:41:35 --- join: lar1 (lar1@adsl-63-204-134-234.dsl.snfc21.pacbell.net) joined #forth 06:59:34 --- join: grurp (grurp@pc19951.batc.tec.ut.us) joined #forth 08:13:02 --- nick: TreySleeping -> Trey 08:21:49 --- nick: Trey -> TreyAway 09:02:11 --- join: aaronl_ (aaronl@vitelus.com) joined #forth 09:15:59 --- quit: aaronl_ (9) nanoseconds) 09:53:45 --- nick: TreyAway -> Trey 13:29:33 --- quit: grurp (Bye all) 14:11:48 --- join: Fare (fare@ppp38-net1-idf2-bas1.isdnet.net) joined #forth 16:58:23 * aaronl is back (gone 15:45:47) 17:01:03 --- join: blandest (not@h24-65-136-122.ed.shawcable.net) joined #forth 17:02:15 --- quit: Fare (Leaving) 17:02:55 --- part: blandest left #forth 17:22:36 --- join: nate37 (nate@cx83983-d.irvn1.occa.home.com) joined #forth 17:57:08 * aaronl is away: I'm busy 18:28:49 * aaronl is back (gone 00:31:41) 18:52:09 --- join: TheBlueWizard (TheBlueWiz@ip-216-25-202-124.vienna.va.fcc.net) joined #forth 18:52:09 --- mode: ChanServ set mode: +o TheBlueWizard 18:52:13 hiya all 19:21:33 got to go....bye 19:21:36 --- part: TheBlueWizard left #forth 19:21:59 --- join: SirDibos (djw@207.6.134.17) joined #forth 19:36:25 aaronl: I'm here already 19:36:46 interpretation isn't all evil. in fact, it often leads to huge savings 19:36:54 it allows extreme compression 19:37:09 and if you can stay within your cpus cache memory, that is a HUGE win 19:37:19 next step down, if you can avoid touching the harddrive, that is a HUGE win. 19:37:25 smaller generally does == faster 19:37:44 and with interpretation, the simpler the interpreter is, the faster it is. 19:37:52 coz it has less work to do. 19:37:55 hmm 19:38:09 when you define a word, the interpreter "compiles" the code on the spot. 19:38:14 if the interpreted code is faster than the compiled code, well, then, it certainly ain't perl :) 19:38:28 aaronl: you're unecessarily distinguishing them. 19:38:30 they work together. 19:38:43 interpreter compiles code, then gives the kickstart to the main() routine 19:38:50 from there on in, its all compiled code. 19:39:03 the interpeter itself, by the simple design of the language, is blazing fast 19:39:19 right 19:39:27 i'm talking about JIT code vs. precompiled code 19:39:47 aaronl: in fact, its as fast to compile the code on the fly, as it is to load the compiled binary from disk 19:39:58 what is JIT? 19:40:02 no, forget JIT. 19:40:07 thats a bunch of nonsense. 19:40:12 compile the code when it is defined, thats it. 19:40:47 s/JIT/On the fly/ 19:41:14 what is on the fly and what isn't? 19:41:29 forth is fundamentally both interpreted and compiled AT THE SAME TIME. 19:41:36 concepts like JIT just don't apply to it 19:42:10 ok 19:43:17 being able to write some small forth code, then pipe it into the compiler which runs it... that is very cool. 19:43:34 and if you pipe nothing in, then you can just type from stdin and experiment that way. 19:45:03 the hardest thing will be getting it to compile itself, then output that to stdout or something. 19:45:58 forth < forth.4 > forth.new 19:49:22 hm. need to have a compile word that apples to a symbol, say 'main, then outputs a forth system that can execute that word. 19:49:39 then you could have your compiled binaries as well. 19:49:46 I bet they'd still be really small. 19:50:20 how hard can it be to trace dependancies in forth and copy out only the things a particular word requires to run? 19:57:49 --- quit: SirDibos ([BX] Life is like BitchX. Ya never know what yer gunna git.) 21:28:40 --- nick: Trey -> TreySleeping 22:32:57 --- join: antonio_ (antonio@212.34.222.62) joined #forth 22:39:27 --- quit: nate37 (later) 23:18:49 --- join: edrx (edrx@200.240.18.51) joined #forth 23:27:01 --- part: edrx left #forth 23:59:59 --- log: ended forth/01.05.15