00:00:00 --- log: started forth/14.11.12 00:06:09 --- quit: proteusguy (Ping timeout: 258 seconds) 00:09:14 --- join: true-grue (~grue@95-25-94-251.broadband.corbina.ru) joined #forth 00:21:37 --- join: proteusguy (~proteusgu@180.183.110.217) joined #forth 00:39:31 --- quit: MrM0bius (Read error: Connection reset by peer) 00:49:19 --- quit: clog (Ping timeout: 250 seconds) 00:49:19 --- log: stopped forth/14.11.12 00:51:08 --- log: started forth/14.11.12 00:51:08 --- join: clog (~nef@bespin.org) joined #forth 00:51:08 --- topic: 'Forth Programming | logged by clog at http://bit.ly/91toWN | isforth.com | forthfreak.net | http://forthworks.com/standards/DPANS/ | www.greenarraychips.com' 00:51:08 --- topic: set by I440r!~mark4@cpe-192-136-220-10.tx.res.rr.com on [Thu Jan 02 15:51:09 2014] 00:51:08 --- names: list (clog proteusguy true-grue nighty-_ beretta samrat klltkr_ impomatic_ protist backer ErhardtTheWhite DGASAU impomatic Anarch DocPlatypus joneshf-laptop joneshf rixard nighty^ ggherdov` +bluekelp john_metcalf bbloom yiyus Adeon karswell aksatac KipIngram bjorkintosh Quozl` carc TodPunk irsol enthos cataska C-Keen ricky_ricardo nisstyre Zag nox crc diginet nottwo_ malyn_ yunfan ttmrichter djinni koisoke krainboltgreene dzho malyn newcup rprimus_ tangentstorm) 00:51:08 --- names: list (danfinch) 00:58:40 --- quit: proteusguy (Ping timeout: 264 seconds) 00:59:40 --- join: proteusguy (~proteusgu@180.183.110.217) joined #forth 01:06:03 --- quit: proteusguy (Remote host closed the connection) 01:10:29 --- join: proteusguy (~proteusgu@180.183.110.217) joined #forth 01:10:29 --- quit: clog (Ping timeout: 245 seconds) 01:10:29 --- log: stopped forth/14.11.12 01:17:45 --- log: started forth/14.11.12 01:17:45 --- join: clog (~nef@bespin.org) joined #forth 01:17:45 --- topic: 'Forth Programming | logged by clog at http://bit.ly/91toWN | isforth.com | forthfreak.net | http://forthworks.com/standards/DPANS/ | www.greenarraychips.com' 01:17:45 --- topic: set by I440r!~mark4@cpe-192-136-220-10.tx.res.rr.com on [Thu Jan 02 15:51:09 2014] 01:17:45 --- names: list (clog proteusguy true-grue nighty-_ beretta samrat klltkr_ impomatic_ protist backer ErhardtTheWhite DGASAU impomatic Anarch DocPlatypus joneshf-laptop joneshf rixard nighty^ ggherdov` +bluekelp john_metcalf bbloom yiyus Adeon karswell aksatac KipIngram bjorkintosh Quozl` carc TodPunk irsol enthos cataska C-Keen ricky_ricardo nisstyre Zag nox crc diginet nottwo_ malyn_ yunfan ttmrichter djinni koisoke krainboltgreene dzho malyn newcup rprimus_ tangentstorm) 01:17:45 --- names: list (danfinch) 01:17:45 -hitchcock(freenode.net)- [freenode-info] please register your nickname...don't forget to auto-identify! http://freenode.net/faq.shtml#nicksetup 03:21:37 --- log: started forth/14.11.12 03:21:37 --- join: clog (~nef@bespin.org) joined #forth 03:21:37 --- topic: 'Forth Programming | logged by clog at http://bit.ly/91toWN | isforth.com | forthfreak.net | http://forthworks.com/standards/DPANS/ | www.greenarraychips.com' 03:21:37 --- topic: set by I440r!~mark4@cpe-192-136-220-10.tx.res.rr.com on [Thu Jan 02 15:51:09 2014] 03:21:37 --- names: list (clog samrat true-grue nighty-_ beretta klltkr_ protist backer ErhardtTheWhite DGASAU impomatic Anarch DocPlatypus joneshf-laptop joneshf rixard nighty^ ggherdov` +bluekelp john_metcalf bbloom yiyus Adeon karswell aksatac KipIngram bjorkintosh Quozl` carc TodPunk irsol enthos cataska C-Keen ricky_ricardo nisstyre Zag nox crc diginet nottwo_ malyn_ yunfan danfinch tangentstorm rprimus_ newcup malyn dzho krainboltgreene koisoke djinni ttmrichter) 03:28:25 --- join: proteusguy (~proteusgu@ppp-110-168-229-200.revip5.asianet.co.th) joined #forth 03:46:58 --- quit: impomatic (Ping timeout: 258 seconds) 03:48:24 --- quit: samrat (Quit: Computer has gone to sleep.) 03:49:21 --- join: samrat (~samrat@61.12.96.226) joined #forth 04:06:15 --- join: impomatic (~chatzilla@235.198.208.46.dyn.plus.net) joined #forth 04:12:33 --- quit: samrat (Quit: Computer has gone to sleep.) 04:34:09 --- quit: ErhardtTheWhite (Read error: Connection reset by peer) 04:41:49 --- join: ErhardtMundt (~quassel@93-43-71-119.ip90.fastwebnet.it) joined #forth 05:18:59 --- quit: joneshf-laptop (Ping timeout: 240 seconds) 05:19:35 --- quit: joneshf (Ping timeout: 244 seconds) 05:20:05 --- join: impomatic_ (~chatzilla@235.198.208.46.dyn.plus.net) joined #forth 05:22:58 --- quit: impomatic (Ping timeout: 256 seconds) 05:23:02 --- nick: impomatic_ -> impomatic 05:26:39 --- join: Zarutian (~zarutian@168-110-22-46.fiber.hringdu.is) joined #forth 05:27:29 --- quit: Zarutian (Read error: Connection reset by peer) 05:27:46 --- join: Zarutian (~zarutian@168-110-22-46.fiber.hringdu.is) joined #forth 05:29:38 --- join: MrMobius (~Joey@c-98-223-189-47.hsd1.in.comcast.net) joined #forth 05:34:11 --- quit: impomatic (Ping timeout: 255 seconds) 05:35:50 --- join: impomatic (~chatzilla@235.198.208.46.dyn.plus.net) joined #forth 05:36:47 --- join: samrat (~samrat@123.236.183.195) joined #forth 06:58:21 --- join: xyh (~xieyuheng@2001:250:3002:5550:6ea1:cc0f:bcb2:b187) joined #forth 07:41:12 --- join: bbloom_ (~bbloom@cpe-68-175-72-82.nyc.res.rr.com) joined #forth 07:44:18 --- quit: bbloom (Ping timeout: 255 seconds) 07:59:42 --- quit: samrat (Quit: Computer has gone to sleep.) 08:00:44 --- join: samrat (~samrat@123.236.183.195) joined #forth 08:13:01 --- quit: xyh (Ping timeout: 265 seconds) 08:18:47 --- join: jabb (~grue@51B6C310.dsl.pool.telekom.hu) joined #forth 08:18:48 yo 08:22:00 --- join: xyh (~xieyuheng@2001:250:3002:5550:6ea1:cc0f:bcb2:b187) joined #forth 08:22:05 is this wrong: " : add for 1+ next ; " ? 08:28:52 --- join: spoofer (~cruella@72.10.28.164) joined #forth 08:39:46 What's a good non-ans Forth that has C FFI? Reva is giving me trouble. 08:54:55 jabb: why a non-ANS Forth? 08:57:40 jabb: retroforth.org 09:00:48 DocPlatypus: I disagree with the philosophy behind it :P 09:01:32 there's a reason that, for example, there's a standard for C 09:01:35 and C++, etc 09:01:55 and that any language intended to run on more than one type of computer, eventually gets some kind of standardization 09:01:57 Forth is no different 09:02:43 is ANS perfect? no, but it's the best standard available until 200x/201x is done 09:02:56 There's a reason why similar standard exists for Forth too. 09:03:30 exactly 09:03:34 There's a reason why similar standards exist for other programming languages with more than one implementation. 09:04:31 what makes it the best standard? 09:04:40 I agree for rigid syntaxes, like C. But not for something like Forth where you're building a DSL. 09:05:05 It doesn't matter on how rigid the syntax is. 09:05:26 of course, you're free to redefine ANS words to be what you want them to 09:05:40 but don't be surprised when other people that have to maintain your code later wonder what you were smoking 09:05:51 I'm aware. 09:06:05 I'm not the only one who has this belief. 09:06:19 Don't be surprised when other people who might use your code will call you a dick and never look at your code anymore. 09:07:10 ...that too 09:07:15 --- join: fantazo (~fantazo@2001:858:5:3a41:99d8:b33b:fce0:c986) joined #forth 09:07:52 (I would have said it more like that but normally I don't just drop vulgar terms for genitalia in a conversation) 09:08:15 We're not at court, aren't we? ;) 09:08:19 heh 09:08:54 Haha, well there are certainly advantages to a Forth standard, but large disadvantages too. 09:09:37 we needed something more than Forth 83 09:09:39 Should every Forth implementation adhere to the ANS standard regardless of the problem it's trying to solve? 09:09:52 and the changes between Forth 79 and Forth 83 needed to be resolved 09:10:12 Yes, it should at least in major parts. 09:10:16 If the problem is extremely simple. Do you really want to code an entire ANS wordset in assembly? 09:10:23 jabb: if they are going to provide functionality covered in the standard, they should make it accessible in the way the standard says to 09:10:39 ANS doesn't restrict you in your choice of implementation language. 09:10:47 the only thing the ANS standard guarantees you is the CORE wordlist. everything else is optional. 09:10:59 Right, but it's a large word list. 09:11:03 No, it isn't like that. 09:11:13 if a Forth implementation has no realistic way to do floating point, then by all means don't provide the FLOAT wordlist 09:11:30 If you implement words from other wordsets, ANS mandates that they behave in standard way, AFAICR. 09:11:52 ok... and what exactly is so wrong with that? 09:12:19 * tangentstorm prefers forth 83 for a variety of reasons... in particular, much better documentation. 09:12:22 In your terms, if your implementation doesn't do FPNs, you ought not to define "F+" to do something weird. 09:12:32 right, exactly 09:13:20 Right. Some common words should definitely behave the same. That doesn't mean full ANS compliance though. 09:13:31 dup, for example 09:13:50 definitely should always duplicate the top of the stack 09:16:36 what gets me are implementations that instead of using ANS standard LSHIFT, for example, it's << or something equally weird 09:17:24 I suppose they're used to C family languages? 09:17:38 yes but that's not what that word is supposed to be in Forth, per the ANS standard 09:17:47 if they want to write C they should go write C 09:18:22 it's like me putting a random, uncommon Spanish word in the middle of my English 09:18:43 not that I ever would of course 09:18:49 Languages borrow from other languages. 09:19:34 sometimes they do but there's already one standard for how to shift bits in Forth, and that's LSHIFT and RSHIFT 09:20:30 it would be one thing if it never existed in Forth before and the standard didn't define it 09:20:57 but it does, and in ANS Forth it's LSHIFT and RSHIFT, not << and >> or whatever 09:21:24 Right, so whatever implements LSHIFT and RSHIFT is ANS Forth, and whatever implements >> and << is a different Forth. 09:22:05 but why do it a non-standard way just because? 09:23:07 there really is no good reason to not use the words in the standard and make up a different word to do the same thing 09:24:07 in fact... at this point in time, any Forth which makes up its own words like that, for stuff defined in the ANS standard, I am tempted to say it's not a real Forth anymore 09:25:30 Perhaps they are modeling more of C's behavior with RSHIFT (keeping sign bit for signed numbers) 09:25:47 Where ANS's RSHIFT pushes 0's always. 09:26:10 we have that too, it's called 2/ 09:26:22 Do you disagree with Forth's inventor when he said he thought the ANS standard was a mistake? 09:26:40 what part of it did he think was a mistake? 09:26:58 and I don't see the people that invented C saying the ANSI/ISO C standards are a mistake 09:27:42 "The ANS Forth standard does not express Moore's vision of Forth. Moore believes the ANS standard is far too large and complex, and he doesn't see much value in any standard since people should write their own Forth. It is fair to say that most of the Forth community disagrees." 09:28:23 it's large and complex because there are words outside of CORE and even CORE-EXT that people need. everything outside of CORE is strictly speaking optional 09:28:36 Different philosophy behind the language. C is all about generality, but Moore is more about "problem-oriented" practices. Basically build everything that you need, and no more. 09:28:54 Moore's Forth* 09:29:17 to be fair I have wanted to figure out how to build a stripped-down GNU Forth that only has the words I need compiled in 09:30:25 I suggest reading his book "Programming a Problem Oriented Language" to better understand his thinking when he invented Forth. I do see the merits in a standard, but I don't think it's necessary to comply with them. 09:30:39 but the standard defines a lot of things that have been around since Forth 79 in some form 09:31:27 it's best to have standardized words for certain functionality if it is there, rather than having to guess what the implementor decided to call the word to open a file 09:31:48 For the very common words, yeah, I agree. 09:32:16 ANS Forth makes it so I can take my code written for GNU Forth and run it on another Forth system that's ANS compliant with a minimum of tweaking 09:32:30 most GNU-isms have standard replacements or they can easily be coded 09:32:44 words like ?dup-if for example 09:32:58 : ?dup-if postpone ?dup postpone if ; 09:33:28 Right. 09:33:43 I agree crap like |LOCALS| shouldn't have made it in 09:34:45 Yes, stuff like that promotes lazy Forth programming. 09:35:00 the successor to ANS Forth should either add mouse event handling to EKEY or otherwise add a way to access the mouse 09:35:20 I don't mind locals in general, they are the best way to solve certain problems, but |LOCALS| does it ass-backwards 09:36:10 the last proposals I saw, standardized {: ... :} instead of { ... } since some implementations stupidly chose to use the latter for something else 09:36:25 --- join: DKordic (~user@93-87-136-236.dynamic.isp.telekom.rs) joined #forth 09:37:11 it's the one case where I can say I would rather we just break the implementations that were that short-sighted than work around them 09:38:18 anyways the forth market isn't that large, it can afford to make a massive break here and there. 09:39:11 tangentstorm: retroforth doesn't load files? 09:39:20 well, it doesn't run files *well* 09:39:45 ? 09:39:55 works fine for me, jabb ? 09:42:11 when i run the file, it outputs every line of inputted text, including the "ok " 09:43:47 so? 09:44:00 you can turn it off 09:44:12 how? 09:45:30 https://github.com/tangentstorm/retro/commit/d1352ec6f513ed427581f059ed38393cd12b1a62 09:48:38 hmm 09:51:19 tangentstorm: i suppose this isn't in the packaged release? i should clone the repo 09:52:05 it'll be in the next released version 09:52:21 ahh 09:53:59 tangentstorm: is that change pushed upstream? 09:54:54 it's on launchpad 09:55:09 in crc's retro repository on the branch for the next version 09:55:11 --- join: joneshf-laptop (~joneshf@98.208.35.89) joined #forth 09:55:53 --- join: aranhoide (~smuxi@205.Red-83-52-6.dynamicIP.rima-tde.net) joined #forth 09:59:08 --- join: joneshf (~joneshf@98.208.35.89) joined #forth 09:59:14 --- quit: joneshf-laptop (Ping timeout: 240 seconds) 10:06:05 tangentstorm, you have sweet twitter account. 10:15:26 :) 10:15:31 thanks 10:50:03 --- join: vanila (~user@unaffiliated/vanila) joined #forth 10:53:01 --- quit: fantazo (Quit: Verlassend) 11:01:48 --- quit: samrat (Quit: Computer has gone to sleep.) 11:05:05 --- quit: xyh (Remote host closed the connection) 11:08:15 --- join: Azel (~Thunderbi@ANice-653-1-594-196.w86-193.abo.wanadoo.fr) joined #forth 12:02:49 --- quit: Zarutian (Quit: Zarutian) 12:06:50 --- quit: DKordic (Read error: Connection reset by peer) 12:11:07 --- join: DKordic (~user@93-87-136-236.dynamic.isp.telekom.rs) joined #forth 12:14:36 --- join: fantazo (~fantazo@089144195062.atnat0004.highway.a1.net) joined #forth 12:16:04 --- quit: DKordic (Read error: Connection reset by peer) 12:32:28 --- join: Mat3 (~Mat3@91.65.76.159) joined #forth 12:32:38 hi all 12:34:22 jabb: "Problem Oriented Language" is archaic shit. 12:40:49 I would also doubt that chuck moore is a very good designer of languages. he is a good designer of whole systems though, but his systems lack normally documentation. I mean colorforth is a good example. 12:48:37 --- join: DKordic (~user@93-87-136-236.dynamic.isp.telekom.rs) joined #forth 12:50:40 or isn't it? chuck's philosophy is to tailor everything to a specific circumstance. so there are no abstractions which can be reused. 13:01:04 His "philosophy" is about tailoring everything manually under premises that manual polishing results in more effective code. 13:01:16 This is what this "POL" is about. 13:01:32 It worked in sixties, 13:02:00 "when disks were large and memories were small," 13:02:25 but it stopped working after people found good parsing and optimisation algorithms. 13:07:16 hmm, I think an important aspect is the minimal effort to implement a Forth environment. This and the flexibility to extend (bootstrap) this minimal system in a platform independent way (theoretical). This gives programmers freedom to scale up applications dependent freely dependent on resource usage 13:07:46 sorry, editor garbage 13:08:34 "This and the flexibility to extend (bootstrap) this minimal system in a platform independent way (theoretical) gives programmers freedom to scale up applications dependent dependent on the resource usage" 13:08:51 * Mat3 gives up line editing 13:09:50 I still appreciate the simple structure of a forth system. but building big systems with it is more of a bad idea. 13:12:41 I disagree, there are some examples of really large Forth systems which are well maintainable (the problem is that such projects are generally not known in public) 13:16:31 well, maybe. I don't see them. But what from the open code out there written in ans forth and co, it is not that well written. 13:17:45 for example people start writing very long definitions, which contain stack comments in itself. and if that is the open code base, then I ask myself what is the closed one? 13:19:36 my opinion is that Chuck Moore's philosophy is not understandable without the fact, that building (or porting) a forth system is a simple task in combination that the language grants flexibility to extend such environments dependent on application usage. I think that is the reason why he seem to be sceptical about standardisation (well I guess so to be precise) 13:20:51 I must say, I have written two forth systems, but I haven't yet ported one from one architecture to another. 13:21:29 and yes, you can program quite fantastic bad in Forth (specially if you are familiar in common languages such as C) 13:23:58 people normally don't split up the problems small enough so that they have one to three lines of definition code. 13:26:28 Mat3, so what is in your opinion a prime example for well written forth? 13:29:42 the one solution from Rod Pemberton (do not know is that a pseudonym or real name) from comp.lang.forth for example: https://groups.google.com/forum/#!topic/comp.lang.forth/M8Dyp2z1Rfg 13:33:00 * Mat3 founds reading this thread quite marcabre 13:33:45 DGASAU: Every philosophy has some merit, no philosophy becomes absolete. The context in which it helps remains the same. 13:34:25 s/help/applies 13:36:06 I have very minimalistic ideals, though, even with lifestyle. So I'm partly biased to keeping things small. 13:36:55 --- quit: DGASAU (Remote host closed the connection) 13:38:41 --- join: DGASAU (~user@p50993595.dip0.t-ipconnect.de) joined #forth 13:40:43 --- join: jabb_ (~grue@51B68478.dsl.pool.telekom.hu) joined #forth 13:40:47 stupid connection 13:41:40 --- nick: jabb_ -> jab 13:41:48 Implementing Forth environment is one-time problem, and it is irrelevant to building systems on top of it. 13:42:01 It is especially irrelevant to building scalable systems on top of it. 13:43:49 --- quit: jabb (Ping timeout: 255 seconds) 13:45:49 Implementing a Forth environment isn't the "problem" it solves. Implementing DSLs is a one-time thing too. 13:46:33 Not in the way CM tells about. 13:46:33 --- quit: TodPunk (Read error: Connection reset by peer) 13:46:51 --- join: TodPunk (~Tod@50-198-177-186-static.hfc.comcastbusiness.net) joined #forth 13:47:05 Implementing a Forth environment is like, step 1 of 2 of solving a problem. 13:47:22 Step 1: Implement a Forth environment tailored to your needs, step 2: solve the problem. 13:47:58 Compare it to alternative approach: 13:48:22 step 1: pick more appropriate programming language and _reuse_ already existing implementation, 13:48:35 step 2: solve the problem a lot more effectively. 13:49:04 E.g. by reusing a lot of library code. 13:49:55 DGASAU: our logic is: x → P1 AND P2; y → P2 NOT P3, so x → p1 AND (P2 → NOT P3); Because P2 → NOT P3 = NOT P3 you really say: x → P1 AND NOT P2. (Congratulations) 13:50:40 I make somewhat useful, ciao 13:51:08 --- part: Mat3 left #forth 13:51:09 DGASAU: Existing implementation written in the appropriate programming language? 13:51:10 Your logic is based on weird operation that you denote as "x NOT y". 13:51:47 --- quit: TodPunk (Read error: Connection reset by peer) 13:52:12 --- join: TodPunk (Tod@50-198-177-186-static.hfc.comcastbusiness.net) joined #forth 13:52:23 Sure, that works. Assuming the appropriate language is available to you, which it almost certainly is now days. 13:53:06 When it is "almost certainly is," there's nothing to assume. 13:53:08 --- join: quuxman (~ac@ec2-54-221-173-57.compute-1.amazonaws.com) joined #forth 13:53:22 I use Forth mostly as an extension to a language anyway. 13:53:28 If I were to try out Forth for the first time, and like to play with graphics and maybe even audio, which interpreter should I start with? 13:53:41 Why are you to try Forth out? 13:53:44 --- quit: true-grue (Read error: Connection reset by peer) 13:53:46 Is it your job? 13:53:48 I'm interested in languages 13:53:54 Forth is bad language. 13:54:00 I'm about to install gforth 13:54:14 I tried processing audio some time ago in Forth. 13:54:17 It sucks. 13:54:26 ok whatever, I guess I'm in the wrong channel 13:54:29 quuxman: gforth is a good start 13:54:30 You have more appropriate languages for it. 13:54:43 DGASAU: nothing wrong with being experimental 13:54:53 I think you missed "< quuxman> I'm interested in languages" 13:54:59 In particular, ones that support FRP or other form of event or dataflow processing. 13:55:32 quuxman: he's kidding, he loves forth, that's why he's in this channel 13:55:53 --- quit: TodPunk (Read error: Connection reset by peer) 13:56:11 --- join: TodPunk (Tod@50-198-177-186-static.hfc.comcastbusiness.net) joined #forth 13:56:33 Besides, whatever implementation you choose, you have to confront the problem of FFI. :) 13:57:02 quuxman: another one is factor, it's a less traditional forth, but it comes with a lot more libraries to play around with 13:57:06 In the end you'll be translating whatever you know into RPN. 13:57:11 gforth? 13:57:24 gforth is one of the most traditional implementations. 13:57:30 DGASAU: factor 13:57:43 Factor isn't Forth even. 13:58:02 it's a concatenative language with forth-like syntax 13:58:12 Well... It may help you dealing with memory allocation, 13:58:35 but otherwise, you'll still be fighting RPN and stack. 13:58:51 anyway, bbl, drinking a beer and leaving the computer :P 13:59:12 quuxman: goodluck! 13:59:41 --- quit: TodPunk (Read error: Connection reset by peer) 13:59:52 Yeah, you'll need it. :) 14:00:08 --- join: TodPunk (~Tod@50-198-177-186-static.hfc.comcastbusiness.net) joined #forth 14:05:24 --- quit: TodPunk (Read error: Connection reset by peer) 14:05:41 --- join: TodPunk (~Tod@50-198-177-186-static.hfc.comcastbusiness.net) joined #forth 14:06:18 --- quit: TodPunk (Read error: Connection reset by peer) 14:06:43 --- join: TodPunk (Tod@50-198-177-186-static.hfc.comcastbusiness.net) joined #forth 14:11:06 --- quit: TodPunk (Read error: Connection reset by peer) 14:11:23 --- join: TodPunk (~Tod@50-198-177-186-static.hfc.comcastbusiness.net) joined #forth 14:25:40 --- quit: nighty-_ (Quit: Disappears in a puff of smoke) 14:30:30 --- join: jab_ (~grue@4E5C554D.dsl.pool.telekom.hu) joined #forth 14:32:39 --- quit: jab (Ping timeout: 272 seconds) 14:42:04 I've already messed with Factor, and wasn't so happy with the OO system 14:42:08 but maybe I should try it again 14:42:47 DGASAU: hey, RPN isn't something I fight. Some of my earliest code was written on a HP 32SII RPN calculator 14:43:14 then an HP 48G 14:45:00 I have a hard time with any OO system 14:47:22 I was attracted to the elegance of Forth, but I guess Factor is actually a version of Forth 14:49:38 I get "Library: DLL" /usr/lib/libgtk-x11-2.0.so.0"; Symbol: gtk_init ; DlError: none" from factor when attempting to run it 14:50:00 seems like a mismatch with my version of libgtkglext1? or something more obvious. I should go to #factor 14:51:51 quuxman: I had the same problem. A link is missing on some distributions 14:52:14 it's libgtk-x11-2.0.so.0.5 or something 14:52:28 I just ln'd my way through it 15:01:07 --- quit: vanila (Remote host closed the connection) 15:06:17 --- join: vanila (~user@unaffiliated/vanila) joined #forth 15:23:56 --- join: aranhoide_ (~smuxi@100.Red-79-152-56.dynamicIP.rima-tde.net) joined #forth 15:24:31 --- quit: aranhoide (Ping timeout: 264 seconds) 15:38:04 --- join: jab (~grue@4E5C505D.dsl.pool.telekom.hu) joined #forth 15:41:02 --- quit: jab_ (Ping timeout: 240 seconds) 16:05:07 --- join: Zarutian (~zarutian@168-110-22-46.fiber.hringdu.is) joined #forth 16:07:56 --- join: aranhoide (~smuxi@9.Red-95-123-58.staticIP.rima-tde.net) joined #forth 16:08:07 --- quit: aranhoide_ (Ping timeout: 245 seconds) 16:18:11 --- quit: aranhoide (Ping timeout: 255 seconds) 16:18:26 --- join: aranhoide (~smuxi@59.Red-88-19-104.staticIP.rima-tde.net) joined #forth 16:20:37 http://www.reddit.com/r/Forth/comments/2m48mj/here_comes_philae_powered_by_an_rtx2010_forth/ 16:20:53 neat! didnt know that the RTX2010 was still in active use. 16:23:50 cool 16:26:43 * Zarutian linked to the reddit posting because there was an link to stack machines book there also in a comment. 16:27:08 jab: so maybe symlink /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 to /usr/lib/libgtk-x11-2.0.so.0 ? 16:43:36 --- quit: klltkr_ (Ping timeout: 250 seconds) 16:50:53 --- quit: aranhoide (Ping timeout: 250 seconds) 16:55:09 --- quit: impomatic (Ping timeout: 255 seconds) 17:14:00 --- join: klltkr (~klltkr@unaffiliated/klltkr) joined #forth 17:21:31 --- quit: klltkr (Ping timeout: 264 seconds) 17:24:16 --- join: klltkr (~klltkr@unaffiliated/klltkr) joined #forth 17:47:48 --- quit: spoofer (Ping timeout: 255 seconds) 17:50:26 --- quit: Zarutian (Quit: Zarutian) 18:00:51 --- join: spoofer (~cruella@72.10.28.164) joined #forth 18:36:19 --- join: yiyus_ (1242712427@je.je.je) joined #forth 18:40:08 --- quit: yiyus (Ping timeout: 258 seconds) 19:01:03 --- quit: spoofer (Quit: Leaving) 19:39:26 --- join: Zarutian (~zarutian@168-110-22-46.fiber.hringdu.is) joined #forth 19:58:19 --- join: evincar (~jon@173-228-12-162.dsl.dynamic.fusionbroadband.com) joined #forth 20:08:13 yunfan - that's what I do. But having znc in the loop back when I used Android made it smoother to connect from multiple clients. 20:08:39 Yes - I run a screen session on my virtual server and remote into it when I want to chat. 20:10:21 --- join: crc_ (sid2647@gateway/web/irccloud.com/x-kmadvfgtxeovkvfw) joined #forth 20:11:04 --- join: samrat (~samrat@123.236.183.195) joined #forth 20:13:06 --- join: nox_ (sid3872@gateway/web/irccloud.com/x-indcmmxjpyzizdrc) joined #forth 20:13:38 --- join: evincar_ (~jon@173-228-12-162.dsl.dynamic.fusionbroadband.com) joined #forth 20:14:13 --- quit: evincar_ (Client Quit) 20:16:06 --- quit: crc (Ping timeout: 272 seconds) 20:16:08 --- quit: nox (Ping timeout: 272 seconds) 20:16:08 --- quit: evincar (Ping timeout: 272 seconds) 20:16:08 --- quit: bluekelp (Ping timeout: 272 seconds) 20:16:08 --- quit: yiyus_ (Ping timeout: 272 seconds) 20:16:10 --- quit: john_metcalf (Ping timeout: 272 seconds) 20:16:10 --- join: john_metcalf (~john_metc@235.198.208.46.dyn.plus.net) joined #forth 20:16:13 --- nick: crc_ -> crc 20:16:19 --- join: yiyus (1242712427@je.je.je) joined #forth 20:16:57 --- nick: nox_ -> nox 20:17:53 --- join: bluekelp (~bluekelp@2001:470:1:41:341f:99ad:5a78:237b) joined #forth 20:17:53 --- mode: ChanServ set +v bluekelp 20:23:55 I use mosh/buffer 3 20:24:01 ooops. 20:24:27 I use mosh. It works a lot like an ssh session, but automatically reconnects after a drop. 20:34:08 --- quit: Zarutian (Quit: Zarutian) 20:44:37 --- join: jab_ (~grue@51B6BF19.dsl.pool.telekom.hu) joined #forth 20:46:39 KipIngram: i have ssh client on android too :] 20:47:09 KipIngram: yes mosh are more useful to people like me who live behind the GFW 20:47:29 --- quit: jab (Ping timeout: 258 seconds) 20:47:31 the cross country link's speed are not that quick than your westen country user 20:55:55 --- quit: samrat (Ping timeout: 255 seconds) 20:57:46 --- join: samrat (~samrat@123.236.183.195) joined #forth 21:03:57 --- quit: samrat (Quit: Computer has gone to sleep.) 21:07:28 --- join: jab (~grue@54027CF7.dsl.pool.telekom.hu) joined #forth 21:11:03 --- quit: jab_ (Ping timeout: 272 seconds) 21:28:34 --- quit: vanila (Quit: Leaving) 21:43:08 --- join: ErhardtTheWhite (~quassel@93-43-90-94.ip91.fastwebnet.it) joined #forth 21:45:39 --- quit: ErhardtMundt (Ping timeout: 245 seconds) 21:47:10 --- join: true-grue (~grue@95-27-254-45.broadband.corbina.ru) joined #forth 21:48:18 --- join: samrat (~samrat@61.12.96.226) joined #forth 21:50:33 --- join: ErhardtMundt (~quassel@93-43-163-57.ip92.fastwebnet.it) joined #forth 21:53:54 --- quit: ErhardtTheWhite (Ping timeout: 255 seconds) 22:21:15 --- quit: DKordic (Quit: ERC Version 5.3 (IRC client for Emacs)) 22:51:38 --- quit: true-grue (Read error: Connection reset by peer) 22:58:05 --- join: true-grue (~grue@95-27-254-45.broadband.corbina.ru) joined #forth 23:54:47 --- quit: true-grue (Read error: Connection reset by peer) 23:59:59 --- log: ended forth/14.11.12