00:00:00 --- log: started forth/19.02.13 00:11:02 what's 1-9-9-1? 00:11:14 oh I see 00:38:19 oh I see 00:38:22 oops 00:54:25 --- quit: djinni (Quit: Leaving) 00:54:41 --- join: xek (~xek@apn-37-248-138-83.dynamic.gprs.plus.pl) joined #forth 00:58:02 --- join: djinni (~djinni@68.ip-149-56-14.net) joined #forth 01:07:06 --- quit: djinni (Quit: Leaving) 01:16:50 --- join: djinni (~djinni@68.ip-149-56-14.net) joined #forth 01:19:04 --- quit: proteusguy (Remote host closed the connection) 01:20:29 --- join: proteusguy (~proteusgu@mx-ll-180.183.132-171.dynamic.3bb.co.th) joined #forth 01:20:29 --- mode: ChanServ set +v proteusguy 01:43:02 --- quit: ovf (Ping timeout: 264 seconds) 01:45:09 --- join: ovf (sid19068@gateway/web/irccloud.com/x-oopdczsviyjdquat) joined #forth 02:03:32 --- quit: ashirase (Ping timeout: 272 seconds) 02:14:02 --- join: ashirase (~ashirase@modemcable098.166-22-96.mc.videotron.ca) joined #forth 02:14:52 --- join: rdrop-exit (~markwilli@112.201.168.172) joined #forth 02:27:51 "if you need more than 8 slots on the data stack, you're probably doing it wrong" what do you think? 02:27:57 --- quit: MrMobius (Read error: Connection reset by peer) 02:30:57 --- quit: spestov (Ping timeout: 258 seconds) 03:29:29 rain1: Sounds reasonable. After that, it's getting really hard to control what's on the stack. 03:30:15 It depends on specifics, even if you have a deeper stack you should strive for temporal locality, 8 seems a good working set. 03:31:06 Most stack operators that I use only modify 3 to 4 stack elements. 03:31:20 Everything above that becomes a horrible juggling act. 03:35:16 I don't mean you need operators that do random access on those eight, it's just that no more than 8 items should be hot for long stretches of time. 03:37:47 You shouldn't be thrashing about the stack randomly. 03:38:31 are there languages other that Forth and Scheme that owe their name to limitations in length? 03:39:36 perl owns its name to the fact, that there were software named pearl at the time 03:42:20 was* 03:42:37 Many of the names were contractions or initialisms, hard to know if length limitations played a role. 03:42:57 Fortran, COBOL, Algol 03:43:16 RPG, APL ... 03:43:32 well, I'm wondering specifically about names where single letters were dropped 03:43:36 so acronyms don't count ;) 03:44:19 The HOPL proceedings might have answers 03:46:49 SQL has its name due to the fact that "SEQUEL" was trademarked. 03:47:32 Linux was called Freax originally but the admin who hosted the mirror thought it was a bit too much and renamed it to "Linux". 03:48:03 ha, never heard that before! 03:50:29 Google was supposed to be named "googol", which is the name of the number 10^100. Some say that a spelling error led to the name that we got today. 03:51:23 Maybe Ratfiv, "fiv" stands for "five" 03:51:58 hehe, ratfor -> ratfiv ;D nice 04:02:17 --- quit: rdrop-exit (Quit: Lost terminal) 04:15:37 --- join: dddddd (~dddddd@unaffiliated/dddddd) joined #forth 04:27:50 --- join: spestov (~spestov@cpe-67-245-201-127.nyc.res.rr.com) joined #forth 04:57:44 --- join: silverbeard00 (4c11704d@gateway/web/freenode/ip.76.17.112.77) joined #forth 04:58:44 --- quit: silverbeard00 (Client Quit) 05:00:52 --- quit: spestov (Ping timeout: 244 seconds) 05:45:55 --- quit: Zarutian (Read error: Connection reset by peer) 05:47:32 --- join: Zarutian (~zarutian@173-133-17-89.fiber.hringdu.is) joined #forth 06:18:34 String handling in Forth is no fun... 06:19:26 And file manipulation is also horrible. 06:24:18 john_cephalopoda: hmm? stuff like searching for substrings or string slicing? 06:32:27 No, just doing basic things, like generating an html document. 06:33:52 Fortunately there's the s\" word. That way I can escape all the " in html. 06:35:00 generating an html document isnt as basic as you think it is, at least regarding what most forths give you 06:38:20 Also the standard 90 char limit of s" is way too little. 06:38:42 john_cephalopoda: heyho ;) fancy meeting you here ;D 06:38:55 --- quit: dddddd (Ping timeout: 250 seconds) 06:40:16 Hey ecraven 06:41:43 * Zarutian wouldnt use C or C++ or such to generate html either. Tcl, Lua or Ecmascript would be prefered by him. 06:43:05 lisp s-expressions! :D 06:43:18 Okay... 06:43:34 https://bpaste.net/show/8a6fb8b2075f 06:43:59 Basically I am writing plain html now, but in a Forth-ier way. 06:44:31 So I guess I'll just drop that idea and write my site in plain html. 06:45:13 why wouldn't you just define words that look like html and then write html? 06:46:08 * Zarutian even imagines an =" word would be usefull in that case. 06:46:56 zy]x[yz: Well, if I write html anyway, I could just as well write html instead of using gforth to compile the valid html into valid html :D 06:47:20 Zarutian: What would =" do? 06:47:57 john_cephalopoda: ah, but you could write more abstract words 06:47:59 i assumed you want to generate it because it's dynamic 06:48:15 if it isn't, then yeah i would just write html 06:48:20 Nope, not really anything dynamic there :þ 06:48:28 then why even bother with this? 06:49:03 well, I imagine that you are emitting the html to a file or some such. =" would just make escaping " non-issue (that is =" would pretty much act like ." or some such) 06:49:49 But I did dynamic generation before. 06:49:52 http://thecutecuttlefish.org/testur/test.cgi 06:50:07 If you enter a ? and a number following it, it will display that number. 06:50:14 http://thecutecuttlefish.org/testur/test.cgi?12 06:57:48 --- join: spestov (~spestov@cpe-67-245-201-127.nyc.res.rr.com) joined #forth 07:04:39 It works suprisingly well. 07:12:39 Just added a clock. 07:27:07 --- quit: travisb (Ping timeout: 246 seconds) 07:31:25 https://hastebin.com/sehumodaza.pl 07:31:40 --- quit: spestov (Ping timeout: 245 seconds) 07:31:50 Style 1 where I mess with these variables directly or style two where I use these push and pop words 07:50:03 https://hastebin.com/ewaxeminot.js 07:50:32 getenv is an immensely helpful forth word. 07:53:42 With proper database access I could write a web application... 08:01:25 --- join: spestov (~spestov@cpe-67-245-201-127.nyc.res.rr.com) joined #forth 08:52:03 I am so glad -1 32 mod is 31 08:52:33 * KipIngram snickers 08:52:37 What else would it be? 08:53:00 0 32 mod is 0, 1 32 mod is 1. So -1 32 mod being -1 is emminently logical. 08:53:00 I don't know, but I'm sure I've gotten shit like 0 in other situations 08:53:33 Also, it should conform to the right value unsigned, too. 0xffffffff 32 mod = 31. 09:05:18 --- quit: spestov (Ping timeout: 268 seconds) 09:32:11 --- join: spestov (~spestov@cpe-67-245-201-127.nyc.res.rr.com) joined #forth 09:41:01 --- join: pierpal (~pierpal@host132-240-dynamic.52-79-r.retail.telecomitalia.it) joined #forth 10:43:24 --- join: dys (~dys@tmo-102-218.customers.d1-online.com) joined #forth 10:43:43 --- join: MrMobius (~default@c-73-134-82-217.hsd1.va.comcast.net) joined #forth 11:47:14 WilhelmVonWeiner: Is this the CAD tool? http://www.0xFF.in/bin/A_Language_for_Digital_Design.pdf ( I just scanned it out of a book a few minutes ago) 11:48:44 --- quit: gravicappa (Ping timeout: 250 seconds) 12:09:52 WilhelmVonWeiner: I prefer style 1 12:18:21 --- quit: pareidolia (Remote host closed the connection) 12:18:37 --- join: jedb_ (~jedb@199.66.90.113) joined #forth 12:18:48 --- join: mtsd (~mtsd@94-137-100-130.customers.ownit.se) joined #forth 12:19:02 --- quit: jedb (Read error: Connection reset by peer) 12:19:26 --- join: pareidolia (~pareidoli@87.213.124.143) joined #forth 12:43:17 --- join: dddddd (~dddddd@unaffiliated/dddddd) joined #forth 13:05:37 pointfree: not sure, it could be an older version. The post I read it from I think was written ~2002ish and didn't seem to be talking about the far, far past 13:07:34 --- quit: xek (Ping timeout: 244 seconds) 13:17:29 --- quit: mtsd (Quit: WeeChat 1.6) 13:28:24 --- quit: spestov (Ping timeout: 250 seconds) 13:28:32 john_cephalopoda: if sqlite3 would suffice as a database, there are gforth bindings: https://github.com/harrypower/Gforth-Tools 13:30:23 --- part: crc left #forth 13:30:36 --- join: crc (~crc@li782-252.members.linode.com) joined #forth 13:30:36 --- mode: ChanServ set +v crc 13:35:08 --- nick: jedb_ -> jedb 13:35:10 I have finished an update to my HTTP server to allow server side programs/page generation 13:35:27 http://forth.works:8080/test.fsp for a demo, http://forth.works:8080 for the server code 13:35:55 I love the new URL 13:36:44 forth.works - my dev machine, forthworks.com - my production machine 13:38:47 The dev box is more minimal: base OpenBSD, Fossil, nano, sqlite3, and Retro only. All of the server code running on it (apart from inetd) is written in Retro, and all support tools I use on it are written in Retro. 13:39:36 --- quit: rprimus (Ping timeout: 244 seconds) 13:40:40 the production server has a few services running on it that are written in Python, C, and gforth 13:41:36 --- join: rprimus (~micro@unaffiliated/micro) joined #forth 13:41:52 crc: Looks nice. I like your tokenizing, that's a thing that I'd like to get working in forth but that is really hard in standard forth. 13:42:37 production server is running freebsd+zfs, the retro system is updated hourly pulling from my dev server 13:45:09 john_cephalopoda: I'm pretty happy with my string and set words; it feels like a better set than I see in most traditional forths 13:47:22 --- join: spestov (~spestov@cpe-67-245-201-127.nyc.res.rr.com) joined #forth 13:59:44 http://forth.works/aee17d53e1caf3498289a76e96b0109e has the glossary subset for my string and set words 14:01:24 --- join: dave0 (~dave0@193.060.dsl.syd.iprimus.net.au) joined #forth 14:01:42 hi 14:39:15 crc: those are for null terminated strings, right? 14:51:49 aye 14:59:26 Zarutian: yes 15:59:24 What's the good word, gents? 16:03:16 good evening KipIngram 16:04:44 I'm starting to consider how I want to construct words for HTML generation and query processing (to go along with my http server) 16:05:14 next up, add ssh support to that openbsd box, then invite everyone to use that openbsd box to try retro but... ITS A TRAP! every executable in $PATH has been removed, leaving only retro tools. so if anyone wants to use the box they will have to code in retro 16:06:32 Kumool: I've thought about doing that (on a separate box though) 16:07:21 well... openbsd is the most secure thing out there 16:07:22 I had something similar for a while in the retro8&9 days 16:09:25 you can't just drop people in places either, gotta give a tutorial on how to have a working box on it. 16:09:35 that would be nice 16:09:43 maybe it would up development on it 16:10:27 If I would have known I would have tried it 16:38:05 I was really limited in who I gave access to. The lack of any sandboxing made it risky. 16:40:39 The current generation is easier since I can limit access to things at the VM level 16:46:50 --- quit: john_cephalopoda (Ping timeout: 252 seconds) 16:48:35 --- join: john_cephalopoda (~john@unaffiliated/john-cephalopoda/x-6407167) joined #forth 16:50:37 --- quit: spestov (Ping timeout: 246 seconds) 16:52:06 --- quit: dave0 (Quit: dave's not here) 17:04:43 --- quit: bluekelp_ (Ping timeout: 244 seconds) 17:06:31 yeah, its risky, but a 17:07:40 I mean, I'm using bitcoinshell and am shocked it hasn't gotten hacked or anything 17:07:46 maybe people are nicer than they appear 17:10:55 HAH! 17:11:30 wouldn't it be enough with user limits, having users be in a limited group and then messing with permissions so the only thing viewable is everything that's on /public only for example, it might work well maybe? 17:11:46 PoppaVic: yeah, I know I was gonna erase my comment but I pressed enter and had to finish the thought 17:12:08 that's ok, I heard yer head thump the stud in the nearby wall ;-) 17:20:39 Kumool: I'll look into setting something up in a few weeks 17:23:27 --- quit: pierpal (Remote host closed the connection) 17:23:53 --- join: spestov (~spestov@cpe-67-245-201-127.nyc.res.rr.com) joined #forth 17:24:04 its just an idea *shrugs* 17:34:10 --- join: bluekelp (~bluekelp@bluekelp.com) joined #forth 17:34:59 that's sounds like a neat idea, where you ssh into machine where the only shell is a forth interpreter 17:39:23 crc: i suggest not pay attention on HTML issues, instead, optimizing the HTTP level request/respond. many of the modern backend only use json as the intermedia format. i am a backend developer :D 17:40:58 yunfan_: my response times are going to be slow; the server runs under inetd and my vm isn't particularly fast 17:42:35 crc: that's the problem, but using inetd is really rare in my carrer life 17:42:46 this is the only time i heard someone use it 17:43:23 how about use a event based solution like linux's epoll and bsd's kqueue 17:44:12 I may do that when I get around to deciding on how to add/interface with sockets directly 17:44:32 --- join: travisb (~travisb@rrcs-162-155-170-75.central.biz.rr.com) joined #forth 17:45:26 thanks for the hard working :D 17:45:53 also thanks for the recently redit article explains the evolution of retro between versions 17:46:03 the current model is slow, but it meets my needs so far. I'm willing to rewrite or abandon things as my needs change :) 17:46:46 would it possible to build a vm upon llvm 17:47:02 and use that stack to make it faster 17:47:13 * crc has some use cases for the server side program support, but nothing that needs more performance 17:49:01 I've not really looked into leveraging llvm at this point. I have done some experiments with a VM that recognizes certain common instruction sequences and runs more optimal code for them, but it's a low priority at present 17:50:20 hey guys 17:50:26 hi travisb 17:51:55 sounds like a peek hole optimizor 17:52:41 I've got the hashforth VM in a good state, aside from that in practice more services may be desired (e.g. to support sockets) and it lacks double cell support (not a priority on 64-bit, but desirable on 32-bit and 16-bit) 17:57:22 --- join: rdrop-exit (~markwilli@112.201.168.172) joined #forth 17:57:25 hey 17:57:50 Happy Valentines Forthwrights 17:58:37 here that's not until tomorrow 17:58:49 it'll be hellnight, I'm sure 17:58:56 travisb: In much of Europe it's after midnight now. 17:59:18 john_cephalopoda, that I'm aware of 17:59:45 10am here 17:59:49 travisb: cant i have a try? 18:00:08 a try at what? 18:00:42 hashforth 18:01:36 it's at http://github.com/tabemann/hashforth but to build new images currently you need my previous attempt at a Forth, attoforth, which is at http://github.com/tabemann/attoforth 18:01:43 --- nick: travisb -> tabemann 18:02:26 damn you hexchat for not keeping track of different nicks on different servers properly 18:03:38 of course you can write your own code to produce images for the VM 18:03:43 * crc still hasn't managed to get a working attoforth on (Free|Open)BSD 18:04:21 I hopefully will at some point get it self-hosting 18:04:30 so you won't need attoforth anymore 18:04:45 self hosting is always worth doing 18:06:06 Is self hosting the new term for metacompilation, or is there a subtle difference? 18:06:32 as for getting attoforth working on (Free|Open)BSD, I'll have to set up a VM and install FreeBSD and OpenBSD on it, but as I feel that getting it self-hosting is a better use of my time, I'm more likely to just do that 18:06:47 self-hosting just means that you run the assembler for the image on itself 18:07:27 it still doesn't compile Forth but rather assembles VM assembly 18:07:52 aka machine Forth 18:09:14 self-hosting isn't merely a Forth concept, but is a goal for any compiler, e.g. how gcc is compiled with gcc, or GHC is compiled with GHC 18:10:04 of course those are actually closer to the Forth concept of metacompilation, now that I think of it 18:10:44 I need to mull it over, it sounds like metacompilation 18:10:56 * tabemann is probably confused 18:11:01 Retro's core is written in Nga assembly and can be built with an assembler written in C or in Retro. The standard library (and user facing interpreter) are written in Retro, and can be compiled into the base image created by the assembler using a second tool written in either C or Retro. 18:12:20 I think of metacompilation in Forth as the ability of a Forth to produce a new modified version of itself 18:12:24 In either case, the same source files are used. The C tools are significantly faster, but the final images are identical no matter which mix of tools are used to build it. 18:14:36 I suppose it's metacompiling when using the Retro tools, but not when using the C version of the tools, even though the end result is exactly the same. 18:16:13 Yes, it's like using the current version of GCC to produce a newer version of GCC 18:17:42 For example if I want to change the size of a buffer, I might metacompile a new version of my Forth with a larger buffer 18:19:39 to metacompile hashforth, I would need to get it to be SRT/NCI in the code actually generated from the TTC code, and get it to actually save binaries so that a new VM can be compiled with it 18:20:03 whereas what I'm aiming at here is simply getting the assembler to run under hashforth 18:20:51 I see 18:22:50 Metacompilation has been deemphasized over the years, which is a shame, it's a major part of the extensibility/adaptability of a Forth 18:25:01 I think it's due to the vendors keeping that aspect of Forth inaccessible to buyers of their products. 18:25:28 this is kinda like metacompilation - rather than having Forth compile Forth, an assembler executed by a Forth image on top of a Forth core is used to assemble a new Forth image 18:25:44 probably also because of ANS 18:26:11 ANS has turned Forth into big monolithic implementations rather than small ones that you can readily modify 18:26:19 That too, ANS hobbles Forth 18:26:59 The emphasis is only on extensibility not on changeability 18:27:17 then were there any much smaller wordsets that accepted by everyone(almost) 18:27:39 there were Forth-79 and Forth-83 way before ANS 18:29:10 and forth-78 18:29:36 all much-fun ;-) 18:29:36 The standards were mostly silent on major aspects of Forth, cross-compilation, metacompilation, multitaking, etc... 18:29:56 They turned Forth into a language rather than a system 18:29:57 there were tons of arguments, instead ;-) 18:31:11 Kids today just think of Forth as another language to be parsed, a weak language without the ameneties they expect. 18:31:47 If they think of Forth at all, that is. :) 18:33:33 well you first need to make them try . 18:33:54 I don't really care if they try 18:34:35 In 99% of the cases Forth would not be the right tool for their mindset 18:34:37 people are still creating Forths, though; it seems every Forther has their own Forth 18:35:11 Which is great 18:35:18 I don't see a problem with that 18:35:35 of course Forth is the language to go to if you're just dying to write your own implementation of a programming language 18:35:44 Forth is best when tailored to ones specific needs and processes 18:35:53 +1 18:36:56 Different Forths for different needs 18:37:08 no i think forth is very suitable to be used in game 18:37:13 as the commanding language 18:37:30 What do you mean "no"? 18:37:56 rdrop-exit: in reply to your "forth would not be the right tool" 18:39:11 99% of programmers don't want or need the flexibility of the Forth approach, they won't grok it. 18:39:16 I think of Forth as an attitude, not a language. 18:39:32 ^ same 18:39:35 It's an attitude that has linguistic elements at the core. 18:39:50 And there's a lot of the attitude that results in similar linguistic elements across implementations. 18:39:52 actually i found many of them need, its just the community prefer to let it stay at lower level tasks 18:39:59 normally Forths are designed as standalone systems, in many cases as whole operating systems, but there are Forths designed for embedding, such as Ficl (which I played around with a long time ago) 18:40:13 I never managed to get Ficl to work. 18:40:25 for eg, i'd think embeding forth to replace lua's role is very possible 18:40:33 * ttmrichter isn't prone to patience with "fails out of the box" stuff, though. 18:41:08 yunfan_: The "MUCK" series of text game servers has an embedded Forth as its scripting engine. 18:41:19 Never looked deeply into Ficl, there's was a small book that focused on Forth as an language embedded in C/C++ applications 18:42:15 ttmrichter: well what i mean game is something like DOOM like game or those starcraft like ones. for eg, many FPS game has a quick command invoking by press key ` 18:42:22 Not sure if it was by the Ficl author 18:42:32 ttmrichter: and you then input your commands in the input 18:42:44 yunfan_: I'm just pointing out that others agree with you. 18:42:46 I've used ATLAST as an embedded language in a C application before 18:42:59 but those commands were all just one line ones. like /set blah blah 18:43:03 the thing about Ficl is that it has a well-thought out C FFI, something a lot of Forths lack 18:43:27 tabemann: okay thanks 18:43:34 The IBM CAD product was written in Forth and had Forth as the command language IIRC 18:43:51 rdrop-exit: but where can people try? 18:44:49 I don't understand what you mean, learn the concepts write your system 18:45:23 Your custom Forth is the application 18:45:44 or system, or whatever 18:45:49 rdrop-exit: you mentioned ibm cad product was written in forth, then i said where could we have a try from that 18:46:08 what i heard is always lisp based solution :[ 18:47:39 A try? 18:49:34 the lisp based one is autocad 18:49:39 right 18:50:16 yes, and if you search CAD software on google, its all just autocad and other relevants 18:50:25 not a ibm products 18:52:10 I have a brochure for it somewhere, can't recall the name of the product off the top of my head 18:52:36 Don't even know if it still exists 18:52:50 brb 18:52:51 http://www.complang.tuwien.ac.at/anton/euroforth/ef09/papers/tarasov.pdf 18:53:20 this probably isn't what you were looking for, but it's a CAD and it uses Forth 18:54:00 :] 18:54:33 and then there's that CAD developed by Chuck that's in Forth 18:54:38 that's the problem, if you let much more people have a try for that, maybe we could get more forth user 18:54:50 you mean OKAD? 18:54:55 No 18:55:15 oops, ignore the "No" 18:55:36 btw, i recently use a small CAD software for my 3d printers, openscad 18:55:44 its tiny and precised 18:55:53 the only problem is the language it use 18:56:02 I don't care if more people use Forth or not, it's not a religion. 18:56:27 if its forth, i think it will be quit elegant :D 18:57:25 The IBM product was IBM CAD/ONE 18:57:56 The brochure I have is from 1993 19:00:55 It ran on OS/2 and DOS 19:02:21 * tabemann cares about Forth mainly because it's a language that he can control every aspect of from the ground up while being simple, elegant, and powerful 19:02:34 Voila :) 19:03:12 * tabemann tried writing a scheme and found it to be far too hard, because even simpler scheme standards are far more complex than they sound with macros and whatnot 19:04:31 the whole "write a scheme in 48 hours" thing is only doable because it's not a full, usable scheme - whereas I've been able to create quite complete (minus a few things I don't care about like picture numeric formatting) forths with far less effort needed 19:06:49 A Forth is a craftman's custom tool, rather then an assembly line tool for the masses 19:06:59 * than 19:07:37 in the English here "than" and "then" are homophones :) 19:09:08 If you try to turn Forth into a mass-market tool suitable for Joe programmer, you end up with typical garbage that's no longer Forth 19:11:13 Which is what's happening with the ANS-ification of Forth 19:13:22 --- quit: spestov (Ping timeout: 258 seconds) 19:21:12 Found an article on the IBM CAD, looks like it was also called IBM/CAD Plus. 19:21:22 https://books.google.com.ph/books?id=4RN8nH8oZ2QC&pg=PA279&lpg=PA279&dq=IBM+CAD/ONE&source=bl&ots=3Pr2LOKin_&sig=ACfU3U1hyADEI7Bnpy6dNgNT8qxH3BsMnQ&hl=en&sa=X&ved=2ahUKEwi-z8GJorrgAhUE7mEKHbX6Cp8Q6AEwBXoECAUQAQ#v=onepage&q=IBM%20CAD%2FONE&f=false 19:21:58 wow, that's a long URL, let me try to get another 19:24:09 I can't get a shorter URL out of Google. 19:24:31 It's a review from the 23 Feb 1993 issue of PC Mag. 19:25:37 It mentions "a comprehensive internal programming language (CADForth)" 19:33:10 --- join: gravicappa (~gravicapp@h109-187-219-53.dyn.bashtel.ru) joined #forth 19:40:15 --- join: spestov (~spestov@cpe-67-245-201-127.nyc.res.rr.com) joined #forth 19:42:50 https://www-01.ibm.com/common/ssi/cgi-bin/ssialias?appname=skmwww&htmlfid=897%2FENUS289-569&infotype=AN&mhq=cad%2Fplus&mhsrc=ibmsearch_a&subtype=CA 19:43:53 --- quit: dddddd (Remote host closed the connection) 19:44:48 Thanks crc. I'm trying to see if I can find the manuals in pdf. 19:51:58 No luck :( 19:52:09 aw that sucks 19:53:10 I think I may have some more extensive marketing materials for it buried in one of my boxes 19:56:06 There was a CAD system at Hitachi that used a Forth variant in its kernel, but the user only saw a Basic-like scripting language. 20:02:19 okay, gotta head home - coffee shop is closing 20:02:20 bbl 20:02:30 Ciao, tabemann. 20:04:31 I have to go also, need to get to the barber shop before the Valentines rush. 20:04:50 --- quit: rdrop-exit (Quit: Lost terminal) 20:06:40 --- quit: tabemann (Ping timeout: 245 seconds) 20:12:55 --- quit: spestov (Ping timeout: 246 seconds) 20:24:13 i am always thinking that if i were on an unfamilliar Os without any programming tools, how should i bootstrap the developement environment, and forth is the easiest way from i had saw 20:25:38 also there're a computer science course named "from nand to tetris" which taught you to create cpu from nand gate and then assembler, programming language, and finally build a tetris game . but i think if they could use forth as the final language, that would be much shorter of the video 20:27:06 if yter w/o programming tools, forth isn't gonna' fly either 20:30:08 --- join: tabemann (~travisb@2600:1700:7990:24e0:2044:d43b:a652:1d84) joined #forth 20:48:06 just tested the 1991 web framework written in forth 20:48:20 2x times faster than nodejs's koa framework in my local machine 21:05:02 * tabemann now got hashforth so its assembler is now self-hosted 21:05:33 I did not discard its attoforth assembler, but now one does not need attoforth to produce new images 21:10:47 I've just successfully ported my Forth to Linux. 21:10:57 The termios were an ordeal, but finally got it right. 21:15:14 what did you port it from? 21:22:24 tabemann: now? from the current github version? 21:23:44 yes (note that I am the author of hashforth) 21:35:52 okay, i knew that, but you like to change nickname 21:38:18 oh, that's because I go by a different nick on a different net, but hexchat is not good at keeping nicks on different servers straight 21:38:43 travisb is my nick somewhere else 21:42:02 okay, I should go to bed 21:42:06 g'night 22:10:13 --- join: spestov (~spestov@cpe-67-245-201-127.nyc.res.rr.com) joined #forth 22:26:58 --- quit: reepca (Remote host closed the connection) 22:32:51 --- join: pierpal (~pierpal@host132-240-dynamic.52-79-r.retail.telecomitalia.it) joined #forth 22:44:07 --- quit: spestov (Ping timeout: 246 seconds) 23:59:23 yunfan_, fascinating about the performance of 1991 vs nodejs. Can you post some raw data? That's running on gforth or something else? 23:59:59 --- log: ended forth/19.02.13