00:00:00 --- log: started forth/12.06.05 00:05:05 --- join: ttmrichter (~ttmrichte@61.184.206.85) joined #forth 00:05:05 --- mode: ChanServ set +v ttmrichter 01:31:17 --- quit: phirsch (Read error: Connection reset by peer) 01:36:49 --- join: phirsch (~phirsch@xdsl-89-0-150-191.netcologne.de) joined #forth 01:36:49 --- mode: ChanServ set +v phirsch 02:45:47 --- quit: ttmrichter (Quit: Leaving) 06:05:44 --- quit: ASau (Remote host closed the connection) 06:06:24 --- join: ASau (~user@176.14.220.200) joined #forth 06:06:25 --- mode: ChanServ set +v ASau 06:07:26 --- join: nighty- (~nighty@static-68-179-124-161.ptr.terago.net) joined #forth 06:07:27 --- mode: ChanServ set +v nighty- 06:09:40 --- join: fantazo (~fantazo@85-127-86-149.dynamic.xdsl-line.inode.at) joined #forth 06:09:40 --- mode: ChanServ set +v fantazo 07:34:55 --- join: Joshua_MG (~alvesjnr@pcpavel.intec.ugent.be) joined #forth 07:34:56 --- mode: ChanServ set +v Joshua_MG 09:32:03 --- join: Monevii (~Monevii@adsl-64-237-234-175.prtc.net) joined #forth 09:32:03 --- mode: ChanServ set +v Monevii 09:32:13 --- join: Kumul (~Kumul@adsl-64-237-234-175.prtc.net) joined #forth 09:32:13 --- mode: ChanServ set +v Kumul 09:52:15 --- quit: ASau (Read error: Connection reset by peer) 09:54:09 --- join: ASau (~user@93-80-107-158.broadband.corbina.ru) joined #forth 09:54:09 --- mode: ChanServ set +v ASau 11:06:05 --- join: RodgerTheGreat (~RodgerThe@71-13-215-128.dhcp.mrqt.mi.charter.com) joined #forth 11:06:05 --- mode: ChanServ set +v RodgerTheGreat 11:58:29 --- join: _spt_ (~in@unaffiliated/-spt-/x-5624824) joined #forth 11:58:30 --- mode: ChanServ set +v _spt_ 12:01:15 --- part: _spt_ left #forth 12:41:20 --- join: impomatic (~digital_w@37.152.226.59) joined #forth 12:41:20 --- mode: ChanServ set +v impomatic 13:28:36 --- quit: DGASAU` (Remote host closed the connection) 13:29:09 --- join: DGASAU`` (~user@91.218.144.129) joined #forth 13:29:10 --- mode: ChanServ set +v DGASAU`` 14:23:00 --- quit: phirsch (Ping timeout: 245 seconds) 14:24:24 --- join: phirsch (~phirsch@xdsl-89-0-191-107.netcologne.de) joined #forth 14:24:24 --- mode: ChanServ set +v phirsch 14:28:37 --- quit: nighty- (Remote host closed the connection) 14:31:56 --- quit: dom96 (Ping timeout: 260 seconds) 15:07:59 --- join: Onionnion (~ryan@adsl-76-229-167-179.dsl.milwwi.sbcglobal.net) joined #forth 15:08:00 --- mode: ChanServ set +v Onionnion 15:08:38 * Onionnion was just trying to calculate Fibonacci numbers in C when he realized it'd probably be a lot easier in Forth thanks to stacking 15:11:31 or..blah I don't know D; 15:14:32 it's not all that hard to do in C, either 15:14:36 though it is much easier in Forth 15:16:07 It is equally difficult. 15:16:19 fibonacci was the first "real" code i wrote in my new asm, which is soon hosting a forth :D 15:16:23 It doesn't depend on "stacking". 15:17:09 I don't know why, but I just can't figure it out 15:19:26 but please no one tell me though cause I have to figure it out on my own to get better 15:35:49 --- join: fantazo_ (~fantazo@91.119.97.228) joined #forth 15:35:49 --- mode: ChanServ set +v fantazo_ 15:38:30 --- quit: fantazo (Ping timeout: 244 seconds) 15:46:48 --- quit: fantazo_ (Remote host closed the connection) 16:26:34 --- join: dom96 (dom96@unaffiliated/dom96) joined #forth 16:26:34 --- mode: ChanServ set +v dom96 16:26:42 --- quit: Onionnion (Quit: Leaving) 17:31:22 --- join: segher (~segher@5ED3C8DF.cm-7-4d.dynamic.ziggo.nl) joined #forth 17:31:22 --- mode: ChanServ set +v segher 18:07:54 --- quit: phirsch (Ping timeout: 248 seconds) 18:08:27 --- join: RodgerTheGreat_ (~rodger@71-13-215-128.dhcp.mrqt.mi.charter.com) joined #forth 18:08:28 --- mode: ChanServ set +v RodgerTheGreat_ 18:08:32 --- quit: RodgerTheGreat_ (Client Quit) 18:14:55 --- join: phirsch (~phirsch@xdsl-89-0-191-107.netcologne.de) joined #forth 18:14:55 --- mode: ChanServ set +v phirsch 18:48:07 --- quit: Nisstyre (Quit: Leaving) 19:50:37 --- quit: jyfl987 (Ping timeout: 256 seconds) 19:59:44 --- join: jyfl987 (~jyf@unaffiliated/yunfan) joined #forth 19:59:45 --- mode: ChanServ set +v jyfl987 20:00:21 is there ever something in forth that is "easier" ? 20:31:08 It's certainly somewhat easier to optimize programs for size in Forth 20:32:04 size? 20:41:16 as in, do the same thing in maybe 50k that it would take a megabyte to do in some other languages 20:41:33 the two basic ways to optimize a program are for speed or size 20:41:41 speed means the program runs faster but may take up more memory 20:41:47 size means it's smaller but may run a bit slower 20:42:28 for a lot of applications where Forth is used, speed is not necessarily the #1 goal anyway, and parts of the program (certain words) can be written in assembler when it is 20:42:35 Kumul: to act as an ACL, i think its quite easy 21:03:57 i was talking more codewise, but forth saving memory is a given (surely it must to be, to be used in such constrained devices) 21:39:11 It is hard to tell what is easier "in" Forth. 21:39:30 One thing is certain is what is easier "for" Forth. 21:40:13 Writing ineffective interpreters for Forth is definitly easier than for more conventional languages. 21:53:17 --- join: I440r (~zhiming@168.sub-166-249-131.myvzw.com) joined #forth 21:53:17 --- mode: ChanServ set +o I440r 22:05:05 --- quit: Monevii (Remote host closed the connection) 22:10:21 --- join: fantazo (~fantazo@91.119.75.149) joined #forth 22:10:21 --- mode: ChanServ set +v fantazo 22:23:15 ASau: I disagree. I could write the world's shittiest C compiler, far shittier than the shittiest of Forth engines 22:23:27 lol 22:23:30 gcc 22:23:34 you cant get shittier than that 22:23:40 i CHALLENGE you! 22:25:54 DocPlatypus: it still takes a bit more knowledge to do that. 22:26:12 (That's why we don't see so many shitty C compilers.) 22:26:51 gcc. nuff sed 22:27:00 I submit the null program as a maximally shitty C compiler 22:27:03 it works very poorly 22:27:18 msvc++ (awesome if you want to code 3465873645873648756384563 gigs of c sources 22:28:41 alternately /dev/urandom. Just take some bytes from it and see if it gives you a binary for the C program you wrote. If it doesn't, try again. You could perhaps use it to compile a C program to automate the process, but... 22:29:28 RodgerTheGreat, NO> that would be a FAR SUPERIOR compiler to any c compiler 22:30:02 it certainly has a chance of producing better code than most c compilers 22:30:08 although compilation time is a bitch 22:30:21 on average 22:30:50 thats why i advocate isforth. 2754762364592364 gigs of soruce code per second compiled on a 286! 22:33:07 --- quit: nighty^ (Ping timeout: 252 seconds) 22:40:35 --- quit: RodgerTheGreat (Quit: RodgerTheGreat) 23:13:51 funny how the most shittiest is the most used program out there 23:14:05 but you must be joking 23:20:31 no 23:20:31 being humorous. but at the same time deadly serious 23:20:45 gnu development tools are the single worst tools ive ever had the misfortune to have to use in 25+ years of software development 23:20:46 period 23:26:04 :) 23:26:09 night gents 23:26:14 --- quit: Kumul (Quit: gone) 23:30:04 --- quit: fantazo (Remote host closed the connection) 23:38:18 --- quit: karswell (Remote host closed the connection) 23:49:53 --- join: karswell (~coat@93-97-29-243.zone5.bethere.co.uk) joined #forth 23:49:54 --- mode: ChanServ set +v karswell 23:59:59 --- log: ended forth/12.06.05