00:00:00 --- log: started forth/15.02.25 00:17:33 --- quit: MrMobius (Read error: Connection reset by peer) 00:22:36 --- join: xyh (~xieyuheng@222.58.73.34) joined #forth 00:55:05 --- quit: mnemnion (Remote host closed the connection) 01:12:44 --- quit: fox__ (Quit: fox__) 01:37:10 --- quit: bjorkintosh (Ping timeout: 252 seconds) 01:44:57 --- join: ttmrichter-ln (~ttmrichte@114.111.167.18) joined #forth 01:48:26 I'm thinking of reversing the usual parse in my Forth by having the number recognizer go before the dictionary look-up. Why is this a bad idea? 01:50:21 because then you can't do : 2 4 ; to ensure job security. :) 01:52:40 I'm my own job securer. No other reason then? 01:54:54 okay, what about 'bad' ? 01:54:56 BAD 01:55:27 (because you can change the base in forth) 01:56:19 That's a word. A hex number would be $bad. 01:57:57 (One of my first design decisions was to ditch implicit bases.) 01:58:46 then i think you're good. 01:59:04 what about 2dup, etc? 02:04:13 --- quit: ttmrichter-ln (Ping timeout: 244 seconds) 02:18:23 --- quit: xyh (Remote host closed the connection) 02:22:23 ttmrichter: do you celebrate the lunatic new year? 02:32:33 --- join: ttmrichter-xm (~ttmrichte@113.57.246.250) joined #forth 02:33:46 --- join: nighty (~nighty@hokuriku.rural-networks.com) joined #forth 02:33:49 --- quit: nighty-_ (Ping timeout: 250 seconds) 02:48:49 --- quit: ttmrichter-xm (Remote host closed the connection) 02:49:16 --- join: ttmrichter-xm (~ttmrichte@113.57.246.250) joined #forth 02:53:17 --- join: nisstyre (~yourstrul@li611-52.members.linode.com) joined #forth 02:53:26 --- join: bjorkintosh (~bjork@ip68-13-229-200.ok.ok.cox.net) joined #forth 03:02:11 --- quit: ttmrichter-xm (Remote host closed the connection) 04:01:08 --- quit: nighty (Excess Flood) 04:02:33 --- join: nighty (~nighty@hokuriku.rural-networks.com) joined #forth 04:16:58 --- join: proteusguy (~proteusgu@180.183.127.68) joined #forth 04:16:59 --- mode: ChanServ set +v proteusguy 05:18:35 most likely a silly question but is anyone aware of a commonly used forth "library" for dealing with JSON data? or does everyone just implement it on their own (which is what I anticipate the answer is) when they need JSON? 05:20:32 The reason why I ask is because http://json.org lists a ton of JSON implementations for a large list of languages and I thought it would be nice to have a forth option published there as well. 05:21:26 --- join: Zarutian (~Adium@168-110-22-46.fiber.hringdu.is) joined #forth 05:23:11 only thing I've found is https://code.google.com/p/ffl/wiki/jis which is strictly a parser and doesn't seem to help you create json structures. 05:27:08 Forth doesnt have data structures per se as I understand it, making translation of JSON objects and arrays a bit tad difficult 05:35:50 --- join: xyh (~xieyuheng@222.58.73.34) joined #forth 05:39:42 --- quit: xyh (Remote host closed the connection) 06:20:31 The Chuck Moore answer to that would be "why would you use a format as grotesquely inefficient and complicated as JSON?" 06:38:43 --- join: mnemnion (~mnemnion@c-98-210-219-91.hsd1.ca.comcast.net) joined #forth 06:41:24 --- quit: mnemnion (Remote host closed the connection) 06:41:31 --- join: mnemnion (~mnemnion@c-98-210-219-91.hsd1.ca.comcast.net) joined #forth 06:48:53 ttmrichter, my answer would be so I can expose my awesome forth apps as RESTful web services to be consumed by anyone on the internet. It actually is one of the few use cases where the "generic standard" provides an extremely high value. 06:50:44 Zarutian, actually parsing strings and composing them is extremely easy to do in forth. Doesn't mean you need to implement the data structures that JSON proposes directly - just that you can marshal/de-marshal your app's data/operations into a JSON representation. 07:00:13 --- join: xyh (~xieyuheng@222.58.73.34) joined #forth 07:01:25 proteusguy: You will recall that Chuck didn't play well with others for his career. :) 07:04:28 haha sure - I'm a big fan of Moore's. But he isn't as irrational as you make our. He's all about making things as simple as possible and not introducing unnecessary complexity. I agree he's not likely to be the guy to suggest a RESTful web service in JSON is the way to go but even he appreciates certain architectural drivers and elegant solutions and would likely implement a more efficient transport format than JSON but still support the concept of R 07:04:29 EST. 07:04:59 proteusguy: Oh, I don't think he's irrational. I think he's a very strong iconoclast, though. 07:05:07 He's not huge on pomp and ceremony. 07:12:18 agreed. 07:13:06 --- join: johnmark_ (~johnmark@c-73-51-235-57.hsd1.il.comcast.net) joined #forth 07:21:05 --- quit: darkf (Quit: gn) 08:43:11 --- join: gabriel_laddel (~user@unaffiliated/gabriel-laddel/x-9909917) joined #forth 08:57:06 --- quit: gabriel_laddel (Remote host closed the connection) 09:32:06 --- quit: xyh (Remote host closed the connection) 09:53:42 --- join: xtalmath (~xtalmath@ip-83-134-182-165.dsl.scarlet.be) joined #forth 10:13:29 --- quit: Zarutian (Quit: Leaving.) 10:14:13 --- quit: proteusguy (Ping timeout: 250 seconds) 10:21:13 --- quit: nighty^ (Remote host closed the connection) 10:32:20 --- join: Mat4 (~claude@ip18861915.dynamic.kabel-deutschland.de) joined #forth 10:32:23 hi all 10:39:31 --- join: proteusguy (~proteusgu@ppp-110-168-229-147.revip5.asianet.co.th) joined #forth 10:39:31 --- mode: ChanServ set +v proteusguy 11:38:53 --- quit: xtalmath (Quit: Leaving.) 12:28:40 --- quit: Mat4 (Remote host closed the connection) 13:18:56 --- join: nighty^ (~nighty@static-68-179-124-161.ptr.terago.net) joined #forth 13:44:05 --- join: ehaliewicz (~user@204.11.226.50.static.etheric.net) joined #forth 13:44:24 --- join: Mat4 (~claude@ip18861915.dynamic.kabel-deutschland.de) joined #forth 14:28:24 --- quit: mnemnion (Remote host closed the connection) 14:29:36 --- join: mnemnion (~mnemnion@c-98-210-219-91.hsd1.ca.comcast.net) joined #forth 14:34:05 --- quit: mnemnion (Ping timeout: 272 seconds) 14:41:00 --- quit: impomatic (Read error: Connection reset by peer) 14:51:13 --- quit: true-grue (Read error: Connection reset by peer) 14:52:32 --- quit: blandflakes (Quit: Page closed) 15:07:18 ciao 15:07:22 --- quit: Mat4 (Quit: Verlassend) 15:59:48 --- join: mnemnion (~mnemnion@c-98-210-219-91.hsd1.ca.comcast.net) joined #forth 16:18:56 --- quit: ehaliewicz (Remote host closed the connection) 16:29:23 --- quit: Quozl`_ (Read error: Connection reset by peer) 16:32:59 --- join: Quozl` (~quozl@activation.laptop.org) joined #forth 17:14:24 --- quit: nighty (Quit: Disappears in a puff of smoke) 17:48:15 --- join: darkf (~darkf___@unaffiliated/darkf) joined #forth 17:49:27 --- join: fox__ (~fox@119.2.12.162) joined #forth 18:33:12 --- join: MrMobius (~Joey@c-68-45-16-225.hsd1.nj.comcast.net) joined #forth 18:36:23 --- join: saml_ (~saml@cpe-24-102-97-97.nyc.res.rr.com) joined #forth 18:44:23 --- quit: fox__ (Quit: fox__) 18:44:52 --- join: fox__ (~fox@119.2.12.162) joined #forth 19:09:08 --- quit: mnemnion (Remote host closed the connection) 19:18:39 --- join: mnemnion (~mnemnion@c-98-210-219-91.hsd1.ca.comcast.net) joined #forth 19:23:32 --- quit: mnemnion (Ping timeout: 272 seconds) 20:29:32 --- quit: nisstyre (Changing host) 20:29:32 --- join: nisstyre (~yourstrul@oftn/member/Nisstyre) joined #forth 21:09:56 --- quit: johnmark_ (Quit: Leaving) 22:10:16 --- quit: saml_ (Remote host closed the connection) 22:52:08 --- quit: proteusguy (Remote host closed the connection) 23:14:26 --- join: nighty-_ (~nighty@hokuriku.rural-networks.com) joined #forth 23:19:45 --- join: proteusguy (~proteusgu@180.183.127.68) joined #forth 23:19:55 --- mode: ChanServ set +v proteusguy 23:59:59 --- log: ended forth/15.02.25