00:00:00 --- log: started forth/19.04.11 00:04:23 --- nick: cp- -> nighty 00:04:45 --- quit: nighty (Quit: Disappeared in a puff of smoke) 00:06:53 --- join: nighty (~nighty@b157153.ppp.asahi-net.or.jp) joined #forth 00:22:28 --- quit: MrMobius (Read error: Connection reset by peer) 00:50:05 --- join: jedb (~jedb@185.128.24.51) joined #forth 00:57:31 pointfree: thanks, but i havnt found seedforth mentioned by the pdf in the repo 01:14:49 --- quit: proteusguy (Ping timeout: 250 seconds) 02:03:48 --- join: rdrop-exit (~markwilli@112.201.169.15) joined #forth 02:04:27 --- quit: ashirase (Ping timeout: 252 seconds) 02:07:01 --- join: ashirase (~ashirase@modemcable098.166-22-96.mc.videotron.ca) joined #forth 04:46:34 --- join: dddddd (~dddddd@unaffiliated/dddddd) joined #forth 05:11:51 --- quit: bb010g (Ping timeout: 240 seconds) 05:11:55 --- quit: alexshpilkin (Ping timeout: 268 seconds) 05:11:57 --- quit: siraben (Ping timeout: 265 seconds) 05:12:25 --- quit: jimt[m] (Ping timeout: 252 seconds) 05:27:45 --- quit: Krenium () 05:43:48 --- quit: rdrop-exit (Quit: Lost terminal) 05:51:29 --- quit: chunkypuffs (Remote host closed the connection) 06:57:56 --- join: MrMobius (~default@c-73-134-82-217.hsd1.va.comcast.net) joined #forth 07:16:46 --- quit: tabemann (Ping timeout: 250 seconds) 07:43:00 --- quit: dave0 (Quit: dave's not here) 07:51:33 --- quit: Zarutian (Read error: Connection reset by peer) 07:51:47 --- join: Zarutian (~zarutian@173-133-17-89.fiber.hringdu.is) joined #forth 09:33:17 --- quit: Zarutian (Read error: Connection reset by peer) 09:34:19 --- join: Zarutian (~zarutian@173-133-17-89.fiber.hringdu.is) joined #forth 10:38:55 Forth totally makes you a better programmer 10:39:41 Was writing some PHP stuff today (never written PHP before), everything worked first time sans a couple syntax errors 10:40:24 was told the development team take maybe a week to develop an equally simple piece of software 10:45:55 --- join: Krenium (Krenium@63.142.121.42) joined #forth 11:29:51 wait wut? why so long? 11:30:41 probably more to the story than we're hearing 11:32:09 but also: always overestimate when asked how long something will take 11:34:10 and also, generally when development in asked for a time estimate, the question isn't "how long will it take you to think about and type this?" it's "how long until you have a working, reviewed, and tested product that's gone through the established process and is ready for delivery?" 11:41:42 We don't have "process" and it's appalling 11:42:17 we have "process" in the sense that there is some process and everybody's aware of it. whether it's actually followed is another matter 11:42:30 it also means I have a production-ready self destructing pastebin thingy deployed in a day 11:43:25 only like 100 lines of php and mysql too 11:45:38 I didn't ask the devs anyway, I asked the guy who shouldn't be anywhere near development but is the only one trusted to liason with their team, dude complains about them all the time 11:47:45 it's also a question of how exactly the estimate was derived. was it "it will take development a week starting tomorrow to implement this thing" or was it "development is really busy atm. we might be able to have something for you in a week?" 11:47:55 --- quit: gravicappa (Ping timeout: 246 seconds) 11:47:58 the former. 11:48:16 --- join: gravicappa (~gravicapp@h83-174-248-43.dyn.bashtel.ru) joined #forth 11:48:34 can't believe people willingly choose to dev in php 11:48:54 would rather work with 1-9-9-1 lol 12:05:43 --- join: DKordic (~user@178-222-26-80.dynamic.isp.telekom.rs) joined #forth 12:21:37 WilhelmVonWeiner: I've been thinking about using (g)forth with CGI but it doesn't really have the database tools. 12:22:23 --- join: proteusguy (~proteusgu@202.58.193.235) joined #forth 12:22:23 --- mode: ChanServ set +v proteusguy 12:24:26 --- quit: gravicappa (Ping timeout: 250 seconds) 12:29:55 Your Forth can be your database. 12:30:03 lest you write to a mysql socket 12:46:20 just write the database tools you need... 12:48:32 I am not quite sure what I need, tbh :þ 12:57:04 http://www.ultratechnology.com/method.htm 12:57:23 good luck with the "bugs simply can't happen" parts though... 13:14:59 I have an unreleased interface to sqlite3 via unix pipes that I've been playing with. I should finish it sometime... 13:22:07 Hmm, I have no clue how to do all that stuff... Maybe I should just generate static pages. 13:24:37 static pages are best IMO 13:25:41 Mmh. 13:39:59 I bought a 2TB HDD. I should have no issues with storage space for static pages :þ 13:46:00 --- quit: Keshl (Quit: Konversation terminated!) 13:53:57 --- join: Keshl (~Purple@207.44.70.214.res-cmts.gld.ptd.net) joined #forth 16:22:04 --- quit: nerfur (*.net *.split) 16:28:19 --- join: nerfur (~nerfur@broadband-95-84-184-13.ip.moscow.rt.ru) joined #forth 16:31:09 --- quit: john_cephalopoda (Ping timeout: 240 seconds) 16:38:43 --- join: rdrop-exit (~markwilli@112.201.169.15) joined #forth 16:43:13 Bonjour Fortheurs c[_] 16:44:50 --- join: john_cephalopoda (~john@unaffiliated/john-cephalopoda/x-6407167) joined #forth 16:44:51 --- join: dave0 (~dave0@108.060.dsl.syd.iprimus.net.au) joined #forth 16:46:29 hi 16:46:42 Hi dave0 16:46:46 hi rdrop-exit 17:42:12 --- join: tabemann (~tabemann@rrcs-162-155-170-75.central.biz.rr.com) joined #forth 17:56:41 know what I should do? 17:57:58 one and then the other of A) having it transparently compile to native code and B) make a version that can run under a hypervisor 18:00:35 subroutine threading sounds fast 18:00:50 everything is code is cool too 18:02:06 hmm I might make it so that the native code transpiler is actually written in Forth 18:03:11 and all that is needed to be added to the VM is a mechanism to make pages executable and a mechanism to execute code at a given address 18:04:43 I agree dave0 SRT+NCI is cool 18:07:12 yeah, I'm gonna do TTC converted to SRT+NCI 18:07:41 but the thing is that I'm not going to implement it in the VM itself 18:08:37 all that I'm gonna do is mmap() with PROT_EXEC the memory space and provide a mechanism to call native code from Forth and vice versa 18:09:01 I'm not clear on where your VM is going 18:09:45 Forth code generating Forth code will generate it as TTC 18:09:52 then, when ; is executed 18:10:07 another chunk of Forth code will take over and transpile it to native code 18:11:16 so words like IF ELSE THEN BEGIN WHILE REPEAT UNTIL ?DO LOOP etc. will see the code as TTC 18:11:27 but the actual code executed will be SRT-NCI 18:12:24 therefore very few changes will need to be made to the VM to support this 18:13:02 as it will almost all be written in Forth 18:14:45 of course in this scheme the image loaded will have to transpile itself at startup 18:15:18 anyways, gotta head home - bbl 18:15:29 I thought your project was a portable VM spec 18:17:01 it is, aside from that it will have two words EXEC-NATIVE that executes native code at an address and RETURN-ADDR which returns an address that can be called from native code to return to the TTC VM 18:17:58 Aren't those implementation internals? And therefore up to the implementer who ports your VM to a new platform. 18:18:11 yes 18:19:00 So perhaps premature at this point 18:19:35 okay, I do need to go now - gotta get dinner 18:19:46 Bon appetit 18:19:50 bbl 18:24:28 --- quit: tabemann (Ping timeout: 250 seconds) 19:46:45 --- join: tabemann (~tabemann@2600:1700:7990:24e0:e9cf:9aca:5cdd:e5ee) joined #forth 20:28:25 --- join: gravicappa (~gravicapp@h83-174-248-43.dyn.bashtel.ru) joined #forth 20:32:47 --- quit: rdrop-exit (Quit: Lost terminal) 20:39:18 --- quit: dave0 (Quit: dave's not here) 20:49:47 --- quit: dddddd (Quit: Hasta otra..) 22:13:36 crc, your sqlite via unix pipes is just streaming text in/out of the sqlite executable? Could do the same with psql client for Postgres just as easily, for example? 23:59:59 --- log: ended forth/19.04.11