00:00:00 --- log: started forth/17.02.22 00:33:29 --- quit: ACE_Recliner (Remote host closed the connection) 00:35:23 --- quit: mnemnion (Remote host closed the connection) 02:19:05 --- quit: proteusguy (Remote host closed the connection) 03:02:56 --- join: proteusguy (~proteus-g@49.228.95.102) joined #forth 03:02:56 --- mode: ChanServ set +v proteusguy 03:06:20 --- nick: cajg_ -> cajg 03:06:30 --- quit: nighty (Quit: Disappears in a puff of smoke) 04:47:50 --- join: nighty (~nighty@s229123.ppp.asahi-net.or.jp) joined #forth 05:27:38 --- join: GeDaMo (~GeDaMo@212.225.112.221) joined #forth 05:59:46 --- join: mnemnion (~mnemnion@2601:643:8102:7c95:f891:4ecb:20ac:94a9) joined #forth 06:04:02 --- quit: mnemnion (Ping timeout: 240 seconds) 06:19:55 --- join: Zarutian (~zarutian@168-110-22-46.fiber.hringdu.is) joined #forth 06:35:39 --- quit: Zarutian (Quit: Zarutian) 07:04:50 --- join: neceve (~ncv@86.125.230.85) joined #forth 07:04:51 --- quit: neceve (Changing host) 07:04:51 --- join: neceve (~ncv@unaffiliated/neceve) joined #forth 07:05:13 I'm thinking about changing move so that the destination comes first 07:06:23 I find that I almost always have to shuffle the source and destination around a move. usually I already have a destination address, and then I call some word to get a source and length 07:06:36 /around/around before/ 07:41:46 --- join: MrBusiness (~ArcMrBism@104-50-90-48.lightspeed.brhmal.sbcglobal.net) joined #forth 08:49:11 --- join: gravicappa (~gravicapp@ppp83-237-170-25.pppoe.mtu-net.ru) joined #forth 08:51:34 --- quit: neceve (Quit: Konversation terminated!) 09:30:53 --- join: rgrinberg (~rgrinberg@24-246-56-85.cable.teksavvy.com) joined #forth 10:07:18 --- quit: gravicappa (Ping timeout: 260 seconds) 10:21:45 --- join: mnemnion (~mnemnion@104.6.70.118) joined #forth 10:28:00 --- join: gravicappa (~gravicapp@ppp83-237-160-20.pppoe.mtu-net.ru) joined #forth 11:07:58 --- join: proteus-guy (~proteus-g@49.228.111.47) joined #forth 11:11:19 --- quit: proteusguy (Ping timeout: 240 seconds) 11:44:11 --- join: ACE_Recliner (~ACE_Recli@c-50-165-178-74.hsd1.in.comcast.net) joined #forth 11:48:34 --- quit: ACE_Recliner (Ping timeout: 260 seconds) 11:51:46 --- join: ACE_Recliner (~ACE_Recli@c-50-165-178-74.hsd1.in.comcast.net) joined #forth 12:20:28 --- quit: gravicappa (Ping timeout: 268 seconds) 12:36:09 --- join: luser1 (~user@h69-21-248-248.crlbnm.broadband.dynamic.tds.net) joined #forth 13:25:28 --- quit: GeDaMo (Remote host closed the connection) 13:55:26 --- quit: true-grue (Read error: Connection reset by peer) 14:12:24 --- part: luser1 left #forth 14:24:45 --- join: vsg1990 (~vsg1990@static-72-88-80-103.bflony.fios.verizon.net) joined #forth 15:03:53 --- quit: rgrinberg (Ping timeout: 255 seconds) 15:15:55 --- quit: nighty (Quit: Disappears in a puff of smoke) 15:49:25 --- join: Zarutian (~zarutian@168-110-22-46.fiber.hringdu.is) joined #forth 16:56:24 --- join: nighty (~nighty@d246113.ppp.asahi-net.or.jp) joined #forth 17:24:10 --- join: neceve (~ncv@unaffiliated/neceve) joined #forth 17:25:39 --- quit: dograt (Quit: No Ping reply in 180 seconds.) 17:26:57 --- join: dograt (~dograt@unaffiliated/dograt) joined #forth 17:28:53 --- quit: mnemnion (Remote host closed the connection) 17:36:11 --- quit: Zarutian (Quit: Zarutian) 17:48:33 --- join: mnemnion (~mnemnion@2601:643:8102:7c95:b0f6:ea92:1649:afb5) joined #forth 17:51:21 --- quit: mnemnion (Remote host closed the connection) 17:51:38 --- join: mnemnion (~mnemnion@2601:643:8102:7c95:b0f6:ea92:1649:afb5) joined #forth 19:27:46 how does one do double-precision multiplication/division (trying to analyze some time measurement data) 19:28:13 (in gforth) 19:42:27 reepca: usually it's done with mixed precision because of overflows and whatnot: http://www.public.iastate.edu/~forth/gforth_10.html#SEC14 19:42:31 but... 19:43:21 Lehs wrote a forth bignum library that runs rather fast: https://github.com/Lehs/BIG-INTEGER-ANS-FORTH 19:43:44 I use it for forth-crypt 19:46:16 I'm not really seeing how I could use mixed precision to go from a double-precision number to that same number times 1000. 19:46:26 --- quit: impomatic (Ping timeout: 260 seconds) 19:46:34 : ud* >r swap >r over over um* rot r> * + rot r> * + ; 19:46:49 --- join: impomatic (~impomatic@host86-164-38-224.range86-164.btcentralplus.com) joined #forth 19:46:50 2 s>d 3 s>d ud* d. 19:48:17 that's an awful lot of stack manipulation to parse 19:49:03 yeah it's ugly. Found it here: https://groups.google.com/forum/#!topic/comp.lang.forth/IuXIpGRDsmg 20:02:47 If you already have a handful of variables used throughout your code, you could use those. Here's a locals implementation from that thread, easily adapted to use possibly pre-existing variables, : d* { al ah bl bh -- cl ch } al bl um* al bh * + ah bl * + ; 20:38:19 --- join: proteusguy (~proteus-g@49.228.113.171) joined #forth 20:38:20 --- mode: ChanServ set +v proteusguy 20:41:19 --- quit: proteus-guy (Ping timeout: 260 seconds) 20:51:56 --- quit: neceve (Quit: Konversation terminated!) 21:28:52 --- quit: vsg1990 (Quit: Leaving) 21:30:36 --- quit: proteusguy (Remote host closed the connection) 21:31:33 --- join: mnemnia (~mnemnion@2601:643:8102:7c95:b0f6:ea92:1649:afb5) joined #forth 21:33:23 --- quit: mnemnion (Ping timeout: 240 seconds) 22:15:15 --- join: wa5qjh (~Thunderbi@121.54.90.139) joined #forth 22:24:06 --- join: phpsux (97ecaa31@gateway/web/freenode/ip.151.236.170.49) joined #forth 22:24:25 Why should I use Forth? 22:35:24 phpsux: Forth is an interactive compiled language, compile-time execution, that is. This means compiling is exposed to the user. This in turn means that you don't need the dragon book telling you how to tokenize, build an abstract syntax tree etc, etc. 22:36:03 That and implicit parameter passing make the language low fat and simple. 22:36:17 https://www.reddit.com/r/Forth/comments/55b8ta/what_makes_immediate_mode_the_key_to_everything/d8bs6bq/ 22:39:19 The problem is, Forth doesn't have a serious, active, and big implementation, whereas C/C++ have LLVM and GCC, Intel CC, etc... 22:46:15 phpsux: Forth doesn't need a central implementation, like say, python, because it's easy enough to write your own forth as needed. Just take only the ideas from other forths that make your forth a better fit for the problem at hand. 23:03:51 --- quit: phpsux (Ping timeout: 260 seconds) 23:07:29 --- join: gravicappa (~gravicapp@ppp83-237-160-20.pppoe.mtu-net.ru) joined #forth 23:14:49 --- join: proteusguy (~proteus-g@180.183.116.228) joined #forth 23:14:49 --- mode: ChanServ set +v proteusguy 23:16:26 --- quit: wa5qjh (Remote host closed the connection) 23:19:38 --- join: wa5qjh (~Thunderbi@121.54.90.139) joined #forth 23:44:47 --- quit: wa5qjh (Read error: Connection reset by peer) 23:46:36 --- join: wa5qjh (~Thunderbi@121.54.90.139) joined #forth 23:55:01 --- quit: wa5qjh (Remote host closed the connection) 23:58:29 --- join: wa5qjh (~Thunderbi@121.54.90.139) joined #forth 23:59:59 --- log: ended forth/17.02.22