00:00:00 --- log: started forth/16.12.09 00:04:28 --- join: reepca` (~user@std-001.cune.edu) joined #forth 00:08:16 --- quit: reepca (Ping timeout: 244 seconds) 00:35:48 --- join: mnemnion (~mnemnion@2601:643:8102:7c95:659c:3764:92ca:6cb0) joined #forth 00:36:43 --- quit: X-Scale (Quit: HydraIRC -> http://www.hydrairc.com <- Now with extra fish!) 00:40:01 --- quit: mnemnion (Ping timeout: 245 seconds) 01:09:11 --- quit: ASau (Remote host closed the connection) 01:09:27 --- join: ASau (~user@netbsd/developers/asau) joined #forth 01:19:16 --- join: opollen (~opollen@184-203-219-105.pools.spcsdns.net) joined #forth 01:27:31 --- quit: ASau (Ping timeout: 268 seconds) 01:33:08 --- quit: nighty (Quit: Disappears in a puff of smoke) 02:03:26 --- join: ASau (~user@netbsd/developers/asau) joined #forth 02:04:36 --- quit: opollen (Quit: opollen) 02:18:43 --- quit: ASau (Ping timeout: 260 seconds) 02:20:28 --- join: ASau (~user@netbsd/developers/asau) joined #forth 02:53:00 --- join: nighty (~nighty@s229123.ppp.asahi-net.or.jp) joined #forth 03:07:29 --- quit: ASau (Remote host closed the connection) 03:07:46 --- join: ASau (~user@netbsd/developers/asau) joined #forth 03:15:12 --- join: ASau` (~user@x52717929.dyn.telefonica.de) joined #forth 03:18:43 --- quit: ASau (Ping timeout: 250 seconds) 03:20:40 --- quit: ASau` (Remote host closed the connection) 03:21:21 --- join: ASau` (~user@x52717929.dyn.telefonica.de) joined #forth 03:29:58 --- join: ASau`` (~user@x52717929.dyn.telefonica.de) joined #forth 03:30:13 --- quit: ASau` (Remote host closed the connection) 03:35:55 --- quit: ASau`` (Ping timeout: 248 seconds) 04:43:37 --- quit: true-grue (Read error: Connection reset by peer) 04:53:22 --- join: mnemnion (~mnemnion@2601:643:8102:7c95:659c:3764:92ca:6cb0) joined #forth 04:58:01 --- quit: mnemnion (Ping timeout: 258 seconds) 05:25:53 --- join: ricky_ricardo (~rickyrica@2602:306:328f:79f0:e971:91fb:95a7:d002) joined #forth 06:20:43 --- join: rgrinberg (~rgrinberg@24-246-56-85.cable.teksavvy.com) joined #forth 06:29:38 --- quit: John[Lisbeth] (Ping timeout: 258 seconds) 07:08:57 --- join: Uniju (~frog_styl@cpe-74-78-4-232.mass.res.rr.com) joined #forth 08:08:04 --- join: Zarutian (~zarutian@168-110-22-46.fiber.hringdu.is) joined #forth 08:08:43 --- quit: Zarutian (Read error: Connection reset by peer) 08:10:20 --- join: Zarutian (~zarutian@168-110-22-46.fiber.hringdu.is) joined #forth 08:16:29 --- join: true-grue (~true-grue@176.14.222.10) joined #forth 09:01:34 --- join: X-Scale (~ARM@48.53.158.5.rev.vodafone.pt) joined #forth 09:27:10 --- join: mnemnion (~mnemnion@2601:643:8102:7c95:9de9:66eb:57ab:88bc) joined #forth 09:31:43 --- quit: mnemnion (Ping timeout: 258 seconds) 09:37:26 --- join: workp (~workp@host-92-25-126-252.as13285.net) joined #forth 09:43:21 --- join: mnemnion (~mnemnion@2601:643:8102:7c95:9de9:66eb:57ab:88bc) joined #forth 10:02:47 --- join: Mat4 (~claude4@ip5b410480.dynamic.kabel-deutschland.de) joined #forth 10:23:16 --- join: neceve (~ncv@79.114.83.228) joined #forth 10:23:16 --- quit: neceve (Changing host) 10:23:16 --- join: neceve (~ncv@unaffiliated/neceve) joined #forth 10:24:29 --- quit: Mat4 (Quit: Leaving) 10:42:37 --- quit: mnemnion (Read error: Connection reset by peer) 10:43:14 --- join: mnemnion (~mnemnion@2601:643:8102:7c95:9de9:66eb:57ab:88bc) joined #forth 11:32:15 --- quit: karswell` (Remote host closed the connection) 11:33:47 --- join: karswell` (~user@127.209.208.46.dyn.plus.net) joined #forth 11:43:46 --- quit: karswell` (Ping timeout: 246 seconds) 11:52:22 --- quit: rgrinberg (Ping timeout: 260 seconds) 12:15:15 --- quit: workp (Ping timeout: 256 seconds) 12:40:42 --- nick: reepca` -> reepca 12:57:49 --- quit: neceve (Quit: Konversation terminated!) 12:59:23 --- join: rgrinberg (~rgrinberg@cp209-202-78-3.cp.telus.net) joined #forth 13:09:25 --- join: proteusguy (~proteus-g@88.128.80.207) joined #forth 13:09:25 --- mode: ChanServ set +v proteusguy 14:20:52 --- quit: rgrinberg (Read error: Connection reset by peer) 14:26:12 --- join: John[Lisbeth] (~user@2601:601:8f01:a6a0:e977:d1e5:cdc:700b) joined #forth 14:26:20 It's like 14:26:25 my life's work was to find forth 14:26:34 and now that I've found it I am just mentally cumming continuously 14:26:47 It just feels like my brain is orgasming any time I think about forth 14:27:27 when arnold schwarzenneger talked about bodybuilding he said working out felt like cumming and every rep felt like he was cumming and I did not understand what he meant because my passion was not bodybuilding 14:27:48 but my passion is computers, computer language, and systems programming, and now I understood why arnold said that as a young man 14:28:21 To get forth after four years of reserach is like the ultiamte reward for my hard work 14:29:05 and it has been out there ready for me to grasp it since before I was a baby. In fact since it can be represented in mathematics you could say it is inherent in the laws of the universe and is always around for all beings in the universe to find and use 14:29:36 but in terms of human concern it has been around far before I was born and if we had known it's use then it RPN would have been taught to me in school, and on a computer, and not infix on paper and pencil 14:42:51 --- join: mnemnia (~mnemnion@2601:643:8102:7c95:a9a6:107:d718:e650) joined #forth 14:44:51 --- quit: pointfree (Ping timeout: 250 seconds) 14:44:52 "I once was lost but now I'm found, 14:44:52 Was blind, but now I see" 14:45:25 forth does that to you... if you an break past the initial resistance to RPN thinking 14:45:30 which it seems most people cant do 14:46:28 --- quit: mnemnion (Ping timeout: 258 seconds) 14:47:01 --- quit: true-grue (Read error: Connection reset by peer) 14:47:07 --- join: pointfree (~pointfree@c-174-62-81-78.hsd1.ca.comcast.net) joined #forth 14:47:19 --- quit: mnemnia (Ping timeout: 240 seconds) 14:52:41 --- quit: nighty (Read error: Connection reset by peer) 14:54:26 --- quit: dzho (Quit: leaving) 14:54:34 --- join: dzho (~dzho@unaffiliated/dzho) joined #forth 14:54:43 --- join: banonos (b04eabac@gateway/web/freenode/ip.176.78.171.172) joined #forth 14:56:06 --- join: mnemnion (~mnemnion@71.198.73.193) joined #forth 14:58:15 --- join: mnemnia (~mnemnion@2601:643:8102:7c95:718d:58a3:d023:92ab) joined #forth 15:01:19 --- quit: mnemnion (Ping timeout: 250 seconds) 15:01:50 hi there 15:03:36 hello? 15:05:00 --- quit: dzho (Quit: leaving) 15:05:09 --- join: dzho (~dzho@unaffiliated/dzho) joined #forth 15:05:48 is it normal for ?DO to be a compile only word in gforth? 15:08:16 I'm trying to troubleshoot a loop but this is making it dificult. i'm afraid I might have done goofed my dictionary 15:13:59 i dont use gforth 15:14:13 but ?do is normally an immediate word that compiles (?do) 15:14:28 and immediate words have no function in interpret mode 15:14:38 they compile 15:14:51 in isforth, if you want to do an interactive loop i have rep 15:15:01 : foo .. . . . ; 15:15:04 100 rep foo 15:15:17 you can also do : bar 100 rep foo ; 15:19:48 no rep for me :/ 15:20:16 no but you can define it. its a simple definition 15:20:21 hang on 15:21:07 generally speaking loops have a specific purpose 15:21:28 if you are iterating over the exact same lines of code over and over again in the exact same sequence then you want to put in a loop 15:21:45 but you don't want to start with a loop, you want to start by programming it the dumb way then automating it 15:21:48 my definition for rep might not work exactly as is for you but hers how i define it 15:22:08 well actually this is a typical array thing 15:22:10 : (rep) swap for dup>r execute r> next drop ; 15:22:22 i'm new to forth but I recognize the pattern 15:22:30 erm actually i use an isforthism in here that has no translation to gforth nvm 15:22:53 it looks like it's two nestes for loops in any other language 15:23:48 nested* 15:24:59 no prob mark4 15:26:01 what rep does is call call (rep) with an address of the word to be repeated and a count 15:26:46 ( address count --- ) 15:26:55 the count is used to initiate a for loop 15:27:03 I see 15:27:14 whats actually on the stack could better be shown as ( ... ... ... address count ) 15:27:21 so we repeat a loop COUNT times 15:27:36 we copy address to the return stack and then call execute which runs the word at "address" 15:27:48 which MIGHT have parameters on the stack or leave results on the stack 15:28:00 dup>r execute r> 15:28:21 the drop discards the address once the requested number of itterations have been completed 15:28:50 --- quit: ricky_ricardo (Remote host closed the connection) 15:30:19 (I'm reading you very slowly :D ) 15:31:52 John[Lisbeth]: the thing is, I'm not writing. I'm reading code. more precisely, I'm messing with glforth 15:32:41 trying to understand it 15:32:51 i think gforth in any incantation is the absolute WORST thing a new forth coder can do 15:33:05 I agree 15:33:08 it is the single most compliFUCKated abomination of a forth compiler ever devised 15:33:22 I've been loving jonesforth 15:33:49 but then GLforth caught my eye and I hand to go the gforth way 15:34:00 had* 15:35:38 glforth is written in gforth 15:37:00 I think it's because it's somewhat straightforward to wrap around shared C libraries, in this case GL GLU and SDL 15:38:34 well one of the main points of forth is for it to be as easy as possible to customize to your own liking 15:38:42 and ans forth is just meant to be the c of doing this 15:38:45 so naturally it is hard 15:38:52 and gforth is just the gcc of forth 15:40:17 John[Lisbeth]: i find what you said to be true on so many levels 15:41:30 that's a great comparison 15:47:12 no gforth is not forth 15:47:32 its a faked forth is abomination 15:47:35 ish 15:47:47 gorth is forth enough 15:47:48 who cares 15:48:07 the point is to understand concatenative programming using push and pop, programming in the purely functional style 15:48:32 no forth will ever be the perfect forth 15:48:47 the problem of forth today is not it's implementations but the barrier to entry 15:49:00 trying to convince someone to think convatenatively using RPN is a very hard task 15:49:19 not that they couldn't learn it, but that they won't, or that they haven't yet 15:49:57 I think a large reason for this is many modern forths have a literal stack which only accept numbers and you manage memory manually 15:50:21 those of us who undertstand forth well know that just a little bit of turing tar, like glue, can add in these features people want 15:50:34 it just needs to be a tad bit easier in order for new programmers to like it 15:52:14 it is hard to convince someone when they are pushing and popping all those numbers that there is light at the end of the tunnel in which they design the perfect language for them 15:52:59 people want to push "hello" and they want to push true and when they pop and pop they want to get back "hello" and true instead of two numbers 15:53:37 and adding this is maybe one page of forth really 15:53:45 John[Lisbeth]: if you need to use objects, use an object-orientated language 15:53:58 I don't get why you'd want objects in Forth 15:54:14 seriously what the fuck is the point 15:54:27 Forth is an ideal language for small, low-power, low-resource systems 15:54:44 I don't think you really need to add in objects in order to get people to use it but that's just me 15:54:50 object-orientated programming is not really something you'd tend to do on a system like that 15:55:02 if you want objects use Python, Python's really good at objects 15:55:18 putting an OO framework into Forth is like putting a dishwasher into a car 15:55:19 sure 15:55:21 you can make it work 15:55:28 and you can drive along washing dishes 15:55:31 but who the fuck wants to? 15:55:34 it makes no sense 15:55:40 it's an utterly inappropriate paradigm 15:57:49 puthon is NOT good at objects lol 15:58:04 mark4: well, no language is, really 15:58:12 mark4: Python's the best of a bad bunch 15:58:41 i think of OOP the same way i think of recursion. sure, you can use it as a crutch 15:58:49 but anything you can do WITH it you can do better without 15:59:50 and i agree, OOP really does not have a place ina forth system 15:59:59 its mashing a round peg into a square hole 16:00:11 it never really fits 16:00:16 no, OOP is a very useful tool 16:00:24 but like all tools, it must be used correctly 16:00:44 sadly it's kind of used as a "we're doing OOP so it must be good!" thing 16:00:49 I blame Java for this 16:05:13 --- join: nal (~nal@adsl-64-237-234-83.prtc.net) joined #forth 16:05:42 „Java the Corba of Object Based Programming“ 16:08:47 java makes OOP palatable. 16:08:54 --- quit: M-jimt (Remote host closed the connection) 16:09:04 i blame c++ 16:09:11 I never really saw the point of Java 16:09:22 the most horrendously craptastic language ever devised 16:09:44 i wish google would stop using it as its basis for android devel 16:09:52 mark4: yea 16:10:21 but most of my android devel is NDK in assembler 16:10:38 I use C quite a bit, but I don't much like very high level languages like that 16:10:51 problem is i cant get android stupidio to build my sources which build just fine from command line 16:11:06 I don't really trust assemblers 16:11:13 too abstracted 16:11:30 i dont like the GNU assemblers 16:11:42 they are not real assemblers. they are the stinky SHITTY rear end of c compilers 16:12:00 NASM is ok 16:12:22 but i would rather isforth had the assembler i cant write so i could then do a proper metacompile 16:12:37 tbh I don't much like software 16:12:46 it's so inefficient 16:13:13 it's like 16:13:15 no software is only inefficient because coders do stupid things 16:13:28 how can you program stuff, when you don't know what's actually happening when that runs 16:13:46 gordonjcp, my primary critisism of c coders 16:13:56 q: how many C coders are there in the world 16:13:56 basically unless you're just going to implement it in hardware you're wasting clock cycles 16:14:00 a: billions! 16:14:14 q: how many of them can write a 100% from scratch C compiler by themselves with no help 16:14:19 a: errr 2? ish? maybe? 16:14:25 mark4: damn sure I can't 16:14:32 q: how many forth coders are there in the world? 16:14:36 Richard Stallman? Bjarne Soustrup? 16:14:43 a: a few thousand MAYBE? 16:14:56 q: how many of them can code a 100% from scratch forth compiler with no help? 16:15:05 a: all of them or they are not forth coders 16:15:05 probably about a quarter 16:15:10 realistically 16:15:14 that doesnt mean they would want to but... thyey COULD 16:15:31 all of them could, with some degree of help 16:15:57 I doubt everyone that programs Real Stuff in Forth could roll their own environment entirely from scratch 16:15:58 remove the requirement for no help from both... the nubmers wont change at all 16:17:53 I think you're overstating it slightly 16:18:00 --- join: Kumool (~nal@adsl-72-50-86-52.prtc.net) joined #forth 16:18:15 but I suspect the figure lies somewhere between your "all Forth programmers" and my "about a quarter of Forth programmers" 16:18:37 mark4: fwiw I get bored round about the part where I need to write "expect" and "word" 16:18:55 mark4: and I end up just writing my app in macro assembler anyway 16:19:11 once I've got my primitives up and a rough implementation of docol and dovar 16:19:36 query and expect are easy 16:19:41 yup 16:19:50 accept should never be used 16:19:54 I just rarely have a use for them 16:19:58 why fix it. it was never broken tyvm 16:20:27 ok well i copied k&r's F83 versions of query and expect out of tom zimmers FPC :P 16:21:49 --- quit: nal (Ping timeout: 265 seconds) 16:21:52 --- join: ASau (~user@netbsd/developers/asau) joined #forth 17:05:50 --- join: John[Lis` (~user@2601:601:8f01:a6a0:5c5:6f8b:9dc7:f2c6) joined #forth 17:05:56 --- join: ricky_ricardo (~rickyrica@2601:240:4203:ecb0:9069:fe52:54ff:b846) joined #forth 17:25:27 --- quit: John[Lis` (Read error: Connection reset by peer) 17:26:05 --- join: John[Lis` (~user@2601:601:8f01:a6a0:5c5:6f8b:9dc7:f2c6) joined #forth 17:28:46 --- quit: John[Lisbeth] (Ping timeout: 245 seconds) 17:36:40 --- quit: ricky_ricardo (Ping timeout: 258 seconds) 17:40:19 --- quit: John[Lis` (Quit: ERC Version 5.3 (IRC client for Emacs)) 17:40:57 --- join: John[Lisbeth] (~user@2601:601:8f01:a6a0:5c5:6f8b:9dc7:f2c6) joined #forth 17:42:31 --- quit: proteus-guy (Ping timeout: 250 seconds) 18:00:12 --- join: ricky_ricardo (~rickyrica@2601:240:4203:ecb0:9069:fe52:54ff:b846) joined #forth 18:06:11 --- quit: DGASAU (Read error: Connection reset by peer) 18:07:08 --- join: DGASAU (~user@lmpc.drb.insel.de) joined #forth 18:07:46 on my windows pc now 18:08:04 maybe I should abandone gforth I dunno 18:08:12 lots of people say it's bad and also I can't install it with emacs it seems 18:08:29 I guess I could make c forth but I would want a good repl 18:08:50 and making a good repl can be really difficult it seems 18:08:57 one that handles things well 18:10:12 maybe I could just do it 18:10:16 just make a c forth 18:10:23 what do you say, gentleman and ladies? 18:10:48 --- join: BigTom (~videloki@acb1-84-91-16-67.netvisao.pt) joined #forth 18:11:00 --- part: BigTom left #forth 18:18:48 John[Lisbeth]: don't care about replies, just do your thing, and publish it to whom it may be helpful by any sense 18:20:20 wise words 18:36:02 --- quit: John[Lisbeth] (Remote host closed the connection) 18:40:59 --- quit: proteusguy (Ping timeout: 248 seconds) 18:50:13 can you not code asm? 18:50:42 take everything you know about how hard it is to code in asm and throw it out the window. coding in C is orders of magnitude more difficult 18:50:59 its just "faster" to code in c 18:51:05 faster how? 18:51:22 you dont have to code 40 lines of assembler for printf. you just call printf 19:02:14 movq $format_str, %rdi movq $0, %rax call printf 19:02:16 oh, I C 19:06:24 what I really wanna figure out is how one writes forth systems in forth. 19:09:13 reepca: what do you mean by that? 19:10:28 I've heard that it can be done, and am not sure how that works. Where you can somehow write the core of a forth system in forth. Metacompilation, I think it's called? 19:10:44 you write forth systems in assembler 19:20:09 you write the forth kernel in assembler. this then compiles the extensions to forth 19:20:16 one of those extensions is an assembler 19:20:27 you use this assembler and a metacompiler to compile a new kernel 19:20:31 which you then extend 19:20:50 the kernel has coded definition (assembler) and colon definitions 19:21:36 the difference between a metacompiler and normal forth compilation is that the sources you compile normaly extend the current forth 19:21:59 metacompilation is a form of target compilation. you compile to a target buffer and the target is not part of the current system 19:23:24 --- quit: Zarutian (Quit: Zarutian) 19:31:22 so back to the askin' 19:31:22 --- join: saml_ (~saml@cpe-24-102-97-97.nyc.res.rr.com) joined #forth 19:32:00 this to asm 19:34:51 --- join: DGASAU` (~user@lmpc.drb.insel.de) joined #forth 19:36:08 --- quit: DGASAU (Write error: Broken pipe) 19:38:18 --- join: zy]x[yz_ (~corey@71.59.19.88) joined #forth 19:38:39 --- join: irsol_ (~irsol@unaffiliated/contempt) joined #forth 19:38:57 --- quit: irsol (Write error: Broken pipe) 19:39:05 --- quit: zy]x[yz (Remote host closed the connection) 19:41:18 --- nick: irsol_ -> irsol 19:44:28 --- nick: zy]x[yz_ -> zy]x[yz 20:17:58 --- join: John[Lisbeth] (~user@2601:601:8f01:a6a0:8046:6edd:bc36:6242) joined #forth 20:18:09 eldre not sure what your asking... i would ask can you code assembler? 20:31:08 can i share a link on the channel? 20:31:26 it's a screencast 20:35:05 there are no anal retentive rules against anything in here except trolling :P 20:35:17 mark4: yes i had to, it was about the metacompilation indeed 20:35:43 hum, one minute too late :'( 20:36:01 eldre there are two things missing from my forth compilers. 1: a built in assembler and 2: a metacompiler 20:36:42 alrighty then 20:36:48 --- quit: ricky_ricardo (Ping timeout: 258 seconds) 20:37:16 this was a night well spent https://vid.me/xwln 20:37:56 figured it was probably not a forth problem 20:38:08 oooh i see wht glforth is 20:38:11 its opengl ! 20:38:13 learned how the damn nested look worked 20:38:38 what underlying forth compiler does it use 20:38:54 metacompiler is just forth ^^, hence a meta-asm! 20:38:56 or does glforth run on the video hardware itself 20:39:00 like I said ...gforth 20:39:22 it's completely dependent on gforth 20:39:39 we should detail a use of gforth on arduino someday 20:39:47 banonos, what in gforth does it depend on 20:40:08 gforth IMHO is utter garbage, its not forth. it should never have been written 20:40:10 and because it's opengl it uses a lot of floating point 20:40:15 ya 20:40:26 tho opengl can use fixed point too 20:40:28 the fp stack 20:40:32 there is no advantage to it 20:40:42 so any forth with a floating point unit would suffice? 20:40:43 and those very odd fp instructions gforth has 20:40:49 nope 20:40:59 gforth's fp is a nightmare 20:41:12 the entire system is a nightmare 20:41:15 it gives very odd results 20:41:19 horrendously over complifuckated 20:41:53 what system is that running on btw? 20:42:12 is that a linux system? 20:42:55 even the manual says you "should't use the obvious word because it behaves like mad, so here are three other different words have to lear now, if you wish nothing breaks" 20:43:15 yes it's linux 20:43:25 what widow manager do you use? 20:43:30 gnome 20:43:48 3? 20:44:14 i couldnt stand gnome 3 20:44:15 --- join: nighty (~nighty@s229123.ppp.asahi-net.or.jp) joined #forth 20:44:20 so installed cinnamon 20:44:23 --- join: nighty-- (~nighty@s229123.ppp.asahi-net.or.jp) joined #forth 20:44:27 oh...i don't really know actually 20:44:35 never bothered 20:44:48 to look for the version 20:44:57 i dont really like a DE but this one has less annoyances than the rest 20:45:42 --- quit: nighty-- (Remote host closed the connection) 20:46:09 --- join: nighty-- (~nighty@s229123.ppp.asahi-net.or.jp) joined #forth 20:46:43 which one? gnome? 20:48:17 btw here's glforth official site http://www.complang.tuwien.ac.at/anton/lvas/stack-abgaben/07w/glforth/ 20:48:24 in case you what to play with it 20:48:48 it depends on a few linux things 20:50:33 (oh cinnamon...never tried it) 20:50:51 nice :) 20:54:52 i think the code has a few typos though. I had to make up some values to constants that had just a "$" sign 20:56:51 what in particular is awful about gforth's floating point? 20:58:54 I think gforth's strongest points are its portability, free-ness, and all of the library interfaces. So I'm interested in learning how one writes foreign-function interfaces to C code. 20:59:07 the worse part is the manual explicitly saying the words aren't well designed so they give unexpected results 21:01:13 I applaude the sincerity and the heads-up but...then they recommend about 3 other words to use instead...depending on the wind direction, the earths albedo and the migratory flow of african swallows 21:02:09 the part about f~? 21:02:25 yes 21:05:01 but the good part is that gforth basically breathes C 21:05:14 so there's that 21:05:25 I'm just wondering how one writes C interfaces in general 21:06:02 (I don't know much about linking, loading, and whatnot) 21:06:03 me too 21:07:57 that's why I've been studying jonesforth 21:08:59 it sits on top of linux and aims to interact with c libs and syscalls 21:10:04 I highly recommend it, the asm code's comments are very extensive readme's full of diagrams and all 21:10:20 I am working on concatenative c 21:10:34 I am going to use macros as : 21:11:00 though I may get it far enough where I don't have to use macros anymore 21:11:04 probably very quickly 21:12:53 reepca: github has a few mirrors of jonesforth 21:13:12 in case you're interested 21:16:19 John[Lisbeth]: how does conc c look like? sounds interesting 21:16:53 well try concatenative bash first 21:16:56 here are some examples 21:17:17 push 2 2; plus; pop 21:17:25 I have also made concatenative javascript 21:17:40 push(2); push(2); plus(); echo(pop()) 21:21:08 push push? 21:22:43 it's quite readable but, woudln't you rather have some syntactic sugar just to free yourself from the hassle of writing it? 21:40:26 what i mean to ask is, what's your reasoning behind that choice? 21:43:12 --- quit: saml_ (Remote host closed the connection) 21:46:11 --- quit: Kumool (Quit: WeeChat 1.4) 22:42:58 --- join: proteusguy (~proteus-g@88.128.80.109) joined #forth 22:42:58 --- mode: ChanServ set +v proteusguy 22:47:12 --- quit: proteusguy (Remote host closed the connection) 22:48:08 --- join: proteusguy (~proteus-g@88.128.80.109) joined #forth 22:48:09 --- mode: ChanServ set +v proteusguy 22:49:22 --- join: proteus-guy (~proteus-g@88.128.80.109) joined #forth 22:51:12 John[Lisbeth], I'd give up emacs before any version of forth. :) 23:14:50 --- quit: proteus-guy (Quit: Leaving) 23:59:59 --- log: ended forth/16.12.09