00:00:00 --- log: started forth/14.11.17 00:00:54 --- join: jabb (~grue@5402AEAF.dsl.pool.telekom.hu) joined #forth 00:14:59 --- join: brylie (~quassel@mobile-internet-6df06a-110.dhcp.inet.fi) joined #forth 00:38:29 --- quit: proteusguy (Ping timeout: 255 seconds) 00:50:55 --- join: nighty-_ (~nighty@hokuriku.rural-networks.com) joined #forth 01:20:55 --- join: xyh (~xieyuheng@2001:250:3002:5550:6ea1:cc0f:bcb2:b187) joined #forth 01:34:07 --- join: jabb_ (~grue@BC064FB6.dsl.pool.telekom.hu) joined #forth 01:37:08 --- quit: jabb (Ping timeout: 264 seconds) 01:56:56 --- join: proteusguy (~proteusgu@49.230.89.30) joined #forth 02:04:54 --- quit: proteusguy (Remote host closed the connection) 03:05:36 --- quit: xyh (Ping timeout: 265 seconds) 03:08:37 --- join: proteusguy (~proteusgu@58.185.7.202) joined #forth 03:14:52 --- quit: proteusguy (Remote host closed the connection) 03:39:41 --- join: Zarutian (~zarutian@168-110-22-46.fiber.hringdu.is) joined #forth 04:04:16 --- quit: samrat (Quit: Computer has gone to sleep.) 04:26:01 --- part: brylie left #forth 04:56:15 --- join: proteusguy (~proteusgu@58.185.7.202) joined #forth 05:12:10 --- join: protist (~javery@130.224.69.111.dynamic.snap.net.nz) joined #forth 05:14:37 --- join: Azel (~Thunderbi@vig91-h03-89-84-5-35.dsl.sta.abo.bbox.fr) joined #forth 05:27:25 --- join: samrat (~samrat@123.236.183.195) joined #forth 06:01:17 --- join: true-grue (~grue@95-25-114-19.broadband.corbina.ru) joined #forth 06:13:09 --- quit: proteusguy (Remote host closed the connection) 06:15:44 --- join: proteusguy (~proteusgu@58.185.7.202) joined #forth 06:24:27 --- quit: Zarutian (Quit: Zarutian) 06:26:44 --- quit: samrat (Quit: Computer has gone to sleep.) 06:32:29 --- join: nicole (~nicole@68.225.98.27) joined #forth 06:47:40 --- join: nighty^_ (~nighty@static-68-179-124-161.ptr.terago.net) joined #forth 06:48:03 --- quit: nighty^ (Read error: Connection reset by peer) 06:56:06 I think so too,. but oh well. Kind of used to it after years and years of the same... 07:09:50 --- join: xyh (~xieyuheng@125.94.36.160) joined #forth 07:16:25 --- join: samrat (~samrat@123.236.183.195) joined #forth 07:29:09 --- quit: beretta (Ping timeout: 250 seconds) 07:33:47 --- quit: jabb_ (Ping timeout: 240 seconds) 07:36:14 --- join: jabb (~grue@BC064FB6.dsl.pool.telekom.hu) joined #forth 07:36:20 --- quit: xyh (Remote host closed the connection) 07:40:31 --- quit: samrat (Ping timeout: 264 seconds) 07:42:51 --- join: beretta (~beretta@cpe-65-185-42-203.columbus.res.rr.com) joined #forth 07:45:14 --- join: samrat (~samrat@123.236.183.195) joined #forth 07:49:55 --- quit: samrat (Client Quit) 07:51:41 --- join: vanila (~user@unaffiliated/vanila) joined #forth 07:53:48 --- join: samrat (~samrat@123.236.183.195) joined #forth 08:11:44 --- join: xyh (~xieyuheng@2001:250:3002:5550:6ea1:cc0f:bcb2:b187) joined #forth 08:25:16 --- quit: samrat (Ping timeout: 255 seconds) 08:26:49 --- quit: Azel (Remote host closed the connection) 08:28:15 --- join: samrat (~samrat@123.236.183.195) joined #forth 08:39:20 --- quit: impomatic (Ping timeout: 264 seconds) 08:46:47 --- quit: samrat (Quit: Computer has gone to sleep.) 08:55:33 --- quit: xyh (Remote host closed the connection) 08:57:03 --- quit: protist (Quit: Konversation terminated!) 09:02:52 --- join: impomatic (~chatzilla@235.198.208.46.dyn.plus.net) joined #forth 09:05:48 --- join: samrat (~samrat@123.236.183.195) joined #forth 09:10:06 --- join: PoppaVic (~pops@unaffiliated/poppavic) joined #forth 09:13:52 --- quit: rixard (Quit: rixard) 09:14:33 --- quit: nicole (Ping timeout: 256 seconds) 09:39:21 --- join: xyh (~xieyuheng@2001:250:3002:5550:6ea1:cc0f:bcb2:b187) joined #forth 09:47:16 --- join: rixard (~rixard@90-229-190-197-no63.tbcn.telia.com) joined #forth 10:14:55 --- quit: xyh (Remote host closed the connection) 10:26:42 --- join: DKordic (~user@109-92-205-94.dynamic.isp.telekom.rs) joined #forth 10:32:06 --- quit: beretta (Ping timeout: 255 seconds) 11:04:30 --- quit: impomatic (Quit: ChatZilla 0.9.91 [Firefox 33.1/20141106120505]) 11:05:06 --- join: impomatic (~chatzilla@235.198.208.46.dyn.plus.net) joined #forth 11:06:58 --- join: impomatic_ (~digital_w@235.198.208.46.dyn.plus.net) joined #forth 11:08:50 --- join: fantazo (~fantazo@2001:858:5:3a41:99d8:b33b:fce0:c986) joined #forth 11:46:23 --- quit: proteusguy (Ping timeout: 264 seconds) 11:52:36 --- quit: samrat (Quit: Computer has gone to sleep.) 12:06:59 --- join: Azel (~Thunderbi@vig91-h03-89-84-5-35.dsl.sta.abo.bbox.fr) joined #forth 12:30:52 --- join: xyh (~xieyuheng@2001:250:3002:5550:6ea1:cc0f:bcb2:b187) joined #forth 12:32:42 --- quit: fantazo (Quit: Verlassend) 12:44:56 --- join: Mat3|coding (~Mat3@ip5b414c9f.dynamic.kabel-deutschland.de) joined #forth 12:45:01 hello 13:06:43 asd/j #lainchan 13:06:48 oops sorry 13:09:30 --- quit: ErhardtMundt (Quit: No Ping reply in 180 seconds.) 13:09:53 --- join: ErhardtMundt (~quassel@93-43-163-57.ip92.fastwebnet.it) joined #forth 13:20:54 --- join: fantazo (~fantazo@089144197205.atnat0006.highway.a1.net) joined #forth 13:22:22 --- part: Mat3|coding left #forth 13:27:49 --- join: BirdReynolds (~mhx@s529d937f.adsl.online.nl) joined #forth 13:28:52 --- join: I440r (~mark4@cpe-68-203-183-77.tx.res.rr.com) joined #forth 13:28:58 --- mode: ChanServ set +o I440r 13:29:00 --- join: beretta (~beretta@cpe-65-185-42-203.columbus.res.rr.com) joined #forth 13:29:09 any android dev crazies in here? 13:29:16 the crazier the better 13:31:02 --- quit: BirdReynolds (Client Quit) 13:35:33 picking on droidies,,, Low, man,, low. 13:36:01 ive written a native android forth library 13:36:12 oh, my - you poor bastard. 13:36:19 im now implementing a java application that will link that library using a server socket 13:36:33 telnet to your device, write forht code on it from your pc. 13:36:51 it was just a minor modification to my already existing arm linux forth 13:37:20 --- join: Zarutian (~zarutian@168-110-22-46.fiber.hringdu.is) joined #forth 13:37:31 im also using this forth in an android game i am writing. the forth decompresses the map data and also calculates mob pathing 13:37:55 plus it defines the personalities of every town, city, npc in towns, mobs in the world map etc etc 13:38:28 the purpose of the application im wiring now is the soket server will be able to be used when you link my forth into your apps 13:38:58 to give you a way to debug your forth interactivly 13:39:10 l440r: by any chance is it called ATLAST? 13:39:40 I440r: you are the auther of isForth ? 13:40:02 yes 13:40:18 i also come in here as mark4 when im too lazy to switch nick names 13:40:39 Zarutian, the first letter is an EYE not an ELL :) 13:40:45 and no its not released or named 13:40:48 yet 13:41:10 I440r == Ibanez 440 Radius. one of my guitars 13:42:28 I440r: I remember this Nick from the doc of IsForth :) 13:42:37 heh 13:42:51 you played withy isforth much? 13:42:56 no 13:43:55 I steal ideas from you, and implement my lang :P 13:44:23 good 13:44:32 steal away :) 13:45:49 I440r: and you are the first register of this channel ? 13:45:55 yes 13:46:25 i claim no ownership, it belongs to the people who idle here 13:47:11 no one never owns a channel, of course :) 13:50:02 I440r: the terminal stuffs of isforth is fancy. 13:50:18 it took 8 hours of man 5 terminfo to figure most of that stuff out 13:50:41 ive done some updates to it including adding the menuing to the text user interface code. cant remember if i released any of that yet tho 13:51:19 i cleaned up the memory manager code and the terminal code a lot 13:51:32 I440r: why not push to github ? please push them to github 13:51:35 but i have a lot on my plate atm 13:51:39 fuck github 13:51:40 fuck git 13:51:42 ... 13:51:44 hg 13:51:45 heheheheha 13:51:50 i use hg locally 13:51:58 push to bitbucket 13:52:04 i wont use github or bitbucket 13:52:09 www.isforth.com <-- 13:52:13 ok~ 13:52:30 but you said it is not updated 13:52:36 git and hg etc are VERSION CONTROL not "release control" 13:52:40 not distribution 13:53:01 i have made changes locally that i have not yet published 13:53:25 right now my most up to date version is broken due to a change heh 13:53:33 * xyh just wishs to steal them all 13:53:44 ive not been working on that, this android forth is going to be marketed on google play 13:54:01 I440r: so, not open? 13:54:32 you cannot steal my memory manager as a whole. you cannot take my memory manager or my terminal stuff and put them into YOUR forth 13:54:44 without permission that is 13:55:02 you can use them as a basis for writing your own stuff in your own language however 13:55:02 of course ... 13:55:12 I have my GC in my lang. 13:55:20 the android forth is not open yet 13:55:24 im not a fan of gc 13:55:51 I am big fan of GC, can't code without it 13:56:09 I believe it 13:56:54 I440r: I see the doc of isforth says arm version is coming soon, so the android forth will be open too ? 13:57:07 wow... just realized how fancy, compared to other forth systems, isforth is visually. 13:57:11 no there already is an arm version its just not up to snuff yet 13:57:17 it runs on my beagleboard xm 13:57:26 but it wont run under debian unless YOU tweak it 13:57:35 i wont tweak it to run under broken linux distros 13:57:41 or stupid ones 13:58:16 you mean the status bar? 13:58:21 you can turn that on and off with 13:58:22 staoff 13:58:24 staton 13:58:56 lol, status bar "Wed, 08 Aug 2018 03:14:14 +2136" time isn't correct 13:59:11 what distro do you use 14:00:11 also. are you running inside a screen session? screen has a buggered terminfo and im not duct taping my code to fix their fuck up 14:00:38 nor will i duct tape it to fix gnomes stupid terminal 14:00:43 actually not stupid. moronic 14:01:12 the terminal is a unicode-rxvt, archlinux 14:01:28 thats one of the things that amazes me about libncurses. he has such a HUGE amout of duct tape in there to fix other peopels incompetence 14:01:40 arch would be my second choice of distro after gentoo 14:01:59 hmm im not sure if your running the version that has a bug in the date/time code 14:02:15 i remember fixing that some time ago, also might not be released 14:02:27 but it was a simple fix if i remember rightly 14:02:35 I440r, what is actually your design of your isforth, if you don't use ans forth as a base. 14:02:55 no. im the single most ANTI ans person you are ever likely to meet 14:03:00 isforth is 100% isforth compliant 14:03:20 its actually not FAR off ans compliance but thats not a goal 14:03:51 my mental base would be the 83 standard but it is not compliant with that either, its more modern 14:04:18 I440r, I know that you are against ANS. I once was too, now I have got somehow that "business" logic behind it. or I have too much seen shit in programming to tolerate it. pick your reasons for hating me. 14:04:29 i used tom zimmers FPC for dos (a 1980's 83 standard forth) as a starting point 14:04:48 i dont hate ans forth users 14:04:58 its ans forth i do not like :) 14:05:11 I would love to write an ans forth compliant library for replacing it. 14:05:11 I440r: any particular bit? 14:05:16 fixing it at the source. 14:05:18 you will never see postpone or invert in any forth i write 14:05:32 Zarutian, the bit that makes forth read like clusterfuck C 14:05:35 thats the bit i hate 14:05:46 I440r: I see. 14:05:59 : foo postpone x ; immediate : bar postpone y ; immediate ... 400 other definitions like this later.... 14:06:09 and C is rather much of a clusterfuck already. 14:06:18 any time i read badly formatted and badly written C code i eventually dont see any logic or even c code 14:06:20 all i see is 14:06:22 blah blah 14:06:23 blah blah 14:06:24 I440r, what are you using instead of postpone? 14:06:25 blah 14:06:27 blah blah blah 14:06:34 i get the same any time i read ans forth 14:06:41 compile [compile] 14:06:50 which BTW are IN THE ANS STANDARD and postpone is not 14:06:52 I440r: I know the feeling. I see it with code that has subcumbed to feeble creaturism. 14:06:57 or wasnt last time i checked 14:07:08 i also will never support conditional compilation 14:07:27 any time you see an ans forth source the first part will always be 14:07:27 conditional compilation? 14:07:31 what is that? 14:07:42 #if this is SOME_SPECIFIC_FORTH 14:07:44 define this stuff 14:07:47 #endif 14:07:50 ad infinitum 14:07:54 oh that kind of crap 14:07:56 * PoppaVic chuckles 14:08:00 #ifdef blah this is defined #endif 14:08:15 the this is defined part is only defined if blah is defined 14:08:30 add conditional compilation and you are guaranteed to have clusterfuck source code 14:08:41 one source file with 2856728956 different versions of the same thing 14:08:45 or the "C style module fix", also a nice one. 14:08:49 want to code like that.. go code c 14:08:51 lol 14:09:01 --- quit: tangentstorm (Quit: WeeChat 0.3.2) 14:09:04 I440r: how is the progress of converting Linus? 14:09:05 c doesnt have modules or a fix for the lack of modules 14:09:21 linus already knows forth and does not like it because it lacks data types 14:10:15 * Zarutian prefers Scheme48's method of modules (very similiar to commonjs modules in javascript) 14:10:37 I440r, well ... yes C doesn't, but my point was the use of macros for preventing that code isn't double loaded. 14:10:53 when using #include in of the same file in multiple C files 14:11:16 i do not recommend nested includes 14:11:23 in forth you should use a load file 14:11:26 no hygenic macros eather. 14:11:38 if you need the memory manager you need to include all the components of it 14:11:50 if you need the termain user interface you should include all the components of it 14:12:08 if you write an application with N modules you should never have any of those modules include any others 14:12:26 --- quit: true-grue (Read error: Connection reset by peer) 14:12:31 you should include the entire application in a load file. and that load file should load all the bits and pieces in the right order 14:12:42 hehaha 14:12:45 i support up to 5 nested includes but recommend only loading from a load file 14:12:50 my version of include just creates a noop word in dictionary that matches the loaded file, after double checking that it wasn't already loaded. 14:13:00 if your stuff is so complicated you cant keep track of all that... rm -rf and start over 14:13:23 beretta, thats one way of doing it 14:13:38 but you shoudl have all the module names in a module_names vocabulary 14:13:48 I440r: have you seen the hurting point of "no Github and no Bitbucket". it makes an ideas-theft can't steals anymore. 14:13:55 because if they are not compiled into there then you might not have them in context 14:14:23 xyh i am a christian, i operate on the honro system 14:14:32 :) 14:14:33 my source code is 100% open source in isforth 14:14:40 if you steal it thats between you and god 14:14:56 i have simply stated "ask first" then its not theft 14:15:01 hahah... that's a phrase my dad says... 14:15:26 pfft.. You take - then ask for forgiveness. Problem solved - absolved. 14:15:49 that only applies if you use my source code 14:16:03 you can take a snippet or a single definition and use it however you want 14:16:06 I440r: I do not copy code. I just read and learn. 14:16:14 like my ?: word. i claim i invented that 14:16:36 but i claim no ownership, you can implement it in your own forth or even take MY definition of it and put it in your forth 14:16:42 I thougth the christian part in your doc is a joke! 14:16:46 xyh thats a good way 14:16:49 no 14:16:53 say, can anyone here tell me why certain kind of cpu designer insists on overcomplicate the heck out it? 14:17:14 Zarutian, what cpu specifically? 14:18:37 I440r: ARMv11 for an recent example. Though x86 is much worse. Spefically what is up with having pipelines branch prediction and all that crap? Instead of having small per core spefic sram on chip? 14:19:03 arm stopped being RISC a long time ago 14:19:15 it is one of the most complicated instruction sets ive ever seen 14:19:20 I440r: I invented (or re-invented) a lot too, how do you find of this, (it is so not up to date too but the Github repo is up to date) :: http://cicada-language.github.io/source-code/english-core.org.html 14:19:30 and thats not even looking at their stupid thumb v2 yet 14:20:01 I440r: so you know what I am talking about then? 14:21:06 Zarutian, i ported isforth to arm. i was looking at writing my own arm assembler in forth. that idea has moved down the todo list tho simply because of the extremely complex instruction encodings 14:21:17 and the fact that there are now THREE instruction encodings supported by arm 14:21:21 arm, thumb, thumb2 14:21:46 Zarutian: I thinke it is not designed by only one Generation of designer, when more people come it becauses big. 14:21:50 x86 is more powerful a processor and has a simple instruction encoding 14:22:10 even after they added sse sse2 sse3 sse4 sse5... sse9999 and mmx and all the other stuff they added 14:22:21 I440r: x86? simple instruction encoding? well perhaps. 14:22:32 a camel is a horse designed by a committee 14:22:35 --- quit: nighty-_ (Quit: Disappears in a puff of smoke) 14:22:45 Zarutian, the x86 instruction encoding is trivial even after all these years 14:22:58 what makes it seem non trivial is the fact that they publish the encodings in HEX 14:23:05 which is utterly moronic 14:23:16 look at the encodings in octal and every single one of them makes sense 14:24:10 I440r: can you give a short example? 14:24:38 http://tnovelli.net/ref/opx86.html 14:24:51 look there, it has a truncated doc on opcode encodings 14:24:58 tom novelli used to hang in here too :P 14:25:10 he helped me get isforth off the ground all those years ago 14:25:57 perhaps I have been looking too much at cell/word addressed architectures 14:28:57 I440r: octal is cool , you should tall them -> http://ref.x86asm.net/ 14:29:22 they wont listen. their tables too a lot of work and they think they are well presented 14:29:52 the fact that it is almost impossible to see all the information you need all at the same time for any given opcode encoding seems to escape them 14:30:28 look at takbe. clik link at bottom of table for more info. click link at bottom of new table for more info... . .. . 14:31:36 is it possible to design new format and reuse their xml ? 14:32:04 no idea. i wouldnt bother trying myself 14:32:29 would be almost impossible to organize the data they have presented into a format that was useful 14:32:44 simpler to start over from scratch and NOT use them as a reference 14:33:08 even NOT use them as a reference ? 14:33:46 not unless you want to end up more confused after referencing them than you were before you did so lol 14:34:01 the way they explain certain things is very confusing 14:34:11 their tables are also in hex which is utterly useless 14:34:31 I wish to write assembler for x86 too, but the encoding seems hard to learn for me. 14:34:39 their tables do not show all of the fields of any of the opcode encodings beause they are in hex 14:35:07 xyh if you want to learn to write an assembler first write a disassembler 14:35:10 i mean for x86 14:35:26 why ? 14:35:32 simpler? 14:35:33 you NEED to be able to understand all of the opcode fields to be able to disassemble 14:35:47 once you have the disassembly figured out the assembly is much simpler to visualize 14:35:57 I see, it is harder! 14:36:09 maybe now the good "octal" will help me to learn 14:36:17 yes 14:36:33 because each opcode is comprised of various ocatl fields within the bytes 14:36:41 better yet - never look at asms again ;-) 14:37:09 I440r, why are tables in hex useless? 14:37:19 because they do not show the opcode fields 14:37:29 patterns 14:37:42 there are also BIT fields in some opcodes. like the direction bit 14:37:57 mov ax, bx <-- this can actually be encode to move AX into BX 14:38:13 or bx into ax as is the norm with x86 14:38:38 theres the size bit too. for byte, word where word can be 16 32 or 64 bits now 14:39:12 tom novelli's site is cool :) 14:39:14 remember, i have never completed any x86 assembler to date 14:39:19 TCN is cool 14:39:34 TCN ? 14:45:37 his innitials 14:51:00 I440r: how are your guitars ? me and friends have a metal band too 14:54:17 band's home page is so empty :: http://wei-ji.github.io/ 14:57:36 i have 3. the i440r, an ibanez ae (accoustic electric) and a hand made spanish classical 15:11:31 --- join: DKordic` (~user@109-92-205-94.dynamic.isp.telekom.rs) joined #forth 15:11:46 vanila: you see my (call/cc f) == (f (cc)) stuff. I think in the "forth-like syntax", this idea is much more useful. 15:12:05 It's interesting 15:12:19 I tried to think how to implement (cc) but i didnt get a solution 15:13:57 one simple solution is to implement return-stack and argument-stack by linked-list (with a GC). I am trying to find better solutions 15:14:28 --- quit: DKordic (Ping timeout: 240 seconds) 15:17:36 vanila: why "90-mins" video is not good ? you know better one ? 15:17:45 just beacuse it's hard to see his slides 15:17:53 but the PDF along with it is good 15:18:05 oh 15:25:13 --- quit: xyh (Ping timeout: 265 seconds) 15:34:50 --- join: xyh (~xieyuheng@2001:250:3002:5550:6ea1:cc0f:bcb2:b187) joined #forth 16:04:05 --- nick: bluekelp_ -> bluekelp 16:04:51 --- mode: ChanServ set +v bluekelp 16:06:29 vanila: scheme needs CPS transformation, but forth does not. we already using CPS [RPN] in forth, no transformation is needed. and in forth the semantics of continuation is extremely clear! why not first class continuation? 16:07:30 could continuation in forth be return stack? 16:07:37 be able to make a copy ofthe return stack 16:07:43 up to some RESET marker 16:12:22 simple way is to do return-stack and argument-stack as list 16:12:40 with a GC no copy of stack is needed 16:13:36 but list is one constant factor slower then stack. 16:14:45 and the Infrastructure (maybe a VM) must have a GC [I do not dare to say it is forth anymore] 16:23:29 /c 16:26:13 --- quit: Zarutian (Read error: Connection reset by peer) 16:26:58 --- join: Zarutian (~zarutian@168-110-22-46.fiber.hringdu.is) joined #forth 16:27:07 bluekelp: /c ? 16:27:09 --- quit: Zarutian (Read error: Connection reset by peer) 16:27:48 in my irc client /c is an alias to clear screen. but if i type a space in front of it, it just sends it 16:27:56 --- join: Zarutian (~zarutian@168-110-22-46.fiber.hringdu.is) joined #forth 16:53:38 --- join: ehaliewicz (~user@204.11.226.50.static.etheric.net) joined #forth 17:00:51 --- join: proteusguy (~proteusgu@49.230.89.30) joined #forth 17:13:18 --- part: xyh left #forth 17:26:23 --- quit: Azel (Ping timeout: 258 seconds) 17:44:02 --- join: xyh (~xieyuheng@121.33.190.150) joined #forth 17:48:28 --- quit: xyh (Ping timeout: 255 seconds) 17:51:28 --- join: xyh (~xieyuheng@121.33.190.150) joined #forth 17:59:13 --- quit: ehaliewicz (Remote host closed the connection) 17:59:28 --- quit: Zarutian (Quit: Zarutian) 18:05:53 --- quit: proteusguy (Ping timeout: 240 seconds) 18:22:11 --- join: samrat (~samrat@123.236.183.195) joined #forth 18:40:59 --- quit: xyh (Ping timeout: 250 seconds) 19:02:58 --- quit: samrat (Ping timeout: 264 seconds) 19:05:51 --- join: samrat (~samrat@123.236.183.195) joined #forth 19:09:33 --- quit: samrat (Client Quit) 19:28:23 --- join: proteusguy (~proteusgu@49.230.89.30) joined #forth 19:29:11 --- join: samrat (~samrat@123.236.183.195) joined #forth 19:36:30 --- quit: proteusguy (Ping timeout: 245 seconds) 20:03:32 --- join: nicole (~nicole@68.225.98.27) joined #forth 20:08:44 --- quit: karswell (Read error: Connection reset by peer) 20:09:35 --- part: nicole left #forth 20:45:14 --- quit: samrat (Quit: Computer has gone to sleep.) 20:57:33 --- quit: vanila (Quit: Leaving) 21:21:09 --- join: samrat (~samrat@61.12.96.226) joined #forth 21:37:14 --- join: Bahman (~Bahman@84.241.8.144) joined #forth 21:38:30 --- quit: PoppaVic (Ping timeout: 258 seconds) 21:45:32 --- quit: DKordic` (Quit: ERC Version 5.3 (IRC client for Emacs)) 22:11:34 --- join: karswell (~user@87.114.135.1) joined #forth 22:18:39 oh my, I have a doubt 22:18:53 the moment I type «bl word foo count type» 22:19:24 how come it doesn't overwrite the string foo after it parses count? 23:00:47 --- join: tangentstorm (~michal@108-218-151-22.lightspeed.rcsntx.sbcglobal.net) joined #forth 23:54:09 --- join: pgomes (~pgomes@ipb2182f12.dynamic.kabel-deutschland.de) joined #forth 23:59:59 --- log: ended forth/14.11.17