00:00:00 --- log: started forth/14.12.23 00:00:25 64k is a big chunk. You want that per CPU I presume. How many cores you looking to run? 00:04:33 well 64k is not big for PC level cpu 00:09:17 proteusguy: for your many core products, you at least need one big core for dispatching 00:22:21 --- join: true-grue (~grue@95-27-128-12.broadband.corbina.ru) joined #forth 00:24:54 --- join: darkf_ (~darkf___@unaffiliated/darkf) joined #forth 00:28:02 --- quit: darkf (Ping timeout: 258 seconds) 00:31:50 --- join: rixard (~rixard@host-95-199-26-119.mobileonline.telia.com) joined #forth 00:32:29 * rixard Has anyone here used Retro, specifically Retro-ios? 00:33:13 rixard: i have had used retro on adroid and retro extension for chome 00:33:23 but havent for ios 00:34:00 Maybe I am not understanding it fully, whenever I use accept or gets... 00:34:14 * rixard ...it never prompts for input 00:34:35 maybe it's supposed to be used with any i/o at all. 00:35:21 retro's pc version used to have io problem 00:35:48 maybe your ios apps met the same problem which unsolved or 00:36:00 but you could wait for crc's responding 00:36:40 in the ios-version you have a window with the editor which is persistent, and below that there is the output window. Maybe I am doing it all wrong. 00:37:07 I am not used to Retro, so I suspect there is a user error in the works 00:37:23 yunfan, there's no reason a dispatching core need be any bigger than the normal core. indeed sometimes there's no need for a dispatching core at all as it can be peer-to-peer in an async workflow. 00:37:32 i am sorry cant help you on this, although i have a ipad, i dont like it, so i only use it as a reading device 00:38:25 Yeah, no worries. I'll play around with it more when I get home. 00:38:39 proteusguy: i think maybe your conclution is true on embed domain 00:39:10 rixard: if you cant wait, just try retro for android and chrome 00:39:26 When I have tinkered with Retro in the past it would accept input as soon as the outer interpreter got whitespace 00:39:51 Yeah, I am in no hurry 00:40:08 maybe retro-ios isn't supposed to be interactive at all. 00:40:15 i like retor's nigro vm arch 00:40:45 also i am interesting of use forth like language as a embed lang 00:40:55 not like gforth does 00:44:25 oh well, I will check back in tomorrow 00:44:30 gotta tend to work 00:44:39 thanks for your pointers 00:44:48 --- quit: rixard (Quit: Colloquy for iPhone - http://colloquy.mobi) 00:46:21 --- quit: MrMobius_ (Ping timeout: 252 seconds) 00:50:04 --- join: nikki93 (~nikki93@37.208.132.20) joined #forth 00:50:45 hi all! I've recently been re-interested in and am learning lisp. the main things attracting me to it are macros (define ur own syntax!) and interactively developing stuff -- re-write and re-compile functions while program is running 00:50:54 would you say these are strengths of forth too? 00:51:15 my main interest is in developing interfaces for rapid game development 00:53:53 i would say so, yes... although everything feels much lower level in forth (at least to me) 00:54:47 nikki93: of course 00:55:16 sweet, I will definitely have to look into it. seems starting forth --> thinking forth --> ... is the usual way to go 01:04:50 nikki93: definitely not. 01:05:01 haha what 01:05:04 In Lisp you can perform program transformations very easily. 01:05:16 yup 01:05:19 In Forth you cannot do anything without major problems. 01:07:24 In order to develop interactively in any sensible way you need to have a lot of non-trivial support. 01:07:43 what do you like about forth? 01:07:57 I guess these things are such that you really gotta try em, but I'm curious 01:08:06 --- join: Azel (~Thunderbi@ANice-653-1-542-113.w86-205.abo.wanadoo.fr) joined #forth 01:08:42 nikki93: i think you could use it at your own purpose, like me i am interesting of emebed forth into server side socket programming 01:10:31 yunfan: I did that in past. It sucks. 01:10:46 But you can try and find it yourself. 01:11:59 ASau: i'd like use it at my own risk, but i am interesting of how you use it 01:12:26 I don't use it anymore. 01:12:40 And I'm not sure that software that used it still runs. 01:15:41 i want to know how you used it before 01:15:54 you could give me a overview of it 01:16:30 We had custom UDP service that performed elaborate switching of packets and processing them in between. 01:16:54 Originally it was thought that embedding programming language into it would be useful. 01:17:05 So I did that. 01:17:23 I took some programming language that was ready to be embedded and got it in. 01:17:42 The first mistake was that this language was Forth. 01:18:54 If you look at FreeBSD's boot loader, you'll see what Forth makes to your software. 01:19:49 then what about next? 01:19:50 Essentially, very few people can really program it and make any sense of it. 01:20:02 what's the problem of using forth under such case 01:20:15 It sucks as a programming language. 01:20:30 All you can use Forth for is writing interpreter. 01:20:39 Take a look at FreeBSD's boot loader. 01:20:58 that's there problem 01:21:09 --- nick: darkf_ -> darkf 01:21:12 i think i could use forth for my own projects 01:21:23 They have the same problem, only it is public code that you can learn from. 01:21:53 The second mistake is that the whole approach of embedding programming language interpreter into networking service is wrong. 01:22:11 ASau: then what about net filter? 01:22:19 they have a vm design 01:22:22 At least, you ought to consider what language you embed. 01:22:27 and be widely used 01:22:35 BPF is exactly the best demonstration of it. 01:22:44 also lua for nginx and lua for redis is popular 01:22:56 BPF programs can be and _are_ proved that they terminate. 01:23:29 Lua for Redis is completely different thing. 01:23:49 It isn't used for structural code. 01:24:05 It's a language to write triggers. 01:24:35 not only triggers 01:24:42 i am glad you have heard of it 01:24:59 and what about lua for nginx? 01:25:01 I have used it in projects. 01:25:07 its much more popular 01:25:13 so do i 01:25:17 nginx is popular. 01:25:30 and i saw some problem of redis, so i want to make a new one 01:25:34 As for lua in nginx, it is so popular that I haven't heard of it till today. 01:25:56 ASau: ok 01:26:03 I don't know how it is used. 01:26:13 Perhaps they use it as configuration format. 01:27:18 If it is so, then it makes some sense but it isn't embedding in common sense. 01:29:17 --- quit: mnemnion (Remote host closed the connection) 01:29:33 The reason is that you can do it with any language: 01:30:13 you expose data structures used to configure your software into implementation of selected programming language, 01:30:38 then you link this implementation against your software 01:31:32 so that once program exists, interpreter starts your program as a library with your configuration data set up. 01:33:52 All this is a lot simpler than developing and maintaining shared access to the same data structures in guest language. 01:37:06 Besides, Lua in Redis is one of the best demonstrations why this "NoSQL" is total failure as general concept. 01:38:05 nikki93, I would say that this iterative development style works well for lisp (scheme), forth, and erlang. You're basically creating a language to describe your own problem domain. Which language is best generally depends on the non-functional aspects of your problem domain. 01:39:37 If you write simple programs, you can use this "iterative development style" in any language. 01:39:39 Even in C. 01:39:54 You can do it even interactively in C. 01:39:59 nikki93, as our resident curmudgeon ASau points out - most people can't program complex system in forth well. But this is also true of lisp & erlang. The reason is that these languages require you to have a completely different mindset than most of the imperative programming languagaes out there. 01:41:00 Forth is imperative language, it doesn't support any other paradigm. 01:41:06 ASau, that's like saying you can problem object oriented system in C. Sure it's possible but the language isn't helping you do it. I'm a pretty hard core C++ guy (been doing it since 1989) and I would not approach a project in that way with C or C++. 01:41:13 In CL you can program in imperative style with little effort. 01:41:15 I guess so... it's sort of about how sticking to one language shapes your thinking such that the limitations of the language are beaten into intuition and you have no other way of thinking 01:41:27 so I wanted to try others just to shape thinking really 01:41:53 whether or not they actually get used 01:42:01 proteusguy: all that OOD stuff is exactly about creating "problem oriented languages". 01:42:28 concatnative and imperative are two different things. I think a more functional style approach works better with forth. Understand my definition of forth does not mean ANS forth just like almost no one actually codes is real Lisp but generally a custom variant. 01:42:36 nikki93: Forth doesn't bring you anything in that respect. 01:42:57 i'm sure it must bring a nonzero amout 01:43:08 Why are you sure? 01:43:40 because it's different, and just by being different I feel like it'll bring something 01:43:46 No, it isn't. 01:43:48 nikki93, ASau and I will just have to agree to disagree on that point. forth definitely will change your thinking about how to approach a problem. In fact you must in order to succeed with forth. 01:43:50 Its syntax is. 01:44:16 But that's the only thing that makes Forth so distinct. 01:44:47 in that case the syntax seems different enough to require different thought 01:44:58 nikki93, that said - forth does seem to excel in environmentally constrained targets - embedded systems. if your problem domain is network intensive or distributed I would look at erlang. 01:45:07 nikki93: no, you're wrong. 01:45:45 ASau, please put a pause on the unsupported conclusions. If you have nothing constructively useful to add I think you've made your point. 01:45:48 What is said about "different thought" usually, is a mere translating into highly irregular syntax. 01:46:23 nikki93, we keep ASau around cause he actually knows a lot technically and challenges us at times when it is his interest to do so. the rest of the time he just steps on people's interests and has to be ignored. 01:46:24 Forth isn't anywhere close to excelling in embedded systems. 01:46:40 proteusguy: lol 01:46:41 ASau, now you're just in denial. I expect better of you. 01:46:59 nikki93, what's the problem domain and environment space you're wanting to explore? 01:47:00 That's not denial, it is hard fact Forth lovers deny. 01:47:09 proteusguy: making games interactively 01:47:12 ASau, I'm anything but a forth lover. 01:47:28 What is your "seems to excel" based on? 01:47:36 nikki93, what kind of games? graphics intensive or text based? massively multi-user or single/few players? 01:47:39 proteusguy: like a system where you're playing a game but can click and drag stuff around or change properties, while also changing logic code on the fly 01:47:51 proteusguy: 2d, single player to begin 01:48:12 proteusguy: tbh probably gonna go with lisp hehe 01:48:24 well I actually wrote a whole game engine in C and exposed it to Lua already as part of this experiment 01:48:27 and it all works, including an in-game editor 01:48:27 nikki93: Forth is definitely not fit in this area, but you can try and find it yourself. :) 01:48:36 I used it to make a game for a 48-hour game competition 01:48:49 thinking about redoing it in Lisp 01:49:01 nikki93, if you use any of these languages forth, lisp, erlang - you're going to have to find something for your graphics primitives or make them yourself or simply use these languages to communicate with a separate UI system. They really don't have standard support for such things. 01:49:07 ASau: yeah, I'll try it for a bit. not really meaning to use it for this thing 01:49:21 Essentially, working in Forth is very much similar to working in Fortran-77. 01:49:28 proteusguy: lisp has a good opengl binding that I've played with already 01:49:34 ASau, geez... 01:49:46 Only you have some rudimental support for dynamic memory allocation. 01:50:31 nikki93, that might be the direction you need to go then. building up graphics primitive from first principles is several orders of magnitude more effort than your game I'd expect. 01:50:46 for sure, it is 01:51:00 I found some open source forth games though, doesn't look to bad 01:51:05 but also looks basically C-like in its code 01:51:38 Oh, I see ASau is off his meds again. 01:51:48 nikki93, do they do graphics as well? I haven't played in this space with forth. All my forth experience is pretty much roll your own for embedded. in other words - you create your own forth from scratch. 01:52:17 well gforth has a c ffi 01:52:20 ttmrichter, someone forgot to slide some food into his cage again. 01:52:27 and it basically works 01:52:33 for opengl 01:53:07 proteusguy: https://groups.google.com/forum/#!topic/comp.lang.forth/YDBpr5bGI7M some dude made a game and an engine in forth 01:54:03 nikki93, my experience with game/ui programming is that 80% of your code is the UI. That means you're spending most of your time dealing with a C lib that is built with a completely different midset than the business logic of your forth code. I would consider that a red flag although you could wrap the C primitives in a forth mini language if the library was flexible enough but I expect that is not likely to fit well with a 01:54:04 stack oriented approach. 01:54:39 proteusguy: hmm it depends really, if your game engine abstracts that away a lot ur fine 01:54:53 the beauty of forth is the stack based zero parameter concept. C fights that every step of the way. the two just don't work well together. 01:54:57 proteusguy: in my cgame engine with Lua that I mentioned earlier, you're in an interactive environment that is emacs/vim like, you press ',' and type 'sprite' (it autocompletes) 01:55:07 then hit enter and it creates a sprite, then type in which image you want 01:55:09 after that ur done and are writing game logic 01:55:16 which is your own paradigm 01:55:50 but no, forth is totally too hard for this stuff haha 01:56:00 nikki93, if you can model things on a stack and don't have to push a lot of parameters around or maintain a lot of local variables then it can work. if not then you're fighting against the architectural constraints of forth and probably have very little to gain from it. 01:57:05 nikki93, but I will say - just playing with forth for a while and building up some higher logic from its primitives is a very useful and entertaining exercise that might help you in order endeavors as well. doesn't take long. 01:57:52 "if you can model things on a stack and don't have to push a lot of parameters around" 01:57:53 Ha-ha. 01:58:31 Hey, ASau, I say this as a concerned citizen, but you need to either start taking your anti-psychotic medication again or hit your doctor stat and get it re-dosed or switched. 01:58:52 ASau, that's what I do with all my mini-forth projects and it is wonderful.. I thought you had some experience with concatonative languages? 01:59:01 And Forth is very, very sorry for murdering your mother and raping your cat. It won't do it again. 02:00:51 You can introduce a lot of parameter objects and shift the burden, sure. 02:02:35 ASau, if you're agreeing with me and saying that integrating forth and a C lib paradigm is freaking hard then just say so. If you're saying that most software cannot be modeled in a clear stack-based architecture then I'd just say that my 30 years of experience says otherwise and, in fact, is leading me to believe that stack based is actually the direction where the industry must ultimately go. 02:03:10 whddya guys think of factor 02:03:23 proteusguy: ASau is just basically raving. Sane people don't hang around in forums for discussing languages they hate. They hang around in forums for languages they like. 02:03:45 nikki93: I quite like Factor conceptually, but its implementation and packaging was quite a bit of a mess last I looked. 02:03:49 it's a neat idea conceptually and heading in the right direction but doesn't do anything useful enough for me to have personally gotten involved in it. 02:04:06 proteusguy: "can be modelled in a clear stack-based architecture" is falling into Turing tarpit. 02:04:18 Yes, once you have two stacks, you can model anything. 02:04:28 to me forth == stack based == simplicity. factor has a bit too much magic for my taste and loses the simplicity with not enough payback. 02:04:31 And hanging around in #forth when you hate the language is falling into insanity. 02:04:37 That doesn't make it easy or comprehensible. 02:05:20 Well your behaviour certainly IS incomprehensible, that much is true. 02:06:12 ASau, I see where you're heading re:Turing but that's not my point at all. zero-operand processors are where we need to go if we want to continue Moore's law a few more generations. function calls with parameters and handling stack frame management is fraught with useless complexity and overhead. 02:06:38 ttmrichter, no need to make it personal... unless it's funny. ;) 02:06:56 I don't see any ground for that. 02:07:30 ASau, then we have different experiences. I don't have a problem with that. 02:08:01 Alright, even if it is true, it is still problematic. 02:08:03 Consider that we don't want to continue Moore's law. 02:08:24 We don't want computations to be faster/cheaper/smaller? 02:08:36 Of course not. 02:08:39 I would argue that we do. :) 02:08:42 We want our computations to be better. 02:08:46 We do, but why Moore's law is relevant here? 02:09:17 I would argue that making things faster/cheaper/smaller actually makes programmers lazy and sloppy, giving us things like browsers that take up more memory than any other single program on an average system. 02:09:34 As you can see the world seems to move towards MP instead of zero-operand CPUs. 02:10:16 ASau, how much have you dealt with the hardware side of computing in terms of CPUs, adders, etc..? Irrespective of the style of coding you're doing it is of benefit to all that our physical components be smaller, faster and require less power. 02:11:21 ttmrichter, it does - there fore we have javascript - but that doesn't preclude good engineers from taking advantage of what hardware has to offer and being competitively more efficient. 02:11:47 proteusguy: I'd love to live in a world where being efficient was actually a competitive advantage. 02:12:16 ASau, it does seem to be going that way but my observations are leading me to believe we should be going to zero operand multi-cpu arrays. 02:12:42 ttmrichter, just play around with encryption and stats for a while. it goes right to the bottom line. 02:13:10 That was my last job in software, actually. 02:13:14 I worked at Entrust. 02:13:24 Software costs a lot more than hardware these days. 02:13:27 And while the crypto guys were interested in that, the rest of the software was bloatware of the worst kind. 02:13:58 ttmrichter, haha indeed but you don't need it everywhere. 02:16:15 ASau, it does - in lage part because we have to write our software to deal with an incorrect hardware architecture. We need hardware that conforms to our software's architecture. But there's too much inertia behind the C=call register-heavy approach and, while software as a whole cost more than hardware, the cost to build a new chip fab facility dwarfs any software project to date. 02:17:36 Software is expensive to architect/implement and almost free to reproduce. Hardware has the opposite cost structure. We need these two domains to be more cooperative. 02:30:14 And the answer is: reconfigurable systems! :) 02:32:26 true-grue, you mean like FPGA? 02:32:41 But "we really don't know how to compute" (Gerald Jay Sussman) and we can't program these reconfigurable systems properly too. Even in the case of FPGA, we still have nothing to program them on the large scale. 02:34:20 As software starts merging into the hardware space I think we're going to learn a lot in the next few decades but computing is indeed an extremely young domain. The term computer science is a joke and computer engineering generally misapplied or premature. 03:01:29 --- quit: nikki93 (Read error: Connection reset by peer) 03:17:40 --- join: mnemnion (~mnemnion@c-98-210-219-91.hsd1.ca.comcast.net) joined #forth 03:19:45 --- join: joneshf-laptop_ (~joneshf@98.208.35.89) joined #forth 03:19:46 --- quit: joneshf-laptop (Read error: Connection reset by peer) 03:22:28 --- quit: mnemnion (Ping timeout: 258 seconds) 03:38:36 --- quit: gabriel_laddel (Read error: Connection reset by peer) 04:00:23 --- quit: samrat (Quit: Computer has gone to sleep.) 04:25:36 --- quit: ttmrichter (*.net *.split) 04:25:36 --- quit: joneshf-laptop_ (*.net *.split) 04:25:36 --- quit: Azel (*.net *.split) 04:25:36 --- quit: darkf (*.net *.split) 04:25:37 --- quit: irsol (*.net *.split) 04:25:37 --- quit: bjorkintosh (*.net *.split) 04:25:38 --- quit: bluekelp (*.net *.split) 04:25:38 --- quit: crc (*.net *.split) 04:25:40 --- quit: ErhardtMundt (*.net *.split) 04:25:41 --- quit: malyn_ (*.net *.split) 04:25:42 --- quit: I440r (*.net *.split) 04:25:42 --- quit: Adeon (*.net *.split) 04:25:42 --- quit: true-grue (*.net *.split) 04:25:43 --- quit: karswell (*.net *.split) 04:25:45 --- quit: nottwo (*.net *.split) 04:25:46 --- quit: ASau (*.net *.split) 04:26:20 --- join: ttmrichter (~ttmrichte@104.236.165.12) joined #forth 04:27:34 --- join: joneshf-laptop_ (~joneshf@98.208.35.89) joined #forth 04:27:34 --- join: Azel (~Thunderbi@ANice-653-1-542-113.w86-205.abo.wanadoo.fr) joined #forth 04:27:34 --- join: darkf (~darkf___@unaffiliated/darkf) joined #forth 04:27:34 --- join: irsol (~irsol@unaffiliated/contempt) joined #forth 04:27:34 --- join: bjorkintosh (~bjork@ip68-13-229-200.ok.ok.cox.net) joined #forth 04:27:34 --- join: bluekelp (~bluekelp@2001:470:1:41:c4c8:c51c:1c5d:5b94) joined #forth 04:27:34 --- join: crc (sid2647@gateway/web/irccloud.com/x-vwsfnarfevrojtsc) joined #forth 04:27:34 --- mode: wilhelm.freenode.net set +v bluekelp 04:27:43 --- join: ErhardtMundt (~quassel@93-43-163-57.ip92.fastwebnet.it) joined #forth 04:27:43 --- join: 7YUAAPOC8 (~malyn@unaffiliated/malyn) joined #forth 04:27:43 --- join: I440r (~mark4@cpe-68-203-183-77.tx.res.rr.com) joined #forth 04:27:43 --- join: Adeon (shannon@sukima.trankesbel.com) joined #forth 04:27:43 --- mode: wilhelm.freenode.net set +o I440r 04:28:06 --- join: true-grue (~grue@95-27-128-12.broadband.corbina.ru) joined #forth 04:28:06 --- join: karswell (~user@87.113.227.45) joined #forth 04:28:06 --- join: nottwo (~trannie@nottwo.org) joined #forth 04:28:13 --- quit: Azel (Ping timeout: 244 seconds) 04:29:56 --- join: ASau (~user@46.115.17.87) joined #forth 04:35:49 --- join: Azel (~Thunderbi@ANice-653-1-542-113.w86-205.abo.wanadoo.fr) joined #forth 04:57:37 --- join: vanila (~vanila@unaffiliated/vanila) joined #forth 05:06:42 --- join: mnemnion (~mnemnion@c-98-210-219-91.hsd1.ca.comcast.net) joined #forth 05:11:27 --- quit: mnemnion (Ping timeout: 255 seconds) 05:27:28 --- quit: Azel (Ping timeout: 244 seconds) 05:29:58 --- join: mnemnion (~mnemnion@c-98-210-219-91.hsd1.ca.comcast.net) joined #forth 05:31:35 --- join: nighty^ (~nighty@hokuriku.rural-networks.com) joined #forth 05:34:55 --- quit: mnemnion (Ping timeout: 272 seconds) 05:50:07 proteusguy: The term "computer engineering" is not "misapplied" or "premature" but a flat-out lie in 99.44% or more of the cases where it's applied. 05:54:18 <-- classic example lol 05:54:29 i have no degree, how can i call myself any kind of engineer 05:54:37 anyway off to work to go engineer some stuff 05:54:39 bbl :) 06:00:54 I440r: This is independent of degrees. I've never seen any software written using any kind of serious engineering principles rigorously applied. 06:01:22 CS majors are maths geeks with such a disconnect from the real world of software they may as well insert "magic happens here" in their explanations for how things should work. 06:01:36 In the meantime people who claim to be doing "software engineering" are really just cargo cultists. 06:08:44 --- join: samrat (~samrat@123.236.183.195) joined #forth 06:19:34 I said computer engineering - not software engineering. ;) CPU design is certainly an engineering effort and there's some new concepts invented for information architecture as well but that's certainly not what people are thinking about when they use the term. 06:32:46 --- join: kumul (~mool@adsl-64-237-236-150.prtc.net) joined #forth 06:33:50 CS, isn't very sciencey, either. :) 06:35:00 most CS undergrads I've met, don't understand more that HTML and JAVA, either. 06:36:06 unless they do their own studies, of course. 06:47:56 A professor friend of mine used to remind us that no real science has the word science in it. Physics, Chemistry - real sciences. Political Science, Social Science, Computer Science - not actually sciences. 07:01:33 --- join: mnemnion (~mnemnion@c-98-210-219-91.hsd1.ca.comcast.net) joined #forth 07:06:12 --- quit: mnemnion (Ping timeout: 255 seconds) 07:07:38 --- join: mnemnion (~mnemnion@c-98-210-219-91.hsd1.ca.comcast.net) joined #forth 07:14:11 --- join: gabriel_laddel (~user@2601:9:4f81:acb0:221:6aff:fea4:6db8) joined #forth 07:15:06 --- quit: gabriel_laddel (Changing host) 07:15:06 --- join: gabriel_laddel (~user@unaffiliated/gabriel-laddel/x-9909917) joined #forth 07:15:09 --- join: _spt_ (~jaat@host-92-24-239-8.ppp.as43234.net) joined #forth 07:15:10 --- quit: _spt_ (Changing host) 07:15:10 --- join: _spt_ (~jaat@unaffiliated/-spt-/x-5624824) joined #forth 07:29:02 --- quit: darkf (Quit: Leaving) 07:53:52 proteusguy: Ah, OK, true, in making the actual computers there's real engineering going on. Sadly this is not true for the software that uses them. 07:54:35 beretta: Computer Science is an overbroad term that covers everything from trade school-level training to advanced maths. NONE of that spectrum is a science. 07:55:08 Computer Science (in its proper academic form, not the trade school stuff) has almost nothing to do with computers and nothing to do with science whatsoever. 07:55:09 computer science isn't about computers or science 08:03:20 --- quit: vanila (Remote host closed the connection) 08:07:07 --- quit: ASau (Ping timeout: 252 seconds) 08:19:12 The iOS version of retro currently doesn't have a functional terminal emulator. Input is currently done by entering in the editor pane, with results displayed below. 08:20:05 Evaluation basically types the contents of the editor into the listener, displaying the results as they occur. So you'd have to enter everything in the editor before evaluate is done. 08:50:32 --- join: fantazo (~fantazo@089144216235.atnat0025.highway.a1.net) joined #forth 09:24:45 --- quit: kumul (Quit: Leaving) 09:32:08 --- join: Azel (~Thunderbi@ANice-653-1-542-113.w86-205.abo.wanadoo.fr) joined #forth 10:48:32 --- quit: protist (Quit: Konversation terminated!) 11:18:06 --- quit: dzho (Ping timeout: 245 seconds) 11:19:00 --- join: dzho (~dzho@unaffiliated/dzho) joined #forth 11:36:48 --- quit: dzho (Ping timeout: 245 seconds) 11:37:47 --- join: dzho (~dzho@unaffiliated/dzho) joined #forth 12:08:42 --- join: MrMobius_ (~MrMobius@c-71-206-218-187.hsd1.wv.comcast.net) joined #forth 12:18:26 --- join: ASau (~user@46.115.17.87) joined #forth 12:27:07 I wonder if you count linguistics as a science or not. 12:27:34 --- join: hellen_haskeller (~kvirc@64.116.185.9) joined #forth 12:34:35 --- quit: hellen_haskeller (Read error: Connection reset by peer) 12:44:23 --- quit: fantazo (Quit: Verlassend) 12:46:29 --- quit: true-grue (Read error: Connection reset by peer) 13:02:51 --- join: Zarutian (~Adium@168-110-22-46.fiber.hringdu.is) joined #forth 13:05:49 --- quit: samrat (Quit: Computer has gone to sleep.) 13:14:47 --- quit: MrMobius_ (Ping timeout: 244 seconds) 13:34:42 --- quit: nighty^ (Read error: Connection reset by peer) 13:35:17 --- join: nighty^ (~nighty@hokuriku.rural-networks.com) joined #forth 13:56:14 --- join: MrMobius_ (~MrMobius@c-71-206-218-187.hsd1.wv.comcast.net) joined #forth 13:58:43 --- quit: nighty^ (Read error: Connection reset by peer) 13:59:27 --- join: nighty^ (~nighty@hokuriku.rural-networks.com) joined #forth 14:01:21 --- join: paolo_o (uid58208@gateway/web/irccloud.com/x-humpurqaisjsdahm) joined #forth 14:08:02 --- quit: MrMobius_ (Ping timeout: 240 seconds) 14:29:53 --- quit: proteusguy (Ping timeout: 264 seconds) 14:36:57 --- quit: ASau (Remote host closed the connection) 14:43:51 --- join: proteusguy (~proteusgu@ppp-110-168-229-17.revip5.asianet.co.th) joined #forth 14:43:51 --- mode: ChanServ set +v proteusguy 14:58:48 --- quit: mnemnion (Remote host closed the connection) 15:03:10 --- join: ASau (~user@46.115.17.87) joined #forth 15:17:52 --- join: mnemnion (~mnemnion@c-98-210-219-91.hsd1.ca.comcast.net) joined #forth 15:52:58 --- quit: nighty^_ (Remote host closed the connection) 16:45:46 --- join: vanila (~vanila@unaffiliated/vanila) joined #forth 16:51:36 --- join: saml_ (~saml@cpe-24-102-97-97.nyc.res.rr.com) joined #forth 16:53:29 --- quit: Zarutian (Quit: Leaving.) 16:55:34 --- join: xyh (~xieyuheng@121.33.190.145) joined #forth 17:17:19 --- quit: nighty^ (Quit: Disappears in a puff of smoke) 17:18:33 --- quit: _spt_ (Quit: Irssi 0.8.17 http://irssi.org/ - gone) 18:21:37 --- quit: mnemnion (Remote host closed the connection) 18:22:16 --- join: mnemnion (~mnemnion@c-98-210-219-91.hsd1.ca.comcast.net) joined #forth 18:26:39 --- quit: mnemnion (Ping timeout: 255 seconds) 18:30:02 --- join: darkf (~darkf___@unaffiliated/darkf) joined #forth 19:14:40 --- join: mnemnion (~mnemnion@142-254-26-6.dsl.static.fusionbroadband.com) joined #forth 19:21:29 --- join: samrat (~samrat@123.236.183.195) joined #forth 19:52:39 --- quit: mnemnion (Remote host closed the connection) 19:53:28 --- join: mnemnion (~mnemnion@142-254-26-6.dsl.static.fusionbroadband.com) joined #forth 19:56:40 --- quit: mnemnion (Remote host closed the connection) 19:56:46 --- join: mnemnion (~mnemnion@142-254-26-6.dsl.static.fusionbroadband.com) joined #forth 20:19:55 --- quit: samrat (Quit: Computer has gone to sleep.) 20:22:37 --- join: samrat (~samrat@123.236.183.195) joined #forth 20:27:53 --- quit: mnemnion (Remote host closed the connection) 20:45:19 --- join: ehaliewicz (~user@50-0-50-17.dsl.dynamic.fusionbroadband.com) joined #forth 20:56:19 --- quit: malyn (Ping timeout: 264 seconds) 20:56:59 --- join: malyn (~malyn@69.55.234.100) joined #forth 20:59:39 --- quit: saml_ (Ping timeout: 272 seconds) 21:11:55 --- quit: samrat (Quit: Computer has gone to sleep.) 21:24:52 --- join: mnemnion (~mnemnion@142-254-26-6.dsl.static.fusionbroadband.com) joined #forth 21:28:23 --- quit: ASau (Remote host closed the connection) 21:28:49 --- join: ASau` (~user@46.115.17.87) joined #forth 21:34:42 --- quit: xyh (Remote host closed the connection) 21:38:17 --- quit: mnemnion (Remote host closed the connection) 21:55:15 --- join: MrMobius_ (~MrMobius@c-71-206-218-187.hsd1.wv.comcast.net) joined #forth 21:59:50 --- join: protist (~javery@121-72-251-45.cable.telstraclear.net) joined #forth 22:01:25 --- join: samrat (~samrat@61.12.96.226) joined #forth 22:01:27 --- nick: ASau` -> ASau 22:08:08 --- quit: samrat (Quit: Computer has gone to sleep.) 22:12:16 --- join: mnemnion (~mnemnion@c-98-210-219-91.hsd1.ca.comcast.net) joined #forth 22:16:59 --- join: samrat (~samrat@61.12.96.226) joined #forth 23:32:29 --- quit: ErhardtMundt (Read error: Connection reset by peer) 23:43:36 --- join: ErhardtMundt (~quassel@93-43-163-57.ip92.fastwebnet.it) joined #forth 23:59:59 --- log: ended forth/14.12.23