00:00:00 --- log: started forth/19.04.02 00:02:54 --- quit: gravicappa (Ping timeout: 245 seconds) 01:23:26 thanks bluekelp 01:23:46 I'm still convinced a cloud forth might be some kind of useful.... somehow 01:31:04 --- join: xek (~xek@apn-37-248-138-82.dynamic.gprs.plus.pl) joined #forth 01:44:00 --- join: aspect (~aspect@abstracted-spleen.org) joined #forth 01:47:18 --- quit: Zarutian (Ping timeout: 250 seconds) 01:48:53 --- join: Zarutian (~zarutian@173-133-17-89.fiber.hringdu.is) joined #forth 02:03:39 --- quit: ashirase (Ping timeout: 250 seconds) 02:06:39 --- join: gravicappa (~gravicapp@h109-187-213-103.dyn.bashtel.ru) joined #forth 02:09:03 --- join: ashirase (~ashirase@modemcable098.166-22-96.mc.videotron.ca) joined #forth 04:07:12 --- join: wa5qjh (~quassel@110.54.243.37) joined #forth 04:07:12 --- quit: wa5qjh (Changing host) 04:07:12 --- join: wa5qjh (~quassel@freebsd/user/wa5qjh) joined #forth 04:07:47 --- quit: wa5qjh (Remote host closed the connection) 05:15:51 --- join: dddddd (~dddddd@unaffiliated/dddddd) joined #forth 08:35:56 crc: using bash command "rm -f fifo; mkfifo fifo; cat fifo | retro rfb_serv.fs | nc -l 127.0.0.1 5901 > fifo", do you think that retro can do RemoteFrameBuffer based gui? one would need to use a vnc client to connect though. 08:56:49 Zarutian: off the top of my head, the only issue I can think of is that RFB uses unsigned integers 11:12:05 --- quit: gravicappa (Ping timeout: 245 seconds) 11:23:36 --- join: dys (~dys@tmo-102-137.customers.d1-online.com) joined #forth 11:52:32 whee... C is so much fun - oh, and flogging gforth is OK ;-) 12:06:37 C is ok... 12:06:53 c is so good i want to marry it 12:12:33 I use C as a matter of convenience; I no longer have the time or drive to handcraft an assembly implementation of my VM for each platform I use 12:13:16 i just wish c toolchains were more accessible and not written by absolute madmen 12:14:49 I have no arguyments in either statement - although "forth toolchains" are worse 12:15:21 PoppaVic: can you point to some "forth toolchains"? 12:15:38 zy]x[yz: never marry it - lease it.. borrow it.. rent it.. 12:15:49 scandelous! 12:16:15 crc: well, we got all of the gforth "extensions", we got various FIG/whatever "libraries" - you end up have to rewrite it anyway 12:16:39 zy]x[yz: been married. Never performing that stupidity again. 12:17:13 I suspect it's cheaper and easier to have a whole house full of cats that ignore what you say, rather than be married. 12:18:18 I don't think of "libraries" and "extensions" as part of the "toolchain", more the tools (compiler, assembler, linker, etc) 12:19:00 So, my engine is at the point where: 1) I should think about target-porting; 2) I should think about importing register bullshit. 12:19:28 crc: Hm, I always considered them the high side of it. Otherwise they just lay there looking silly 12:20:11 zy]x[yz: were you speaking of the compiler? linker? libc? Yes? 12:20:17 yes 12:20:20 not libc 12:20:29 ah, love a man that understand interrogation. 12:20:44 sorry, you already said YES. 12:20:53 fight me 12:21:15 nah, I never fight anymore - I'd have to learn all the new places to dump parts of a body. 12:22:02 well, my botch has always been the linker nonsense.. Everyone tells me we need 'em, but sheesh. 12:22:24 "but wait! we need to 'program' the linker, too!" 12:22:59 (Look, biotch: just lay down the bytes where I fucking told you to lay down the goddamned bytes) 12:27:04 --- quit: Zarutian (Read error: Connection reset by peer) 12:27:26 --- join: Zarutian (~zarutian@173-133-17-89.fiber.hringdu.is) joined #forth 12:36:03 OK, just generated a handful of assembler .inc -> fort .fs conversions. yay 13:09:00 --- quit: xek (Ping timeout: 257 seconds) 13:23:42 --- quit: Zarutian (Read error: Connection reset by peer) 13:24:05 --- join: Zarutian (~zarutian@173-133-17-89.fiber.hringdu.is) joined #forth 13:25:55 --- quit: PoppaVic (Remote host closed the connection) 13:53:17 --- join: PoppaVic (~PoppaVic@unaffiliated/poppavic) joined #forth 14:49:32 --- join: dave0 (~dave0@223.072.dsl.syd.iprimus.net.au) joined #forth 14:50:08 hi 15:37:04 --- quit: nonlinear (Quit: Ping timeout (120 seconds)) 15:37:21 --- join: nonlinear (~nonlinear@unaffiliated/discrttm) joined #forth 15:40:28 --- quit: dave0 (Quit: dave's not here) 16:42:08 --- quit: john_cephalopoda (Ping timeout: 258 seconds) 16:43:00 --- quit: tabemann (Ping timeout: 250 seconds) 16:55:13 --- join: john_cephalopoda (~john@unaffiliated/john-cephalopoda/x-6407167) joined #forth 17:00:29 --- quit: irsol (Remote host closed the connection) 17:30:49 --- join: irsol (~irsol@unaffiliated/contempt) joined #forth 17:38:46 --- join: tabemann (~tabemann@rrcs-162-155-170-75.central.biz.rr.com) joined #forth 17:44:59 --- quit: dddddd (Remote host closed the connection) 18:11:05 --- join: tabemann_ (~tabemann@rrcs-162-155-170-75.central.biz.rr.com) joined #forth 18:12:34 --- join: malyn_ (~malyn@unaffiliated/malyn) joined #forth 18:12:56 --- quit: tabemann (Remote host closed the connection) 18:12:56 --- quit: malyn (Quit: "") 18:12:58 --- nick: malyn_ -> malyn 18:22:02 --- join: dave0 (~dave0@223.072.dsl.syd.iprimus.net.au) joined #forth 18:22:38 re 19:48:32 rdrop-exit: So last night you mentioned that "metacompilation could take shortcuts." What exactly were you referring to? You said that it was limited, but I can't really see any limitations of the approach I'm planning. Maybe I'm planning what you'd call cross-compilation, just without actually "crossing" to another architecture. 19:48:37 Hi dave0. 19:53:33 --- quit: tabemann_ (Ping timeout: 250 seconds) 19:57:59 Anyway, so far as I can tell from pre-thinking this, I'm just compiling code (code that generates machine code bytes, and regular definitions), and the compiler is using the base address of my image region for the "relative" calculations. 19:58:33 It seems to me like pretty much anything I compile that way ought to work, as long as it's self-contained and I properly take care of the handful of odds and ends that need touching after the process is over. 20:16:17 --- join: tabemann_ (~tabemann@2600:1700:7990:24e0:e9cf:9aca:5cdd:e5ee) joined #forth 20:28:22 hi KipIngram 20:28:46 i was trying to code 20:29:03 can't concentrate today :-( 20:32:45 --- join: gravicappa (~gravicapp@h109-187-213-103.dyn.bashtel.ru) joined #forth 21:06:12 --- join: rdrop-exit (~markwilli@112.201.169.15) joined #forth 21:06:41 Good afternoon Forthwrights :) 21:14:13 KipIngram: A metacompiler is both simpler than a cross-compiler because the native and target architectures are the same, and the native and target Forth threading scheme are the same. 21:22:25 --- join: proteusguy (~proteusgu@cm-114-109-129-168.revip13.asianet.co.th) joined #forth 21:22:25 --- mode: ChanServ set +v proteusguy 21:24:15 But it is more confusing than a cross-compiler because it's using image #N to compile a modified version of its own source to produce Image #N+1. 21:28:26 In other words in a cross-compiler there are two codebases, that of the native system, and that of the target system. 21:31:32 In a meta-compiler you're trying to get away with one codebase. 21:38:41 A metacompiled Forth makes it look like it compiled itself from its own source, when actually it was an older version of itself that compiled its source. 21:41:51 --- quit: cp- (Quit: Disappeared in a puff of smoke) 21:44:03 --- join: cp- (~cp@b157153.ppp.asahi-net.or.jp) joined #forth 21:44:13 --- quit: cp- (Client Quit) 21:44:48 --- join: cp- (~cp@b157153.ppp.asahi-net.or.jp) joined #forth 22:44:24 --- quit: proteusguy (Ping timeout: 250 seconds) 23:42:56 --- quit: sigjuice (Quit: ZNC - http://znc.in) 23:45:43 --- join: proteusguy (~proteusgu@mx-ll-180.183.121-251.dynamic.3bb.co.th) joined #forth 23:45:47 --- mode: ChanServ set +v proteusguy 23:59:59 --- log: ended forth/19.04.02