00:00:00 --- log: started forth/08.09.19 00:05:40 --- quit: gnomon (Read error: 60 (Operation timed out)) 00:06:54 --- join: aum (n=aum@60-234-243-247.bitstream.orcon.net.nz) joined #forth 00:15:09 --- quit: proteusguy (Read error: 110 (Connection timed out)) 00:15:51 --- join: proteusguy (n=proteusg@61.7.144.97) joined #forth 00:37:51 --- join: qFox (i=C00K13S@132pc222.sshunet.nl) joined #forth 01:07:57 --- join: prunedtree (i=Aozaru@195.140.142.184) joined #forth 01:08:02 hello 01:30:36 in your experience, is it easy to do extensive compiler analysis on forth code (very regular code that doesn't do strange dataflow) ? 01:31:58 like constant propagation, code motion, loop unrolling... 02:57:21 I don't think it's too difficult, but I don't know of any Forth system that does... 02:57:29 Check out Factor though (factorcode.org). 02:57:48 and there are papers on Joy, I believe... 02:59:07 --- quit: aum ("Leaving") 02:59:37 well, my question is essentially about any threaded-code 03:00:18 I'm wondering if much semantics are lost, or if you can rebuild decent semantics for flow control like loops from them 03:05:18 I don't think you'd lose much of anything. 03:06:03 Especially since, if you're writing the compiler, you'd design it so that you didn't. :) 03:06:44 Basic threaded code is pretty much just a tokenization of the source. 03:10:33 OK, time to go milk the cow... 03:20:21 --- quit: nighty__ (Read error: 104 (Connection reset by peer)) 06:24:24 --- quit: proteusguy (Read error: 110 (Connection timed out)) 06:25:15 --- join: proteusguy (n=proteusg@61.7.144.97) joined #forth 06:40:26 --- quit: MalfermitaKodo (Read error: 104 (Connection reset by peer)) 06:45:36 --- join: MalfermitaKodo (n=kansu@xdsl-78-34-138-110.netcologne.de) joined #forth 07:18:28 --- quit: ASau` (Remote closed the connection) 07:56:51 --- join: gnomon (n=gnomon@CPE001d60dffa5c-CM000f9f776f96.cpe.net.cable.rogers.com) joined #forth 08:01:43 --- join: TreyB (n=trey@74.203.168.157) joined #forth 08:34:17 --- quit: mathrick (Excess Flood) 08:34:44 --- join: mathrick (n=mathrick@users177.kollegienet.dk) joined #forth 08:36:41 --- quit: erg (zelazny.freenode.net irc.freenode.net) 08:38:04 --- join: erg (n=erg@li13-154.members.linode.com) joined #forth 08:47:03 --- quit: segher (Read error: 110 (Connection timed out)) 09:26:43 --- quit: ecraven ("bbl") 09:30:39 --- quit: TreyB (Read error: 110 (Connection timed out)) 09:32:55 --- join: ramkrsna (n=ramkrsna@unaffiliated/ramkrsna) joined #forth 09:56:27 --- join: segher (n=segher@84-105-61-45.cable.quicknet.nl) joined #forth 10:19:28 --- quit: prunedtree () 10:41:04 --- join: Aozaru (i=Aozaru@195.140.142.184) joined #forth 10:43:20 --- join: ecraven (n=nex@cm207-109.liwest.at) joined #forth 10:53:14 --- quit: ecraven ("bl") 11:07:05 --- part: Aozaru left #forth 11:54:34 --- quit: kspaans (Read error: 104 (Connection reset by peer)) 12:13:33 --- join: Maki_ (n=Maki@adsl-224-84.eunet.yu) joined #forth 13:10:13 --- quit: ramkrsna ("Leaving") 14:00:01 --- join: edrx (i=edrx@189.25.119.163) joined #forth 14:09:18 --- nick: edrx -> edrx2 15:05:42 --- join: TreyB (n=trey@74.203.168.157) joined #forth 15:31:45 --- quit: Maki_ ("Leaving") 16:14:37 --- quit: qFox ("Time for cookies!") 16:32:56 --- join: aguai_ (n=aguai@122-116-183-8.HINET-IP.hinet.net) joined #forth 17:11:48 --- join: gogonkt`1 (n=info@125.34.36.29) joined #forth 17:21:50 --- quit: TreyB (Read error: 113 (No route to host)) 17:31:28 --- quit: gogonkt`` (Read error: 110 (Connection timed out)) 18:53:17 --- quit: tathi ("leaving") 19:32:00 --- quit: MalfermitaKodo (Read error: 104 (Connection reset by peer)) 19:36:47 --- join: MalfermitaKodo (n=kansu@xdsl-78-34-137-80.netcologne.de) joined #forth 21:43:12 --- nick: aguai_ -> aguai 21:58:28 --- part: aguai left #forth 23:30:29 --- quit: edrx2 (Read error: 110 (Connection timed out)) 23:33:25 --- join: ramkrsna (n=ramkrsna@unaffiliated/ramkrsna) joined #forth 23:59:59 --- log: ended forth/08.09.19